pipeline

Invoke the pipeline orchestrator without arguments; it scans docs/devdocs/ to detect your project stage and asks at most 2-3 questions to route you. You can also call entries directly, such as init for new projects or feature for additions.

Init runs the full chain from requirements through development for new projects. Feature adds functionality to existing keel projects with adaptive Lite/Standard/Deep depth. Bugfix uses a fast path for simple bugs or falls back to dev-tasks and dev-workflow for complex ones.

Stages communicate only through yaml-summary-v1 envelopes containing status, output file paths, and new ID lists. Each sub-agent reads prerequisite documents from docs/devdocs/ itself; the orchestrator never inlines full document contents.

The orchestrator stops at that stage, displays blockers and pending items, and suggests the next recommended skill. It never treats partial as complete, since partial usually means a milestone awaits user verification.

Use dev-flow when you have no keel documentation and want to develop directly from a plan or task description. The pipeline is for keel-governed projects with numbered requirements, design, and traceability documents.