Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →blackbelttechnology/plan-proposal
Develop-side planning orchestrator for an OpenSpec change: artifact creation → doubt-driven-review → scenario-design → fold of automated scenarios into tasks.md, then STOPS at the git-worktree boundary. Main interactive session only; never a subagent. Triggers: "plan this change", "draft the proposal and plan", "scaffold + review + fold", "prep a change for building".
Passed 15 of 18 test cases with the skill, and 3 of 18 without it.
and 21 more in the full report
15 fixed4 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/4/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am currently inside a git worktree branch named worktree-payments. Can I run the plan-proposal orchestrator here to draft and commit the initial planning artifacts?
| Checked | Without skill | With skill |
|---|---|---|
| Requires planning phase orchestration to be executed on the develop branch. | Missed | Passed |
The instructions your model reads when the skill loads.
Orchestrates the planning phase of an OpenSpec change on develop. Composes
existing skills — it does not reimplement them. Twin of ship-it, which owns
the implementation phase inside the worktree. The two split at the git-worktree
boundary, which is also the interactive/headless line.
flowchart LR
subgraph Planning ["PLANNING — develop, human present"]
A["new/ff/continue"] --> B["doubt-review"]
B --> C["scenario-design + category-fold + manifest"]
C --> D["plan-proposal (this skill)"]
end
D -->|"boundary: commit + spawn worktree"| E["ship-it"]
subgraph Implementation ["IMPLEMENTATION — worktree"]
E
end
plan-proposal MUST run in the main interactive session. It invokes
doubt-driven-review (which spawns a fresh-context reviewer, and a second
cross-model reviewer — automatically when a @propose-review-N role resolves,
offered interactively only when none does; nested subagent spawn is blocked) and
scenario-design (whose proposal/design-stage HARD gate calls ask_user). Both
need a live main session.
Guard: if you detect you are running inside a subagent context (nested
reviewer spawn would be blocked, or ask_user is unavailable), STOP and
surface: "plan-proposal must run in the main session — doubt-review and the
scenario-design gate cannot run nested. Re-invoke from the main session on
develop." Do not degrade the doubt-review to a self-questioning fallback.
develop branch (planning happens on develop; the worktree is spawned
from the planning commit).openspec CLI available; resolve the change name from --change <name>, thetest cases passed, vs 3 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.