Task Breakdown

Tasks should be small enough to test.

Pipeline

Intent

Name the problem and make success checkable.

Shape

Plan, seams, and ticket-sized work.

Build

Edit, test, debug, and review the repo.

Ship

Assemble, publish, and learn from the live app.

Enters

Architecture + plan.

Exits

Ticket-sized tasks.

What happens

The plan is sliced into repository-sized jobs.

Huge tasks hide failures.

Planning agent, PM agent, human.

Agents can split work; humans keep slices vertical.

Encyclopedia entries that operate at this stage of the pipeline.