What problem does it solve? Teams lose track of task context when plans, execution state, and review findings live in scattered notes. This Skill standardizes every task as a Task Bundle — a directory under docs/tasks/ containing plan.md, state.md, and review.md — so goals, progress, and conclusions stay consistent and auditable. ## Core Features & Use Cases - Standardized Task Structure: Each task gets a task-id (YYYY-MM-DD-<seq>-<kebab-description>) and three files: plan.md for goals and acceptance criteria, state.md for current step and blockers, and review.md for findings and conclusions. - State Transition Rules: Every status change updates the state.md frontmatter, appends a row to the state history table, and refreshes the last_checkpoint timestamp, following the Failure FSM protocol. - Template-Based Creation: Copy plan.md.tpl, state.md.tpl, and review.md.tpl from the templates directory and replace placeholders to bootstrap a new bundle. - Use Case: After running /workflows:plan, create a Task Bundle for the new feature, link the plan file, update state.md during /workflows:work, and fill review.md after /workflows:review. ## Quick Start Create a new Task Bundle for the login-refactor task by generating a task-id, copying the three templates into docs/tasks/, and filling in the plan frontmatter.
