planning-workflows

1# Planning Workflows (spec / no-spec)
2 
3This skill standardizes how to choose and execute planning modes using local slash commands.
4 
5## When to use this skill
6 
7Use this skill when the user:
8 
9- wants a full spec workflow before implementation
10- wants to skip spec and execute directly for small scoped tasks
11- asks how to decide between spec vs no-spec
12 
13## Source of truth
14 
15- `references/source-commands.md`
16 
17## Decision rules
18 
19- Prefer **spec** when work is new/complex, cross-module, risky, or acceptance criteria are unclear.
20- Prefer **no-spec** when work is small, low-risk, well-scoped (docs/config/simple fixes).
21 
22## Execution rules
23 
241. Read the matching command template from `references/source-commands.md`.
252. Follow it as a phase gate workflow:
26   - do not skip required confirmations when running spec mode
27   - keep scope tight when running no-spec mode
283. Keep artifacts in the repo conventions (e.g. `specs/<name>/...`) when spec is selected.
29   - `specs/` is a local-only directory in this repo: never `git add` it (it is gitignored). Sync / retrieve it through the private archive described in `AGENTS.md` section `<internal_dirs>`.
30 
31## Command mapping
32 
33See `references/command-catalog.md`.