cookbook-start

Initializing a planning pipeline involves running the start command with your task description to generate a .cookbook/pipeline.json file. This state file tracks your progress across 38 guideline concerns, capturing phase details, step lists, and timestamps.

State management for an implementation pipeline uses a .cookbook/pipeline.json file to track phase progression and step completion. It ensures version consistency and validates arguments to safely guide developers through 38 structured guideline concerns.

Start an implementation phase by executing the start command with the implementation argument and a task description. The system determines the appropriate step range and creates the pipeline state file to track your implementation progress.

If state tracking already exists, the system includes safety guards that check for existing pipelines and ensure version consistency before proceeding. This prevents overwriting your current progress when you attempt to initialize a new session.

A limitation of this pipeline state management is its strict adherence to 38 specific guideline concerns. It requires passing argument validation and version checks, meaning custom steps outside the predefined list are not supported.

Pipeline initialization supports both planning and implementation phases. You specify the desired phase and task description when starting, and the system configures the state file and step list accordingly for that specific workflow.