mspec-tasks

Automating mspec task generation produces a tasks.md file containing anchor blocks that link to spec documents and FR-IDs. It requires existing mspec status and design.md files to provide the necessary context for the workflow.

Anchor blocks in a tasks.md file are Markdown elements that link generated tasks directly to mspec spec documents and FR-IDs. They are needed to maintain traceability between development tasks and specification requirements.

Yes, a design.md file is required to generate tasks.md for mspec. The skill requires both mspec status and design.md files as context inputs to accurately produce the task list with proper anchor blocks.

Integrating task generation into continuous integration involves running the mspec tasks command during the workflow. This automatically generates the tasks.md file, allowing the pipeline to proceed with the development process seamlessly.

The best way to create a tasks.md file linking to FR-IDs is to use an automated mspec workflow tool. It generates the Markdown file with anchor blocks natively, ensuring accurate links to spec documents without manual formatting errors.

Mspec task generation fails without mspec status context because the generation logic relies on the current workflow state and design.md content to map anchor blocks to the correct spec documents and FR-IDs.