Use when writing implementation plans after a design or spec has been approved.
Use when writing implementation plans after a design or spec has been approved.
npx skills add https://github.com/dnldxn/claptrap --skill ct-writing-plansこのコマンドをClaude Codeにコピー＆ペーストしてスキルをインストール
Use when starting a new design or spec to interview the user, answer open questions, and draft a specification.
Use when starting a new design/spec that should be saved as a GitHub Issue on the Project board after user approval.
Use when executing an implementation plan from a GitHub Project board, committing directly to main with Closes trailers.
Use when breaking a GitHub spec issue into implementation plan sub-issues on the Project board, optionally updating the spec issue body with meaningful new constraints or decisions.
Use when a Claptrap workflow needs to update or resync `.planning/state.html` after spec, plan, implementation, review, merge, or archive changes.
Use when you have a written plan and are ready to execute it in the current workspace.
| name | ct-writing-plans |
| description | Use when writing implementation plans after a design or spec has been approved. |
OPERATION OVERRIDE: The instructions in this file take precedence over conflicting instructions in any other Skills.
REQUIRED SUB-SKILL: Use writing-plans with the following modifications:
.planning/plans/YYYY-MM-DD-<order>-<spec-slug>-<plan-slug>.md<order> values (01, 02, ...)..planning/specs/).<spec-slug> from the parent spec's title/header line (usually H1) as a short kebab-case visual hint..planning/state.html when each plan is written.After saving each plan file, invoke ct-manage-state-file to record the current state and include:
When parent linkage is uncertain, make a best-effort guess and explicitly label it as inferred so ct-manage-state-file can mark the mapping as inferred in .planning/state.html.
Spec: $ARGUMENTS