Commands¶

All commands use your project's prefix (set at wk init time). Examples below use wk as the prefix.

/wk-check¶

Full hygiene sweep. Runs the guardian against current state, then the glossary steward for terminology consistency.

/wk-check [description of proposed change]

Without arguments: read-only check of the codebase against spec. With arguments: evaluates a specific proposal.

Full gate chain with implementation handoff.

/wk-impl <module_name>

Runs: guardian -> spec-synthesizer -> test-author -> handoff. Stops at first failure.

Guardian gate + implementation brief, without the handoff step.

/wk-spec <module_name>

Useful for reviewing what would be implemented before committing.

Scans for spec-code divergence after spec changes.

/wk-drift

Reports BREAKS (must fix), NEEDS UPDATE (should fix), and NO ACTION items. Each finding includes a FIX instruction.

Interactive ADR authoring. Asks for context, drafts the ADR, propagates through spec.

/wk-decision <title>

Dependency upgrade audit. Detects the package ecosystem, checks for updates, tests compatibility.

/wk-deps

Roadmap burn-down and phase progress.

/wk-status

Architect-level review of spec quality across all dimensions.

/wk-review-spec

Fan a manual spec edit across all downstream documents.

/wk-propagate <doc>

Lists all available commands with descriptions (reads them dynamically from command file frontmatter).

/wk-help