Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →svgreg/sg-plan
Turn a research or roadmap document into skill-guard's executable development plan — reconcile it against the repo, expand the next milestone into one-PR tasks with acceptance checks, and keep docs/v1-dev-plan.md current. Planning only, never code.
Passed 14 of 20 test cases with the skill, and 5 of 20 without it.
and 13 more in the full report
11 fixed6 passed either way8 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
When running pre-ship sanity checks on docs/v1-dev-plan.md, what requirement must be verified for every task marked as status todo that has no listed Deps?
| Checked | Without skill | With skill |
|---|---|---|
| Verifies that all todo tasks lacking Deps can be started immediately against main. | Missed | Passed |
The instructions your model reads when the skill loads.
Goal: keep docs/v1-dev-plan.md an accurate, executable breakdown of the source research —
docs/v1-dev-roadmap.md by default — so that /sg-develop can pick up the next task in a fresh
session with no other context. This skill writes plans, not code.
Invocation forms:
/sg-plan — default: reconcile, then expand whichever milestone needs it next./sg-plan M5 — expand that milestone's titles into full task cards./sg-plan docs/<some-research>.md — fold a new research document into the plan./sg-plan replan M4 — re-plan a milestone whose assumptions a spike invalidated.All sg-maintain global guardrails apply, plus:
pkg/, cmd/, testdata/, or a rule pack. If planning reveals a
one-line code fix, write it as a task; do not fix it here.docs/**, README.md, PROGRESS.md, so per guardrail 4 it is
merged right away once CI is green.planning.
Create it once: gh label create planning -c 1d76db -d "development planning" --force.git checkout main && git pull --ff-only
Read, in this order:
docs/v1-dev-roadmap.md) — the what and why.docs/v1-dev-plan.md if it exists — the current what is next.CLAUDE.md, PROGRESS.md, and the repo itself for actual state: what is implemented, whattest cases passed, vs 5 / 20 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.