doccraft-queue-auditlisted
Install: claude install-skill alexpialetski/doccraft
# doccraft — queue, dependency audit, and parallel waves
## When to use
- After **adding** a story, changing **`depends_on`** / **`id`**, or
reshuffling priorities and you want a sanity check on `{{DOCS_DIR}}/queue.md`.
- The user asks "what can I work on next", "what's unblocked",
"sanity-check the queue", or similar pick-next / dependency questions.
- The user asks for **parallel-ready batches** ("what can I run in
parallel?") — see **Parallel waves** below.
- The user pastes the suggested follow-up block from `doccraft-story`.
Not for: authoring a new story (use `doccraft-story`), recording a
decision (use `doccraft-adr`), proposing artifacts from a chat thread
(use `doccraft-session-wrap`), or closing one specific story end-to-end
(use `doccraft-close` — it does the status/backlog/queue/epic transition,
then defers to this skill's reconcile invariants).
## Configuration
Read `doccraft.yaml` at invocation. Every key below has a default in the
rest of this body so a missing config file is a soft fallback, not an error.
Relevant keys:
- `docsDir` — root folder for all docs. Default: `docs`. Stories, queue,
and backlog are at `{docsDir}/stories/`, `{docsDir}/queue.md`,
`{docsDir}/backlog.md`.
- `queue.tables.suggestedOrder`, `queue.tables.platformSpikes` — the
heading text this skill uses to find the two tables in the queue file.
Defaults: `Suggested order`, `Platform spikes`. Rename in config if
the project uses different headings; the skill matches on