Frenchie Method

Frenchie Method is the workflow/process layer. Frenchie Kit is the file and multimodal capability layer.

• /frenchie-method starts Method orchestration.
• /frenchie remains Frenchie Kit and must not be treated as a Method alias.
• Text-only Method usage does not require a Frenchie API key.
• Install skills alongside MCP tools with npx @lab94/frenchie install.
• Codex Desktop exposes slash entrypoints by skill name, not by reading

.claude/commands/*.md. The Codex installer creates wrapper skills such as requirement, qa-analysis, and implement so /requirement can work after restart. If a host does not expose those wrappers, treat no-slash requests such as Frenchie Method requirement ... as the corresponding Method command.

Runtime Defaults

Use .frenchie/method.config.json when present. If it is missing, continue with production-safe defaults:

• artifacts: .frenchie/docs/feature
• knowledge: .frenchie/docs/knowledge
• worktrees enabled by default
• orchestrator recommends the full sequence; direct commands warn-and-continue
• artifact language: auto
• cross-model review: off
• skill triggers: command-key skeleton is present; defaults are empty because installed skill sets vary by agent

Command Routing

The slash form below is the canonical Method command name. Claude Code reads command files directly. Codex uses wrapper skills with the same names. If the host agent does not support either path, recognize the same names without the leading slash when the user clearly asks to use Frenchie Method.

Tier 1 commands:

/frenchie-method
/method-check
/prepare-feature
/documenting-code
/requirement
/qa-analysis      alias /test-case
/design           conditional
/security-review
/sa-analysis      alias /implementation-plan
/task-plan
/implement
/run-test
/walkthrough
/create-pr
/pr-review        alias /review-pr
/quality-score
/fix-review
/systematic-debug alias /debug /fix-bug
/release-check
/release
/job-done

PRD command routing:

/refine-requirement      alias /frenchie-refine-requirement
/user-story              alias /frenchie-user-story
/scope-check             alias /frenchie-scope-check
/open-questions          alias /frenchie-open-questions
/stakeholder-summary     alias /frenchie-stakeholder-summary
/impact-analysis         alias /frenchie-impact-analysis
/api-design              alias /frenchie-api-design
/db-design               alias /frenchie-db-design
/architecture-review     alias /frenchie-architecture-review
/risk-analysis           alias /frenchie-risk-analysis
/regression-test         alias /frenchie-regression-test
/e2e-scenario            alias /frenchie-e2e-scenario
/test-data               alias /frenchie-test-data
/bug-repro               alias /frenchie-bug-repro
/write-unit-test         alias /frenchie-write-unit-test
/update-docs             alias /frenchie-update-docs
/performance-review      alias /frenchie-performance-review
/rollback-plan           alias /frenchie-rollback-plan
/changelog               alias /frenchie-changelog
/incident-report         alias /frenchie-incident-report
/postmortem              alias /frenchie-postmortem

Route PRD commands to the nearest production-depth command unless a dedicated command file exists. Preserve the exact command the user invoked in the artifact note.

Every direct command warns when recommended Method context is missing, recommends the safer next step, and asks whether to continue from current chat/repo context. Direct commands always work, regardless of which prereqs have run. /frenchie-method recommends the full Method sequence for users who want a structured path — it does not enforce. Method never blocks; the user has final authority on every command, including /release.

/requirement will auto-bootstrap /prepare-feature (after a single confirmation) when no active feature folder exists, so users do not need to chain the two commands manually.

Before each command, read .frenchie/method.config.json.skillTriggers[command] and invoke listed installed skills. Command keys omit the leading slash, for example requirement, qa-analysis, or implement. If a listed skill is unavailable, say so briefly and continue.

Freeform Implementation Requests

When a user invokes Frenchie Method in any form and asks for implementation in the same request, route the request into Method before normal coding. This includes slash commands, wrapper skill names, Frenchie Method ..., and natural-language requests that mention Method while asking to build, change, edit, code, or implement.

For a freeform implementation request, do not edit production code, create a feature branch, or start a generic implementation workflow until Method has established feature context and the minimum artifact set exists, or the user explicitly approves a documented skip.

Minimum artifact set before production edits:

• Feature context and state.json, created or selected through /prepare-feature.
• 01-requirement.md.
• 02-acceptance-criteria.md.
• 03-test-case.md.
• 04-implementation-plan.md.
• 05-design.md for user-facing marketing, frontend, content, UI, navigation, page, component, or flow work.

Branch creation and worktree setup belong to /prepare-feature context. Do not create a branch as an ordinary coding step before Method has resolved or proposed the feature folder.

Chat approval does not replace Method artifacts. If the user asks to skip any artifact, record a documented skip in state.json.decisions[] or in the next Method artifact note before editing production code. "Method never blocks" means the user can override after warnings and a documented skip; it does not mean silent bypass.

Recommended Sequence

The full sequence the orchestrator (/frenchie-method) recommends for production work. Each command can be invoked directly at any point — Method warns when prereqs are missing but never blocks.

/prepare-feature
→ /documenting-code when source context is missing
→ /requirement
→ /qa-analysis            recommended for non-XS work
→ /design                 recommended for new screens, flows, components, or interaction patterns (not color/spacing/copy tweaks on existing components)
→ /security-review        recommended when sensitive paths are touched
→ /sa-analysis            recommended when architecture or schema changes
→ /task-plan
→ /implement
→ /run-test
→ /walkthrough            recommended after /design
→ /pr-review
→ /fix-review             when /pr-review surfaces findings
→ /release-check          recommended before /release
→ /release                only when the user explicitly invokes it
→ /job-done

Source Files

When this package is available locally, Method source lives under method/:

• method/commands/ command docs
• method/skills/ domain workflows
• method/references/ discipline references
• method/templates/ artifact templates
• method/workflows/ task-type flows
• method/adapters/ agent routing notes