# AI Slash Commands Workflow

These commands align with OpenSpec and can be used with Claude Code, Codex, Copilot, or similar assistants. Include them in PR descriptions, issues, or comments.

Core commands
- `/propose <title> [scope=spec|infra|policy] [labels=a11y,compliance] [assignees=@owner] [model=claude|gpt|copilot]`
  - Scaffolds `openspec/changes/YYYY-MM-DD-title/proposal.md` from the template
- `/review areas=accessibility,compliance,security,mobile,web,backend`
  - Summons focused review checklists and routes to domain owners
- `/apply spec=openspec/specs/<target>.md [pr=<link>]`
  - Moves accepted sections into the target spec; opens/updates PR
- `/archive reason="accepted into <spec>" link=<PR>`
  - Finalizes the change and records traceability

Helpful commands
- `/assign @user1 @user2` — set reviewers/owners
- `/estimate 5d` — initial t‑shirt or time estimate
- `/plan` — generate a milestone/task breakdown tied to the spec
- `/generate tests scope=<module>` — create or update test skeletons per acceptance criteria

Usage examples
- Start a feature: `/propose Community Forum MVP scope=spec labels=a11y,compliance,security model=claude`
- Ask for targeted review: `/review areas=accessibility,compliance`
- Apply after approval: `/apply spec=openspec/specs/feature-forum.md pr=<link>`
- Archive the change: `/archive reason="merged" link=<PR>`

Agent notes
- Keep assistants grounded in `openspec/project.md` guardrails.
- When generating code, require an approved spec link in the PR description.