Stats
Actions
Tags
From sdd
Implements SPEC.md tasks via single-thread plan-then-execute loop. Cites invariants/interfaces, runs verification, backprops failures to spec updates, commits per task.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sdd:buildThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Single-thread native plan→execute. You are main Claude. No swarm.
Single-thread native plan→execute. You are main Claude. No swarm.
SPEC.md. If missing → tell user to invoke the spec skill first. Stop.FORMAT.md once if not loaded.§T.n → that task only--next → lowest-numbered row with status . or ~--all or empty → every . row in §T orderNative plan mode. For chosen task(s):
Show plan. Wait for user OK unless auto mode.
Per task in order:
. → ~. Just write to SPEC.md.~ → x. Next task.On test/build failure:
bug: <cause> first, let it update §V and §B, then resume build against updated spec.Rule: never silently fix root-cause without considering backprop. §B is the memory that stops recurrence.
T<n>: <goal line> + §V cites.Task x only if:
cat SPEC.md | grep §T is the dashboard.npx claudepluginhub kborovik/pilot-skillsPlan-then-execute implementation against SPEC.md, with auto-invoked backprop on failure. Runs native single-thread loop, no sub-agents. Useful for structured, specification-driven development.
Executes approved implementation tasks from a plan.json file created by spec-plan. Tracks progress via beads or harness todos, enforces TDD, and reports between batches. Invoke when ready to start coding from an approved plan.
Executes tasks from an OpenSpec tasks.md file during implementation. Reads task checkboxes, applies code changes, marks progress, runs validation, and handles blockers.