Use when you have a written plan and are ready to execute it in the current workspace.
Use when you have a written plan and are ready to execute it in the current workspace.
npx skills add https://github.com/dnldxn/claptrap --skill ct-implementこのコマンドをClaude Codeにコピー＆ペーストしてスキルをインストール
| name | ct-implement |
| description | Use when you have a written plan and are ready to execute it in the current workspace. |
OPERATION OVERRIDE: The instructions in this file take precedence over conflicting instructions in any other Skills.
ct-manage-state-file to record that the workflow is now in the implementation state and note the branch name.ct-manage-state-file to record that the workflow plan is now implemented and note which plan was finished.Use the following Skills to implement the plan below. Announce newly loaded skills before starting. Then implement the plan step by step using subagent-driven-development. Invoke other skills (frontend-design, systematic-debugging, etc.) as needed. Continue until the plan is fully implemented.
REQUIRED SUB-SKILLS: Use using-superpowers, context-management, token-efficiency, subagent-driven-development, and ct-manage-state-file.
Plan: $ARGUMENTS
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 writing implementation plans after a design or spec has been approved.