菜单
Skill for plan authoring agents. Writes structured implementation plans to the worktree. When BONES_REPO is set, routes plan output through bones repo CI for review before finalizing. Backward compatible: when BONES_REPO is unset, writes plans directly to the local worktree.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use at session start in any darken-managed workspace (any repo containing `.scion/grove-id`) to prime as the host-mode orchestrator for the §7 pipeline. Loads the non-negotiables block, the routing classifier, the background-dispatch monitoring protocol, the bounded-transcript evidence rule, the 14-role roster, the escalation classifier, and the four loop primitives for playbook-driven coordination (darken dispatch / inbox / accept / state). Invoke whenever the operator types a task and the workspace is darken-managed.
Use in any darken-managed workspace (any repo containing `.scion/grove-id`) when you would normally dispatch a subagent via the Agent tool but you are operating as the host-mode orchestrator. Translates the muscle memory into subharness dispatch, maps task shapes to roles, frames the task in caveman-standard with a status-publishing recipe and a fixed milestone vocabulary, and reads worker output back via the bounded-transcript protocol.
Constitution-driven specification flow mounted by planner-t4. Activates when an agent must drive the full ratification pipeline: constitution review, spec.md authoring, plan.md production, and tasks/ decomposition. Use when operating under the specify CLI, when a feature requires formal ratification before implementation, or when producing structured spec artifacts for downstream worker harnesses.
Multi-skill bundle mounted by planner-t3. Activates when a design session must scaffold an architecture that satisfies both Hipp zero-config reliability principles and Ousterhout deep-module complexity reduction. Triggers on requests to design libraries, data layers, or system modules where simplicity, embeddability, and minimal cognitive load must all be balanced together.
Use when designing libraries, modules, or data layers that must be simple, reliable, and self-contained. Use when choosing between embedded vs server-based solutions. Use when reviewing code for unnecessary complexity, dependencies, or configuration. Triggers on requests involving zero-config design, embedded systems, long-term maintainability, or first-principles thinking.
Use when designing modules, classes, APIs, or system architecture. Use when reviewing or refactoring code for complexity. Use when choosing between implementation approaches. Triggers on requests involving abstraction design, interface simplicity, information hiding, or reducing cognitive load.
| name | writing-plans |
| version | 0.1.0 |
| description | Skill for plan authoring agents. Writes structured implementation plans to the worktree. When BONES_REPO is set, routes plan output through bones repo CI for review before finalizing. Backward compatible: when BONES_REPO is unset, writes plans directly to the local worktree. |
| type | skill |
| targets | ["claude-code"] |
| category | {"primary":"workflow"} |
You are authoring an implementation plan. Follow this protocol precisely.
Default (BONES_REPO unset): Write the plan to docs/superpowers/plans/<date>-<slug>.md in your current worktree. Commit with message plan: <slug>.
Bones repo CI (BONES_REPO set): When the BONES_REPO environment variable is set to a path, route plan output through that repo for review:
${BONES_REPO}/plans/pending/<date>-<slug>.md${BONES_REPO} with message plan(pending): <slug>plans/pending/ to plans/approved/), copy the approved plan back to your worktree at docs/superpowers/plans/<date>-<slug>.md and commitIf BONES_REPO points to a path that does not exist or is not a git repo, fall back to the default output target and emit a warning: writing-plans: BONES_REPO=${BONES_REPO} is not a git repo, falling back to local output.
Every plan MUST contain these sections in this order:
Each unit must be implementable in a single TDD cycle (write test, write impl, green, commit). A unit that requires more than ~150 LOC of production code is too large -- split it.
If you cannot write a unit spec because the interface is undefined or the acceptance criterion is unverifiable, add the unit to Open questions instead of guessing. Do not invent interfaces.
Plans authored without BONES_REPO are fully valid. The bones repo CI path is opt-in. Existing tooling that reads docs/superpowers/plans/ is not affected.