Context-driven development for Cursor: setup, spec, plan, implement, review, and revert.
Measure twice, code once.
| Command | Description |
|---|---|
/conductor-setup |
One-time project bootstrap |
/conductor-new-track |
Brainstorm, spec, plan (single track or programme mode) |
/conductor-implement |
Execute plan todos (depends_on, eligible picker, cleanup + continue options) |
/conductor-status |
Progress + eligible / parallel-ready / blocked tracks |
/conductor-revert |
Git-aware revert |
/conductor-review |
Review against guidelines, plan, spec |
/conductor-programme-review |
Review multi-track programme |
/conductor-validate-review |
Validate review findings against repo |
/conductor-prototype |
Decision-track spike on spike/<slug> branch |
From conductor/reviews/*.md → validate → split tracks → synthesis → implement in order (continue via explicit cleanup choices when unblocked).
Reference: docs/examples/remediation-programme-example.md
Deliverable is an OKF concept in a repo knowledge bundle:
| Scope | Bundle root | Example deliverable |
|---|---|---|
| Domain package | <pkg>/knowledge/ |
<pkg>/knowledge/decisions/<slug>.md |
| Repository | knowledge/ |
knowledge/decisions/<slug>.md |
Workflow: /grilling → /research → /conductor-prototype → /grill-with-docs
See OKF v0.1.
**/knowledge/index.md bundlesknowledge/ or domain <pkg>/knowledge/ beside codetemplates/knowledge/bundle-placement-guide.mdconductor/context/, conductor/specs/, conductor/plans/, conductor/reviews/knowledge/ or <pkg>/knowledge/ in the repositoryConductor from gemini-cli-extensions/conductor. OKF from Google Cloud OKF spec. Engineering skills from mattpocock/skills (MIT).
Output style: Base rules come from i-have-adhd (skills/i-have-adhd/SKILL.md). Conductor-only command formats live in templates/output-style.md. Install both plugins from the marketplace; run /i-have-adhd for session-wide formatting on non-Conductor work.