work-capturelisted

Quickly capture a bug, feature idea, improvement, annoyance, tech-debt item, or security concern into the project's requests.md intake file, without starting a planning session. Use when someone says "note this down", "log this", "capture this", "add this to the backlog", "remember this for later", "I noticed a bug", "I had an idea", "can you add a request for", "flag this for later", or otherwise mentions something in passing that they want recorded rather than fixed now. Also use proactively at the end of a session when a real defect or improvement was noticed but deliberately left unfixed. Works on any project set up with the work-management model; discovers the project from its manifest rather than assuming a location. Do NOT use for refining requests, proposing release scope, or closing out a release — those are the /work-plan command.
martynjsimpson/workManagementClaudePlugin · ★ 0 · AI & Automation · score 72

Install: claude install-skill martynjsimpson/workManagementClaudePlugin

# Work capture Append a single request to the project's intake file and stop. Capture is deliberately cheap: the point is to record the thought before it is lost, not to refine it. ## Resolve configuration Follow `${CLAUDE_PLUGIN_ROOT}/skills/work-model/references/config-resolution.md` to locate `<paths.work>/project.yml`. If no manifest is found, do not create one and do not write a request anywhere. Say that this project is not set up for work capture and that `/work-init` will set it up. Offer to hold the note in the conversation meanwhile. **Stale schema — proceed anyway, with one line of warning.** This skill has the only exemption from the compatibility gate. If `model_version` is older than the supported version, capture still runs, provided the fields it reads are present and well-formed: `paths.work`, `ids.*`, `taxonomy.request_types`, `taxonomy.priorities`. Those have not moved between schema eras. Mention the stale schema once, in one sentence, and name `/work-init --upgrade`. Then get on with the capture. The reasoning: refusing here loses the note, and the note is the whole point — whereas the schema can be fixed at any time. If a field capture actually needs is missing or malformed, stop like any other command. ## Write the request Read the tail of `<paths.work>/requests.md` to find the highest existing request ID, then allocate the next one using `<ids.request_prefix>` and `<ids.pad>`. Do not reuse an ID, even if a gap exists — gaps usually mean somethi