feature-design

Feature Design Templates

A structured, adversarial multi-model workflow for taking a feature from a raw idea to implementation-ready epics, stories, and an execution handoff.

What This Repo Contains

This repo is both a set of standalone prompt templates and a Claude plugin that wraps them into slash commands.

• 15 numbered prompt templates — usable independently in any LLM. One process guide plus fourteen prompts covering discovery, adversarial review, synthesis, verification, spec generation, and implementation setup.
• A Claude plugin (fd) — slash commands and a discovery skill that automate triage, exploration, problem statement, UI contract, verification, spec, epics, and PE setup. State is tracked per-feature in a session folder.

The method is best suited to products that already have canonical source docs, a human decision-maker who will make explicit rulings, and a willingness to run multiple independent LLM sessions in parallel.

Use As a Claude Plugin

The plugin runs the in-scope stages of the pipeline (everything except crossfire, deferred for now) as slash commands.

Install

This repo is a self-contained plugin — install it as a local plugin in Claude Code or Cowork mode. Once installed, all commands are namespaced under /feature-design:.

Quick start

/feature-design:start <feature-name> -- <one-line idea>
/feature-design:next      # walks the rest of the pipeline; hard-gates prerequisites
/feature-design:status    # snapshot of the active session

Pipeline (full)

Command	Wraps template	Output
/feature-design:triage	02	01-triage.md
/feature-design:explore	03	02-exploration.md (interactive)
/feature-design:problem	04	03-problem-statement.md
/feature-design:problem-crossfire	05	05a-claude.md, 05b-codex.md, 05c-gemini.md
/feature-design:problem-decision	06	06-validated-problem.md, 06-feature-proposal-source.md
/feature-design:ui-draft	07	04-ui-contract.md (user-facing only)
/feature-design:proposal-crossfire	08	08a-claude.md, 08b-codex.md, 08c-gemini.md
/feature-design:proposal-synthesis	09	09-round{N}-synthesis.md (re-runnable per round)
/feature-design:proposal-iterate	10	10a-round{N}-claude.md, 10b-round{N}-codex.md, 10c-round{N}-gemini.md
/feature-design:proposal-final	11	11-final-design.md (canonical design — locked)
/feature-design:verify	12	07-verification.md
/feature-design:spec	13	08-spec.md
/feature-design:epics	14	09-epics.md
/feature-design:pe-setup	15	10-pe-prompt.md

Sessions live in .feature-design/<slug>/ in your working folder.

The orchestrator (/feature-design:next) hard-gates progression — it refuses to advance if a prerequisite stage hasn't completed. Pass --force to override deliberately.

Crossfire iteration loop: after /feature-design:proposal-synthesis completes, /feature-design:next stops and asks you to choose: another adversarial round (/feature-design:proposal-iterate, then /feature-design:proposal-synthesis again) or finalize (/feature-design:proposal-final). The convergence signal in the synthesis report tells you whether iterating again is likely worth the cost.

Crossfire dispatch — internal vs. external: the three crossfire dispatch commands (/feature-design:problem-crossfire, /feature-design:proposal-crossfire, /feature-design:proposal-iterate) support two modes:

• Internal: plugin invokes Claude (via claude-cli skill), Codex (via codex skill), Gemini (via gemini skill) sequentially from the project working directory. Default.
• External: plugin saves the substituted crossfire prompt to disk and waits for you to run it through your own crossfire tool, then drops the three response files into the session folder. Useful if you have a dedicated crossfire system that does this better than three sequential CLI shellouts.

Mode is set per-session at /feature-design:start time (state.crossfire.dispatch_mode) and can be overridden per-command with --external or --internal. Synthesis and decision commands (/feature-design:problem-decision, /feature-design:proposal-synthesis, /feature-design:proposal-final) work identically regardless of dispatch mode — they just read the response files from the session folder.