doccraft-configlisted
Install: claude install-skill alexpialetski/doccraft
# doccraft — config
## When to use
- **After `doccraft init`**: run Analyse mode to tailor the freshly scaffolded
`doccraft.json` to the project's actual subsystems, surfaces, and themes.
- **Any time you want to add or change a config field**: run Edit mode with a
plain-English request ("add slice:billing", "set maxStoryFiles to 10").
- **Before invoking `doccraft-story` or `doccraft-queue-audit`** when skill
output references unfamiliar vocabulary — the config is probably stale.
## Schema
The full JSON Schema for `doccraft.json` is embedded below. Use it for
validation in Edit mode instead of calling any CLI.
```json
{{DOCCRAFT_CONFIG_SCHEMA}}
```
## Modes
### Analyse mode (no specific field requested)
1. Read the project tree: directory names, `package.json` scripts/workspaces,
git remote, conventional-commit scope history if a `.git/` dir is present.
2. Propose values for each key group with one sentence of reasoning per group:
- `story.areas` — one entry per logical subsystem (aligns with commit scopes).
- `story.slices` — one entry per user-facing product surface; `[]` for
purely technical tools.
- `story.themes` — recurring cross-cutting concerns from the tree.
- `story.id.tiers` — e.g. `[p0,p1,p2]` for most projects; more tiers only
when severity levels are meaningfully distinct.
- `queueAudit.scale` — lower thresholds for small repos, higher for large.
- `sessionWrap.capture` — disable categories for folder trees the proje