doccraft-session-wraplisted

# doccraft — session wrap (propose docs artifacts) ## When to use - The user **invokes this skill** or asks to **wrap this session** / **propose docs artifacts** / **what should we capture** / **summarize this discussion into docs** from the **current conversation**. - Typical triggers: architecture or product discussion concluded (or deferred with rationale), research synthesis, or reprioritisation — **not** every casual Q&A. **Default:** propose artifacts **only if necessary**. Do not invent work to document. NEVER write files unless the user explicitly asks to create or update them in the same turn. Propose drafts only. ## Configuration Read `doccraft.yaml` at invocation. The `sessionWrap.capture:` block controls which artifact categories are in scope for this project — skip rows entirely in the proposals table when their category is disabled. Relevant keys: - `docsDir` — root folder for all docs. Default: `docs`. All artifact paths below are relative to `{docsDir}/`. - `sessionWrap.capture.research` — default `true`. - `sessionWrap.capture.reference` — default `true`. - `sessionWrap.capture.business` — default `false`. Projects that track strategy under `{docsDir}/business/` set this to `true`; most projects leave it off. If `doccraft.yaml` is missing, apply the defaults above. The `ADR`, `Story`, and `Backlog / queue` categories are always in scope — they are the load-bearing set. ## Package routing <!-- doccraft:packages --> <!-- /doccraft:packa