Commands¶
Slash-command definitions live as flat .md files under src/apothem/commands/. The
canonical set is the five-stage plan-suite pipeline.
| Command | File | Description |
|---|---|---|
/plan-spec |
src/apothem/commands/plan-spec.md |
Refine unstructured content into spec-grade prose |
/plan-generate |
src/apothem/commands/plan-generate.md |
Materialise a plan suite from prose / requirements |
/plan-review |
src/apothem/commands/plan-review.md |
Forensic audit with scorecards |
/plan-execute |
src/apothem/commands/plan-execute.md |
Execute a phase with quality gates |
/plan-status |
src/apothem/commands/plan-status.md |
Read-only progress report |
Frontmatter contract¶
Every command file carries the canonical nine-key frontmatter:
---
name: <slash-command name without leading slash>
description: <one-line role>
type: command
argumentHint: <optional placeholder for the slash-command argument>
allowedTools: <optional whitelist>
disallowedTools: <optional blacklist>
model: <optional model hint>
agentModel: <optional agent-tier model hint>
version: <semver>
---
The validator's frontmatter-cohort check (Command branch) verifies the
contract on every command file.
Authoring discipline¶
- Self-contained workflow. Every command's body lists the workflow as numbered steps so the assistant can execute from a cold start.
- Bindings block. Every command ends with the canonical five-direction Bindings block.
- Domain language only. No plan-internal references in the bodies.