Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/plan
Use this skill when performing structured project planning and PRD generation with three modes: new (project kickoff with repo scaffolding), feature (compact feature PRD), retro (data-driven retrospective). All modes share a researched Q&A engine that dispatches parallel Explore agents before each question wave, presents options via AskUserQuestion with recommendations, and produces documents with prioritized issue creation.
Passed 18 of 21 test cases with the skill, and 7 of 21 without it.
and 11 more in the full report
12 fixed8 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are writing the technical design specification for the user payment integration before creating any implementation plan. In which directory path should this design specification document be saved?
| Checked | Without skill | With skill |
|---|---|---|
| The response identifies docs/staging/specs/ as the destination directory. | Missed | Passed |
The instructions your model reads when the skill loads.
docs/staging/plans/YYYY-MM-DD-<topic>.md. Reference the spec; don't restate it.
If unresolved spec notes affect implementation or task order, return to design.
If topology=multi-module (triage announcement or coordinator spec/plan declaration), read ../references/multi-module.md. Open the workspace plan with the declaration block (topology: multi-module, change-set, coordinator, repos, module plan paths, integration task) - it is the on-disk mode marker downstream skills rely on.
repository: and one module:. Cross-module verification is an integration task owned by the coordinator.design only if the addition changes a shared contract.Spec references a milestone (milestone: MN)? Check docs/ROADMAP.md — expand only that milestone. Leave the rest as stubs.
After ship: open docs/ROADMAP.md, confirm which milestone is next, then expand it. Return to design only if the milestone's goal materially changed.
Every task is - [ ] T<n>: <name> - always a checkbox, never a heading. tdd/subagents flip it to - [x] on completion; ship refuses to run while any - [ ] remains.
goal: <one sentence>
files: <paths>
acceptance: <test or cmd>
spec: <docs/staging/specs/...#anchor>
No exact code. No step-by-step. Acceptance is verifiable: a test, command, or scripted check — or, when none is possible, an explicit manual check (steps + expected result). Each task leaves the repo green.
Mark independent tasks: [parallel] T3, T4, T5.
Only mark [parallel] when shared contracts, state, errors, and acceptance are closed.
test cases passed, vs 7 / 21 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.