capture-work

# Skill: capture-work Classify-then-triage entry point for adding work to `workspace.toml`. Given a bulleted or numbered list, `capture-work` classifies each item as `[build]` or `[shape]`, derives spec paths, infers real dependencies, prioritizes and groups the items, and writes them to the right destination — each entry carrying a comment rich enough that a cold-start session can write the full spec without revisiting this one. `capture-work` writes `workspace.toml` only. It never creates spec files, and it never invents a dependency. The user reviews the complete proposed change before anything is written. ## When to invoke - A session produced a list of "things we should do later" — deferrals, follow-ons, recommendations, remediation items — and you want them queued. - The items are concrete enough to name, even if not yet fully shaped. If the input is unstructured external prose that needs shaping into a product brief, use `author-brief`. If it is an already-written brief to decompose into specs, use `receive-brief`. If you just want to see what is already queued, use `workspace-status`. ## The destinations this skill writes to `capture-work` appends only to the destinations it owns. For anything else it *suggests* the right home and defers the write to the owning skill. **Build items (`[build]`):** 1. **An active initiative's `[work].queue`** — well-shaped, ready build work scoped to an active initiative. If more than one initiative is `active`, ask whi...