refactor: start design recipes from codebase analysis instead of requirement-analyzer#126
Merged
Merged
Conversation
…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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
recipe-designandrecipe-front-designpreviously began withrequirement-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)requirement-analyzercall at the start of both design recipes.rg/grep, and builds therequirement_analysisseed thatcodebase-analyzerrequires. Empty results fall back to asking the user; overly broad results (>~20 files) are narrowed with the user before proceeding.codebase-analyzernow runs first, with its existing schema unchanged.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.subagents-orchestration-guideto 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-reviewerreceivescodebase_analysis, plusui_analysisfor the frontend recipe).Out of scope (unchanged)
requirement-analyzer,codebase-analyzer,subagents-orchestration-guide, and the implement recipes.recipe-implement/recipe-fullstack-implementstill start withrequirement-analyzer.Release
package.jsonto0.19.3.Validation
claude plugin validate— marketplace manifest + all four plugins passnpm run sync:check— generated plugin copies in syncnpm run check:skills-index— all skills consistent🤖 Generated with Claude Code