Loading...
Found 1 Skills
Break an implementation plan markdown file into a sequenced, dependency-annotated, checkbox-tracked task list saved as a sibling doc (e.g. `docs/<feature>-tasks.md`). Each task is annotated with the lower-numbered tasks it depends on (or marked dependency-free) and ordered topologically, so independent tasks can be implemented in parallel. The task list is the execution contract — each task is one logical commit that bundles the code change **and** the ticked checkbox together (never a separate "tick-only" commit). Use this whenever the user has an implementation plan (file like `docs/<thing>-plan.md`, an `## Implementation plan` section, or a freshly written design doc) and wants a step-by-step todo list to drive the build. Trigger on phrases like "break this plan into tasks", "make a task list", "generate the tasks doc", "turn this plan into checkboxes", "split this into steps I can implement one by one", or whenever a plan exists and the next move is execution — even if the user doesn't explicitly say "task list".