Search, contribute to, or update the project's knowledge base.
Create a new Specification for a feature.
Create a new Plan from an approved Specification.
| name | spek-implement |
| description | Execute an approved Plan to implement the feature. |
This skill drives a multi-step interactive workflow that executes an approved plan in .spektacular/plans/<name>/plan.md, producing working code, tests, and a changelog. The workflow is owned by the {{command}} CLI, not by you — the CLI is the state machine and you are the executor.
On each turn, the CLI returns JSON containing an instruction field. That instruction describes exactly one step (e.g. analyze, implement a phase, verify, update changelog, …). You must:
instruction carefully.goto command named at the bottom of the instruction to advance the state machine.instruction from the new JSON response and repeat.This is a loop. Do not stop after the first step. Keep looping — step → goto → next instruction → step — until a returned instruction tells you the workflow is finished. Only then should you report completion to the user.
The CLI owns the plan documents — plan.md, context.md, and research.md. Never read or write them with the Write, Edit, or Read tools — those bypass Spektacular and the configured plan directory. All plan document access goes through {{command}} plan file:
{{command}} plan file read <name>/<doc>.md — read a plan document from the plan store.{{command}} plan file write <name>/<doc>.md --from <source-path> — write a plan document into the plan store from a source file on disk. Stage the body under .spektacular/tmp/ first, then rm the scratch file after a successful write.This includes the edits the implement workflow makes to plan.md — ticking phase checkboxes and appending changelog entries. Read the document with plan file read, apply the change, and commit it with plan file write. Never edit a plan document in place with the Edit tool. Path arguments are plan-directory-relative document paths (e.g. my-feature/plan.md).
Plan name: $ARGUMENTS
If no plan name was provided, check .spektacular/state.json for an active plan under data.name. If one exists, ask the user whether they want to implement that plan, offering the option to name a different one. If no active plan is found, ask the user which plan to implement before proceeding.
The plan file must already exist at .spektacular/plans/<plan_name>/plan.md. If it does not, stop and tell the user to run {{command}} plan first.
Start the implement workflow by running:
{{command}} implement new --data '{"name": "<plan_name>"}'
This creates the state file automatically and returns the first instruction. From that point on, follow the loop above: do what the instruction says, then call {{command}} implement goto --data '{"step":"<next_step>"}' to get the next one. Do not invent step names — every instruction tells you the exact goto command to run next.