From creation-daemon
Implement a cd:ready ticket: create a branch, write code (TDD), commit, open a PR, transition to cd:in-review
How this skill is triggered — by the user, by Claude, or both
Slash command
/creation-daemon:cd-implementThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Implement ticket #$ARGUMENTS.
Implement ticket #$ARGUMENTS.
Load context. Call cd_get_ticket with issue_number: $ARGUMENTS. Read the refinement artifact (the approved spec) and note the acceptance criteria.
Transition to in-progress. Call cd_transition_state with new_state: in-progress.
Create (or resume) the branch.
<slug> as a short kebab-case form of the ticket title (max 50 chars).cd/$ARGUMENTS-<slug>.git checkout -b cd/$ARGUMENTS-<slug> — or git checkout cd/$ARGUMENTS-<slug> if it already exists.Implement following the spec.
superpowers:executing-plans skill is available, invoke it using the refinement artifact as the plan.superpowers:test-driven-development if available for any new code.[cd#$ARGUMENTS].Push and open the PR.
git push -u origin cd/$ARGUMENTS-<slug> via Bash.gh pr create --title "[cd#$ARGUMENTS] <title>" --body "<body>" --head cd/$ARGUMENTS-<slug> via Bash. The body should reference the issue: Closes #$ARGUMENTS.Write the implementation artifact. Call cd_write_artifact with:
issue_number: $ARGUMENTS
type: implementation
content:
# Implementation for #<n>
## What was built
...
## Key decisions
...
## Deviations from the spec (and why)
...
## How to test
...
Transition to in-review. Call cd_transition_state with new_state: in-review.
cd_block_ticket with the specific conflict rather than guessing.[cd#$ARGUMENTS].cd_block_ticket — do not guess.Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub rainbowrider5/creation-daemon --plugin creation-daemon