Skip to content

refactor: start design recipes from codebase analysis instead of requirement-analyzer#126

Merged
shinpr merged 2 commits into
mainfrom
refactor/requirement-analyzer-intro-steps
May 20, 2026
Merged

refactor: start design recipes from codebase analysis instead of requirement-analyzer#126
shinpr merged 2 commits into
mainfrom
refactor/requirement-analyzer-intro-steps

Conversation

@shinpr
Copy link
Copy Markdown
Owner

@shinpr shinpr commented May 20, 2026

Summary

recipe-design and recipe-front-design previously began with requirement-analyzer, organizing requirements from the user query alone before any code was inspected. In the design phase, a thin query-only requirements pass that misses the mark creates uncertainty and rework. Both recipes now enter design from a scope grounded in real code.

What changed

Design-phase entry (recipe-design, recipe-front-design)

  • Removed the requirement-analyzer call at the start of both design recipes.
  • Added a recipe-local scope bootstrap (Step 1): the orchestrator extracts keywords from the user requirements, locates seed files with rg/grep, and builds the requirement_analysis seed that codebase-analyzer requires. Empty results fall back to asking the user; overly broad results (>~20 files) are narrowed with the user before proceeding.
  • codebase-analyzer now runs first, with its existing schema unchanged.
  • Added a recipe-local scope confirmation step after codebase-analyzer: the user reviews target files/modules, affected layers, unknowns, and open questions, then chooses to proceed / correct the scope / hear more / produce an ADR.
  • Narrowed each recipe's dependency on subagents-orchestration-guide to orchestration principles, the Scale Determination table, and handoff contracts HC-02 onward. The recipes now define their own start order and inline all subagent prompts (including HC-04: document-reviewer receives codebase_analysis, plus ui_analysis for the frontend recipe).

Out of scope (unchanged)

  • requirement-analyzer, codebase-analyzer, subagents-orchestration-guide, and the implement recipes. recipe-implement / recipe-fullstack-implement still start with requirement-analyzer.
  • No agent schema or handoff-contract changes; no new global orchestration concept.

Release

  • Bumped the four local plugins and package.json to 0.19.3.

Validation

  • claude plugin validate — marketplace manifest + all four plugins pass
  • npm run sync:check — generated plugin copies in sync
  • npm run check:skills-index — all skills consistent

🤖 Generated with Claude Code

shinpr and others added 2 commits May 20, 2026 22:40
…irement-analyzer

recipe-design and recipe-front-design previously began with requirement-analyzer, organizing requirements from the user query alone before any code was inspected. A thin query-only requirements pass that misses the mark creates uncertainty and rework in the design phase. Both recipes now enter design from a code-grounded scope: a recipe-local scope bootstrap builds the codebase-analyzer seed, codebase-analyzer runs first, and a recipe-local scope confirmation step lets the user confirm or correct scope before design proceeds. Each recipe's reference to subagents-orchestration-guide is narrowed to orchestration principles, the Scale Determination table, and handoff contracts HC-02 onward, and all subagent prompts are inlined. Agent schemas, handoff contracts, and the implement recipes are unchanged.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@shinpr shinpr self-assigned this May 20, 2026
@shinpr shinpr merged commit b3d7da4 into main May 20, 2026
1 check passed
@shinpr shinpr deleted the refactor/requirement-analyzer-intro-steps branch May 20, 2026 13:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant