Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →shinpr/recipe-design
Execute from codebase analysis to design document creation
Passed 11 of 16 test cases with the skill, and 5 of 16 without it.
and 5 more in the full report
8 fixed7 passed either way7 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
We have finalized the draft Design Doc at `docs/design/billing.md` and need to verify code claims. What `doc_type` argument must be supplied to code-verifier?
| Checked | Without skill | With skill |
|---|---|---|
| Supplies doc_type set to design-doc | Missed | Passed |
The instructions your model reads when the skill loads.
Execute Skill: documentation-criteria before document routing or creation.
Execute Skill: llm-friendly-context before writing Agent prompts, handoffs, or generated artifacts.
Execute Skill: subagents-orchestration-guide before invoking agents or resolving findings.
Before the first finding disposition, read references/review-resolution.md from the loaded subagents-orchestration-guide skill.
Coordinate the design phase from repository evidence to an approved Design Doc. The orchestrator owns requirement convergence, Structural Scale, ADR qualification, evidence selection, and Review Resolution. Named specialists own semantic investigation and artifact authorship.
The Design Doc is always the complete implementation design for Medium/Large work. A qualifying ADR batch narrows technical choices before the Design Doc, which retains the complete flow and implementation boundary.
Requirements: $ARGUMENTS
requirement source -> codebase-analyzer -> scope/decision confirmation [Stop]
|
optional ADR batch -> batch review [Stop]
|
Design Doc -> code-verifier -> Review Resolution
|
document-reviewer -> design-sync -> approval [Stop]
Execute each dependent step after its prerequisite evidence exists. Use Review Resolution for every actionable verifier, reviewer, or design-sync finding. Wait at each [Stop] for explicit user confirmation.
At each Invoke below, build the Agent prompt as a mechanical extraction: copy the named source values into the exact fields, apply only the declared serialization, then invoke immediately.
Use the approved PRD path when one exists. Otherwise use the confirmed requirements verbatim.
Set confirmed_requirement_context to the approved PRD path exactly. Only when no approved PRD exists, use the orchestrator-confirmed convergence record unchanged.
Invoke dev-workflows-fullstack:codebase-analyzer:
test cases passed, vs 5 / 16 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.