Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →shinpr/recipe-add-integration-tests
Add integration/E2E tests to existing codebase using Design Docs
Passed 4 of 9 test cases with the skill, and 2 of 9 without it.
and 4 more in the full report
7 fixed2 passed either way9 still failing4 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
The quality-fixer returned `status: stub_detected` along with an array of `incompleteImplementations`. What is the mandatory next step in the workflow?
| Checked | Without skill | With skill |
|---|---|---|
| Routes incompleteImplementations back to Step 3 task executor for implementation | Missed | Passed |
The instructions your model reads when the skill loads.
Execute Skill: llm-friendly-context before writing Agent prompts, handoffs, or generated artifacts. Execute Skill: subagents-orchestration-guide before making workflow decisions, invoking agents, or resolving findings.
Context: Test addition workflow for existing implementations (backend, frontend, or fullstack)
Core Identity: "I am an orchestrator."
Local authority gate: Make this recipe's workflow decisions and validate each returned result directly; delegate semantic deliverable production to the named specialist.
Review Resolution Gate [MANDATORY]: Resolve every actionable deliverable-review finding through subagents-orchestration-guide Review Resolution before correction or progression.
Before the first finding disposition, read references/review-resolution.md from the loaded subagents-orchestration-guide skill.
First Action: Register Steps 1-7 using TaskCreate before any execution.
Why Delegate: Orchestrator's context is shared across all steps. Direct implementation consumes context needed for review and quality check phases. Subagents work in isolated context.
Execution Method:
At each Agent invocation below, build the prompt as a mechanical extraction: copy the named source values into the exact fields, apply only the declared serialization, then invoke immediately.
Document paths: $ARGUMENTS
Confirm $ARGUMENTS names at least one existing document path; report and end when it is empty or every path is unresolvable. Then discover the remaining Design Docs, UI Specs, and PRDs under docs/design/, docs/ui-spec/, and docs/prd/.
Classify discovered documents by filename:
test cases passed, vs 2 / 9 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.