Command Reference
All available slash commands for factory operations.
| Command | Description |
|---|---|
| /arch-blueprint | Create or review an architecture blueprint for a system or production line. Usage: /arch-blueprint [system-name or description] |
| /arch-review | Review a component, design, or proposal for architectural alignment. Usage: /arch-review [component or description] |
| /ceo-brief | Board-ready factory status brief. Usage: /ceo-brief |
| /ceo-decide | Facilitate a strategic decision by gathering specialist input. Usage: /ceo-decide "topic or question" |
| /ceo-focus-group | Chair a focus group on a strategic topic with relevant specialists. Usage: /ceo-focus-group "topic" [attendee roles] |
| /ci | Log a continuous improvement item to the factory backlog. Usage: /ci "description of improvement, lesson, or issue" |
| /deploy-checklist | Generate and run a deployment checklist for a specific client deployment. Usage: /deploy-checklist <client-name> [--generate | --run] |
| /docs-generate | Auto-generate documentation from repo state. Usage: /docs-generate <mode> [path]. Modes: release-notes, user-guide, api-docs, workflow-docs, all |
| /docs-pipeline | Documentation pipeline — detects what changed, generates internal + client docs, updates intranet. Usage: /docs-pipeline [--scope factory|talent|all] [--dry-run] |
| /docs-publish | Publish generated documentation to a target platform. Usage: /docs-publish <target> [source-path]. Targets: confluence, html, jira, markdown, sharepoint |
| /infra-review | Review repo structure against org chart — reports gaps, orphans, and structural issues |
| /infra-scaffold | Scaffold a new role directory with templates. Usage: /infra-scaffold department/role-name |
| /kb-audit | Audit documentation completeness across all roles and departments. Usage: /kb-audit [department-or-role] |
| /kb-index | Browse or search the factory knowledge base. Usage: /kb-index [search-term] |
| /kb-ingest | Ingest external knowledge into the factory -- scores relevance, maps to roles/patterns/processes, and implements improvements. Usage: /kb-ingest "concept name" [source-url-or-reference] |
| /maint-fix | Diagnose and fix a specific issue with a role or command. Usage: /maint-fix <description of problem> |
| /maint-health | Run health checks across all deployed roles — file completeness, test scores, staleness |
| /market-analysis | Analyze a market segment or trend for digital talent opportunities. Usage: /market-analysis "topic or segment" |
| /market-position | Create or review product positioning for a digital talent type. Usage: /market-position "product or digital talent type" |
| /method-adapt | Create a framework adaptation guide — maps a client methodology (TOGAF, COBIT, ISO, PMBOK, etc.) to the digital talent production pipeline. Usage: /method-adapt "framework-name" |
| /method-improve | Analyze completed orders and propose process improvements to the manufacturing methodology. Usage: /method-improve [order-id | "all"] |
| /method-review | Review an order or production stage for methodology compliance — checks process adherence, handoff completeness, and gate criteria. Usage: /method-review [order-id or stage-number] |
| /method-status | Show manufacturing methodology coverage and compliance summary — methodology health dashboard. Usage: /method-status |
| /name-check | Validate a proposed name against naming standards. Usage: /name-check entity-type/proposed-name |
| /name-standards | Display current naming standards or propose updates. Usage: /name-standards [update-topic] |
| /pattern-catalog | Browse, search, or add patterns to the agentic pattern catalog. Usage: /pattern-catalog [search-term | add | list] |
| /pattern-recommend | Recommend agentic patterns for a use case. Usage: /pattern-recommend "description of your use case" |
| /prod-line-create | Design and create a new production line. Usage: /prod-line-create [line-name or description] |
| /prod-line-status | Review status of all existing production lines. Usage: /prod-line-status [line-name] |
| /qa-regression | Run regression tests across all active roles. Usage: /qa-regression |
| /qa-validate | Validate a role or digital talent against quality standards. Usage: /qa-validate <role-path | --digital-employee path> |
| /rd-scan | Scan for new Claude Code features, MCP servers, plugins, and ecosystem developments. Usage: /rd-scan |
| /request-status | Scan all requests and orders factory-wide, generate company/requests-registry.md, and print a terminal summary. Usage: /request-status |
| /role-factory | Build a new factory worker role — designs, tests, and deploys roles (agents or documented processes) through a 6-stage pipeline. Usage: /role-factory [department/role-name | "description"] |
| /signaler | Signaler un problème — recherche d'abord dans la documentation, puis crée une fiche feedback si non résolu. Usage: /signaler <description du problème> |
| /tech-direction | Review or set technical direction for a topic. Usage: /tech-direction "topic or question" |
| /tech-review | Review a technical proposal or implementation for alignment with vision and standards. Usage: /tech-review "description or file path" |
| /ux-designer | Audit and improve user experience — Analyze websites/products for usability issues, accessibility, and design improvements. Usage: /ux-designer audit {url} or /ux-designer improve {url} {brief} |
| /web-designer | Professional web designer — audits and improves website design. Usage: /web-designer {improve|audit} {url} [brief] |
How to Use
- 1. Type a command name starting with
/ - 2. Include any required arguments as shown in the command description
- 3. Commands are executed in the Claude Code environment