rb-planning

To convert requirements into kanban cards, provide your design doc or plan text to the planner, which decomposes the input into epics and worker-ready task cards with EARS acceptance criteria and oracle exercise instructions.

Breaking down plans into commit-sized work items involves structuring epics for organization and dispatchable tasks for workers, marking dependencies when outputs must exist first, and routing architecture-sensitive decisions through a dedicated Plan path.

Writing testable acceptance criteria is best handled using EARS specs, which allow the board to gate promotion from backlog to todo by ensuring each task card has concrete file scope, verification steps, and a dedicated oracle block for the correct test surface.

Yes, creating task cards with dependency mapping requires the bl CLI, as it is used to generate cards directly on the ralph-ban board with correct specs, priorities, epic grouping, and self-contained worker instructions referencing relevant code patterns.

Yes, you can split architecture-sensitive tasks into separate spike and implementation cards, applying dependency-aware planning to mark tasks as blocked-by other tasks when specific outputs must exist before implementation work begins.

Manual task decomposition lacks design-first safety rails and EARS-ready acceptance specs, risking misaligned worker context and missing dependency mapping that automated board card generation provides for reliable orchestration execution.