split-to-tasks

To convert a Markdown implementation plan into Trello-style task cards, you use an automated process that splits the plan into self-contained cards. It generates a kanban.json file serving as the single source of truth for execution tracking.

Limiting story points per Kanban card works by enforcing a maximum of four story points and approximately four hours per generated card. This constraint ensures each task remains self-contained and manageable for execution tracking.

You need a Markdown implementation plan file to generate a Kanban board package. The process outputs kanban.json, state.json, progress.md, cards_catalog.md, and trello_quality_gate.json for tracking and review.

Yes, you can automatically track progress using a generated kanban.json file. The package derives state.json and progress.md from the Kanban source of truth to reflect current execution status across the task cards.

The best way to split large project plans into smaller execution tasks is to enforce size and duration constraints during generation. Limiting cards to four story points and four hours creates self-contained tasks tracked in a Kanban board.

Limitations of automating task card generation include strict duration and size constraints, capping cards at four hours and four story points. Plans requiring larger continuous task blocks may not fit this structured Kanban execution model.