parallel-task-format

Parallel-task-format provides a compact YAML specification for defining task scope, agent assignments, dependencies, and contracts. Structure task files with required frontmatter fields (id, component, wave, deps, blocks, agent, contracts) and three-part scope sections (CREATE, MODIFY, BOUNDARY) to coordinate work across teams.

Task files use YAML with mandatory frontmatter defining unique task IDs, component names, wave numbers, dependency rules, blocking relationships, agent assignments, and contract references. The format enforces validation rules including no circular dependencies and proper agent designation.

Yes. The format includes wave-dependency rules and a blocks field to define task relationships. Validation criteria enforce unique IDs and detect circular dependencies, ensuring tasks execute in the correct sequence without conflicts.

Each task file includes an agent field in the frontmatter to specify which agent owns the task. The format validates proper agent assignment as part of the task specification schema.

Create task files under the parallel/TS-XXXX-slug/tasks/ directory structure. Use the YAML template format with proper naming conventions to maintain consistency across your parallel task organization.

The validation criteria enforce that circular dependencies are not allowed. The format includes built-in checks to reject task specifications that would create circular dependency chains.