writing-plans
The spec-to-plan bridge. Routed to by /feature once the brainstormed spec is approved, and by /sprint before execution. Decomposes the spec into 2–5 minute tasks, each carrying its exact file path(s) and a concrete verification step that maps to a tdd obligation. Writes the plan to .codearbiter/plans/<slug>.md, ordered with dependencies flagged and an MVP slice identifiable. Nothing executes until every task has a path and a verification and the task set covers every acceptance criterion.
npx skills add arbiterForge/codeArbiter --skill writing-plans --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# writing-plans Turn an approved spec into an executable plan. Routed to by `/feature` (after spec approval) and `/sprint`. ## Pre-flight Read these, or STOP and surface the gap — never plan against an unapproved or missing spec: - `{{PROJECT_DIR}}/.codearbiter/specs/<slug>.md` — the approved brainstorming spec. The single source of acceptance criteria. Absent or unapproved → STOP and route back to `/feature`. - `{{PROJECT_DIR}}/.codearbiter/CONTEXT.md` — the `stage:` frontmatter (the maturity value) and project context. - `{{PROJECT_DIR}}/.codearbiter/tech-stack.md` — file layout, build/test/lint invocations. A verification step cites a real command from here, never a guess. - `{{PROJECT_DIR}}/.codearbiter/coding-standards.md` — structure and naming, so a task names the right path. **If `--farm` was requested:** check that `FARM_API_KEY` is set in the environment{{IF:pi}} of the Pi parent process{{ELSE}} (or `.env` at `{{PLUGIN_ROOT}}/tools/.env`){{END}}. If absent, BLOCK immediately — cite `{{PLUGIN_ROOT}}/includes/farm.md` for setup instructions. Do not proceed; the farm dispatcher cannot run without an API key. Model selection happens later (at dispatch time in `subagent-driven
- Pre-flight
- Phase 1 — Criterion extraction · gate: BLOCK
- Phase 2 — Task decomposition · gate: BLOCK
- Phase 3 — Order & MVP slice · gate: BLOCK
- Phase 4 — Coverage proof & write · gate: BLOCK
- Phase 4-farm extension (only when --farm was requested)
- Hard rules
What does the writing-plans skill do?
The spec-to-plan bridge. Routed to by /feature once the brainstormed spec is approved, and by /sprint before execution. Decomposes the spec into 2–5 minute tasks, each carrying its exact file path(s) and a concrete verification step that maps to a tdd obligation. Writes the plan to .codearbiter/plans/<slug>.md, ordered with dependencies flagged and an MVP slice identifiable. Nothing executes until every task has a path and a verification and the task set covers every acceptance criterion.
How do I install it?
Run `npx skills add arbiterForge/codeArbiter --skill writing-plans --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From arbiterForge/codeArbiter, a repository with 138 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.