capture-work

You can capture deferred work items by triaging them into structured build or shaping queues within a workspace.toml file. This ensures tasks persist across agent sessions, preventing important follow-on work from being lost in chat history.

Build and shaping tasks are distinct queue classifications based on task intent within workspace.toml. Build items represent actionable implementation work, whereas shaping items cover research or design exploration needed before a task can be executed.

To capture follow-up tasks, provide a bulleted list of unstructured items to the assistant. The skill automatically classifies them as build or shaping tasks and derives dependency edges to maintain a logical, machine-readable project backlog.

Yes, the task triage process automatically infers hard dependencies between items to ensure logical sequencing. By deriving dependency edges, it maintains a structured project backlog where tasks are properly ordered for execution.

Yes, you can queue deferred remediation items directly into a workspace.toml file. The skill operates on lists of remediation items, classifying them into structured queues to ensure they are captured and persisted for future cycles.

You need a structured workspace.toml file when you want to prevent fragmented task tracking and ensure work items survive beyond a single agent session. It provides a durable, machine-readable format for maintaining build and shaping queues.