plan-work-items

Use this skill by providing an implementation plan path or feature name to break it into atomic, verifiable work items. It outputs a single work-items.md file in the target plan folder for tracking and execution.

The best way to convert a project plan into independently-grabbable tasks is to use an automated task-breakdown tool that writes atomic, verifiable work items to a single work-items.md file, ensuring a unified artifact for execution and tracking.

Yes, you can generate a single work-items.md file from existing plan documentation. The process ensures a deterministic, single-output work-items file that references plan decisions and artifacts within the plan's folder.

Yes, task-breakdown automation supports referencing plan decisions and artifacts. It converts a trusted implementation plan into atomic work items while ensuring references to the original plan decisions are maintained in the output file.

You need to convert a plan into atomic work items for ticketing when you require plan-to-workflow handoffs, providing self-contained, granular units ready for downstream development, assignment, and verifiable testing.