From ctx
Executes a development plan step-by-step: loads plan, breaks into atomic verifiable steps, implements with per-step verification (build/test), checkpoints progress, final full check.
npx claudepluginhub activememory/ctx --plugin ctxThis skill uses the workspace's default tool permissions.
Take a plan (inline text, file path, or from the conversation)
Executes approved implementation plans from the plans directory phase by phase, reading files fully, implementing changes, verifying success criteria, and updating progress checkboxes. Use for structured plan execution.
Executes written implementation plans: loads and reviews critically, processes task batches with verifications, reports for feedback, iterates, completes via sub-skill.
Executes written implementation plans in controlled batches with review checkpoints, verification steps, and feedback pauses. Use when a plan exists requiring strict adherence and regression prevention.
Share bugs, ideas, or general feedback.
Take a plan (inline text, file path, or from the conversation) and execute it step-by-step with build/test verification between steps.
/ctx-brainstorm or plan mode produces an approved plan/ctx-brainstorm
first to refine it/ctx-implement
/ctx-implement path/to/plan.md
/ctx-implement (the plan from our discussion above)
Parse the plan into discrete, checkable steps. Each step should be:
Present the step list to the user for confirmation:
Implementation plan (N steps):
- [Step description] - verify: [check]
- [Step description] - verify: [check]
- ...
Ready to start?
For each step:
CGO_ENABLED=0 go build -o /dev/null ./cmd/ctxCGO_ENABLED=0 go test ./...Verify after every individual step before proceeding to the next.
After every 3-5 steps (or after a significant milestone):
After all steps complete:
make check or
CGO_ENABLED=0 go build && go test ./...)| Change type | Verification command |
|---|---|
| Go source code | CGO_ENABLED=0 go build -o /dev/null ./cmd/ctx |
| Test files | CGO_ENABLED=0 go test ./... |
| Templates/embeds | CGO_ENABLED=0 go build -o /dev/null ./cmd/ctx |
| Makefile | Run the new/changed target |
| Skill files | Build (to verify embed) + check live copy matches |
| Docs/markdown only | None required |
| Shell scripts | bash -n script.sh (syntax check) |
When a step fails verification:
If a step fails repeatedly (3+ attempts), stop and ask the user for guidance rather than thrashing.
Progress updates should be concise:
Step 1/6: Create ctx-next skill directory .......... OK
Step 2/6: Write SKILL.md template .................. OK
Step 3/6: Copy to live skill directory ............. OK
Step 4/6: Build to verify template embeds .......... OK
Step 5/6: Run tests ................................ OK
Step 6/6: Mark task in TASKS.md .................... OK
All 6 steps complete. Build and tests pass.
Step 3/8: Add
checktarget to Makefile Addedcheck: build auditafter theaudittarget. Verify:make check... build OK, audit OK. Result: PASS
"I'll implement the whole plan now" [makes all changes at once without verification] "Done! Everything should work."
(No step-by-step, no verification, no checkpoints: this defeats the purpose of the skill.)
Before starting, verify:
During execution, verify:
After completion, verify: