doccraft-storylisted

# doccraft — planning stories ## When to use - Creating a new story in `{{DOCS_DIR}}/stories/`. - Updating status, acceptance criteria, tags, or `openspec` on an existing story. - When closing a story: update `{{DOCS_DIR}}/queue.md` and the **Status** column in `{{DOCS_DIR}}/backlog.md`. See **Workflow reminders** for queue-audit invocation rules. ## YAML frontmatter (required fields) Use valid YAML between `---` delimiters at the top of the file. Every field marked **yes** MUST be present — do not omit any. If the user has not provided enough information to fill a required field, ask — NEVER guess. | Field | Required | Values / notes | |-------|----------|----------------| | `id` | yes | Stable, unique id across all stories. `P0.3` when aligned to `{{DOCS_DIR}}/backlog.md`, or a slug like `story-2026-001`. MUST be unique — verify before writing. | | `title` | yes | Short human-readable title. | | `status` | yes | One of the values in `story.status` config (default: `todo` \| `in_progress` \| `done`). **Manual** updates only. | | `impact` | yes | One of the values in `story.impact` config (default: `H` \| `M` \| `L`). If the user does not specify, ask. | | `urgency` | yes | One of the values in `story.urgency` config (default: `now` \| `soon` \| `later`). If the user does not specify, ask. | | `tags` | yes | YAML list of **prefixed** strings (`area:`, `slice:`, `theme:`) from the tag vocabulary below. If nothing fits and the label will recur, extend the vocabulary in