unit-planner

To generate a UNITS.csv execution contract, instantiate or update the file from a selected pipeline and units template. This translates the pipeline definition into structured tasks, defining dependencies and acceptance criteria for workspace execution.

Managing task dependencies and acceptance criteria in a CSV workspace involves maintaining a UNITS.csv file that cross-references CHECKPOINTS.md for consistency. This ensures structured task management accurately reflects pipeline requirements and execution contracts.

Yes, you can update an existing UNITS.csv file to expand your research scope. The process incorporates new scope, dependencies, or acceptance criteria into the current execution contract while adhering to CSV formatting standards.

Yes, the unit planner requires cross-referencing with CHECKPOINTS.md. This consistency check ensures the generated execution contracts and task dependencies in UNITS.csv accurately reflect the selected pipeline requirements.

A structured CSV format for pipeline execution contracts is needed to define tasks, dependencies, and expected outputs clearly. Adhering to CSV formatting ensures accurate translation of pipeline definitions into manageable workspace units.

You need to instantiate a UNITS.csv file when initializing or expanding research scopes requiring structured task management. This creates the initial execution contract outlining all tasks and their dependencies from a pipeline.