/feature - Feature Development Orchestrator

Chain /think → /code → /audit for end-to-end feature development.

Plugin Dependencies

Plugin	Required for	Install
agent-browser	Phase 4.5 only	claude plugin add agent-browser

Phase 4.5 is skipped gracefully if agent-browser is not installed.

Input

• Feature description: $1 (optional)
• If empty → prompt via AskUserQuestion (context-aware options)

Context-Aware Options

Detect project type → present relevant options:

Pattern	Detection	Options
Claude Code config	~/.claude/ or .claude/ with skills/hooks/	Add skill, Add hook, Add agent
React/Next.js	package.json has react, next	Add component, Add page, Add API route
API server	Express, Fastify, Hono, or src/routes/	Add endpoint, Add middleware, Add service
CLI tool	bin in package.json or src/cli/	Add command, Add option, Add subcommand
Library	main/exports in package.json	Add function, Add class, Add type
Fallback	No match	New feature, Extension, Refactoring

SOW Context

[@../skills/lib/sow-resolution.md]

Execution

Phase	Name	Action	User Checkpoint
1	Discovery	Context scan → PRE_TASK_CHECK	[?] or [→] resolution
2	Design	Skill: /think	Design approval
3	Implementation	Skill: /code	—
4	Quality	/audit → /fix loop (max 3)	Remaining issues only
4.5	Visual Verification	Browser check (UI tasks only)	Visual approval
5	Summary	AC coverage + scope report	Completion

Phase 1: Discovery

1. Context scan — CLAUDE.md, package.json, Cargo.toml, etc.
2. If $1 empty → AskUserQuestion with context-aware options
3. Execute PRE_TASK_CHECK
4. Resolve any [→] or [?]
5. Early exit: ≤ 2 target files → suggest /code (skip Phases 2-5)
6. TaskCreate for tracking (Phases 2-5)

Phase 2: Design

Execute Skill("think", $1).

Output: .claude/workspace/planning/YYYY-MM-DD-[feature]/sow.md + spec.md

Phase 3: Implementation

Execute Skill("code", $1).

/code auto-discovers SOW from Phase 2 output.

Phase 4: Quality Loop

Step	Action	Exit
1	Skill: /audit (changed files from git)	0 critical/high → Step 4
2	Skill: /fix for each critical/high	→ Step 3
3	Increment iteration (max 3) → Step 1	Max reached → Step 5
4	Skill: /polish → verify tests pass	Tests fail → fix (max 2). Still failing → Step 5
5	Present remaining issues (if any)	User decides

Changed files: git diff main...HEAD --name-only (or base branch).

Phase 4.5: Visual Verification (conditional)

Skip Conditions (evaluate in order, skip on first fail)

#	Check	How	On fail
1	UI files in changed files	Match .tsx, .jsx, .css, .scss, .html	skip (silent)
2	agent-browser installed	which agent-browser	skip (silent)
3	Dev server detected in package.json	Match dev, start:dev, start scripts	skip (silent)

Dev Server Detection

From package.json scripts:

Priority	Script name pattern	Default URL
1	dev, start:dev	http://localhost:5173
2	start	http://localhost:3000
3	storybook, storybook:dev	http://localhost:6006

Extract port from script value if specified (--port, -p, PORT=).

Workflow

1. Detect dev server script and URL
2. AskUserQuestion: "Dev server running at {url}? (Y to proceed / N to skip / custom URL)"
3. agent-browser --headed open {url} → navigate to page matching SOW scope (infer route from changed file paths or AC descriptions)
4. agent-browser screenshot → capture current state
5. Check AC items containing visual keywords (display, layout, UI, style, render, visible, responsive)
6. Present screenshot + findings to user
7. AskUserQuestion: "Visual check OK?" (Approve / Request fix / Skip)
8. If "Request fix" → return to Phase 4 Step 2
9. E2E Test Generation (conditional):
   • If Spec has Type: e2e scenarios:

     Agent(subagent_type: "e2e-test-generator",
           prompt: "spec_path: <path>\ndev_server_url: <url>",
           run_in_background: true)
     

   • If no e2e scenarios → skip (silent)
   • On failure → advisory, continue
10. agent-browser close

Phase 5: Summary

Present summary. AC coverage is already verified by /code Quality Gates.

• Feature scope (files changed, tests added)
• Quality iterations and remaining issues
• AC coverage from /code

Resume

Detect resume point from existing artifacts:

Artifact	Resume
No SOW	Phase 1
SOW draft	Phase 2
SOW in-progress + no implementation	Phase 3
Implementation done + quality not completed	Phase 4
Quality passed + UI files changed	Phase 4.5
Quality passed + no UI files	Phase 5

Implementation evidence: git diff main...HEAD --name-only shows files matching SOW scope.

Error Handling

Error	Action
/think cancelled or fails	Save context, exit
/code fails	Present error, ask user
Quality loop exhausted (3 rounds)	Present remaining, user decides
agent-browser not installed	Skip Phase 4.5, continue to Phase 5
Dev server not running	Skip Phase 4.5, continue to Phase 5
/code Quality Gates shows unmet ACs	Offer to re-enter Phase 3 or 4

Verification

Check	Required
PRE_TASK_CHECK passed?	Yes
SOW + Spec generated?	Yes
All tests pass?	Yes
/code AC coverage?	Yes