spec-driven

A spec-driven task workspace creates a centralized nanospec directory to store shared specs, plans, and tasks for multi-skill collaborations. It provides a unified container with outputs and assets folders to prevent fragmented documentation across collaborative agents.

Alignment tracking uses an alignment.md file within the nanospec directory to capture changes, conflicts, and deviations. This ensures all collaborative agents reading and writing shared task documents remain synchronized throughout the project lifecycle.

Yes, you can use a spec-driven task workspace for agile development without a rigid workflow. The system allows any skill to read and write shared spec, plan, and task documents dynamically, making it ideal for flexible product planning and research projects.

The best way to centralize documentation is to establish a unified spec-driven task directory. This creates a nanospec container that holds shared output files and tracks alignment, preventing missed updates across collaborating agents.

No specific dependencies are required to create a nanospec container for cross-skill collaboration. The workspace operates independently to establish shared storage for spec, plan, task, and alignment files, allowing any skill to integrate without external tools.