doccraft-closelisted
Install: claude install-skill alexpialetski/doccraft
# doccraft — close a story (transactional)
## When to use
- The user wants to **close / ship / finish / resolve** a specific story and
have the planning surface end up consistent — not just the story file.
- Work is moving to any **terminal** state: `done`, or a non-promoting
terminal like `done-no-promote`, `abandoned`, `absorbed`.
- The user pastes "mark P1.30 done", "close audio-engine/STR-0042", "we
shipped the retry flow", or similar.
Not for: authoring or re-scoping a story (use `doccraft-story`), a general
"what's unblocked / fix the queue" sweep with no specific story to close
(use `doccraft-queue-audit`), or recording a decision (use `doccraft-adr`).
Closing a story is a multi-file transaction. The story file is only step
one; the backlog row, the queue row, and (with epics) the parent epic table
all describe the same work and drift the moment one is updated without the
others. This skill owns the whole transition so a close never lands halfway.
## Configuration
Read `doccraft.json` at invocation. Every key below has a default in this
body, so a missing config file is a soft fallback, not an error.
- `docsDir` — root folder for all docs. Default: `docs`. Stories, queue, and
backlog live at `{docsDir}/stories/`, `{docsDir}/queue.md`,
`{docsDir}/backlog.md`.
- `story.status` — the allowed `status:` values. The **terminal** values are
whichever of these mean "no longer active work" — `done` always, plus any
the project adds (`done-no-promote`, `aban