Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →shinpr/recipe-prepare-implementation
Verifies the work plan is implementable end-to-end and resolves verification-lane / fixture / E2E-environment gaps before the build phase begins.
Passed 8 of 14 test cases with the skill, and 3 of 14 without it.
and 12 more in the full report
10 fixed3 passed either way8 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
After completing prep task commits for `docs/plans/order-processing.md`, there are leftover task files for `order-processing` and an older plan `user-settings`. Which files are deleted?
| Checked | Without skill | With skill |
|---|---|---|
| The assistant deletes prep task files matching the active plan name. | Passed | Passed |
| The assistant retains the main work plan file in `docs/plans/`. | Missed | Passed |
The instructions your model reads when the skill loads.
Execute Skill: llm-friendly-context before writing Agent prompts, handoffs, or generated artifacts.
Context: Optional readiness phase between work-plan approval and recipe-*-build. Confirms the implementation will be observable from Phase 1 onward and resolves any gaps via Phase 0 tasks. Exits no-op when the readiness criteria already pass, so the recipe is safe to invoke unconditionally.
Core Identity: "I am an orchestrator." (see subagents-orchestration-guide skill)
Execution Protocol:
Work plan: $ARGUMENTS
Run before any recipe-*-build invocation when ANY of the following hold:
When none of the above hold, the readiness scan in Step 2 will find zero failing criteria and the recipe exits no-op (see Context at the top of this skill).
Each criterion is a measurable check producing pass, fail, or not_applicable with cited evidence.
| ID | Criterion | Pass evidence |
|---|---|---|
| R1 | Verification Strategy references resolve | Every command, file path, function, endpoint, and test referenced in the work plan's Verification Strategy section either exists in the codebase (verified via Glob/Grep) or is the deliverable of a task already in this plan |
| R2 | E2E preconditions addressed | When E2E skeletons exist: every precondition mentioned in skeleton comments (seed data, auth fixture, env var, external mock) is present in the codebase or covered by a Phase 0 task in this plan |
| R3 | Phase 1 observability | The first implementation phase contains at least one task whose Operation Verification Methods can execute at task completion using only artifacts that exist before the task starts (existing code, prior Phase 0 task deliverables, or the task's own outputs) |
| R4 | UI rendering surface | When the plan implements UI components: a fixture entry, dev route, Storybook story, or equivalent rendering surface exists for the impacted components, OR a Phase 0 task adds one |
| R5 | Local lane procedure | The work plan or a referenced doc records the commands needed to start the system locally for manual verification (start commands, default ports, seed steps) |
R4 and R5 are evaluated only when their triggering signals appear in the work plan; otherwise mark not_applicable.
test cases passed, vs 3 / 14 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.