m-sdd-tasks

Normalize approved SDD plan steps into a structured tasks.md checklist.

2|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/mituso89/Spec-Driven-Development-toolkits --skill m-sdd-tasks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: m-sdd-tasks
Source: https://github.com/mituso89/Spec-Driven-Development-toolkits/tree/main/m-sdd-tasks
Command: npx skills add https://github.com/mituso89/Spec-Driven-Development-toolkits --skill m-sdd-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of converting an approved SDD plan into a structured tasks list, eliminating the manual process of task creation and management.

Core Features & Use Cases

  • Task Normalization: Converts bite-sized steps from an approved SDD plan into a well-structured checklist.
  • Task Derivation: Extracts tasks from plan content and file structure if specific steps are missing.
  • Task Tracking: Assigns stable IDs to tasks, ensuring each is independently testable and traceable to user stories and success criteria.
  • Single Source of Truth: Ensures the tasks.md file is the central reference for task status and progress.

Quick Start

Run the command 'm-sdd-tasks' after approving your plan.

Frequently Asked Questions about m-sdd-tasks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert an approved spec-driven development plan into a structured task list?

Spec-driven development plan conversion normalizes approved plan steps into a structured tasks.md checklist. It extracts tasks from plan content and file structure, assigns stable IDs, and ensures each task is independently testable and traceable to user stories.

What is task normalization in spec-driven development?

Task normalization in spec-driven development transforms bite-sized plan steps into a well-structured checklist. It assigns stable tracking IDs to extract tasks, ensuring a single source of truth for task execution and success criteria traceability.

Do I need an approved plan before deriving tasks for SDD?

Yes, task derivation requires an approved SDD plan as input. The Skill automates task extraction from the plan content and file structure, assigning stable IDs to create a single source of truth for task tracking and execution.

How are tasks tracked to ensure they remain traceable to user stories?

Task tracking assigns stable IDs to derived tasks, ensuring each is independently testable and traceable to user stories and success criteria. The tasks.md file serves as the central reference for task status and progress.

What is the best way to manage SDD task creation without manual entry?

Automating SDD task creation with a normalization script eliminates manual entry by extracting tasks from an approved plan and file structure. It generates a tasks.md checklist with stable IDs, maintaining a single source of truth for execution.

Can missing steps in an SDD plan still yield derived tasks?

Yes, task derivation extracts tasks from plan content and file structure even if specific steps are missing. This ensures a complete normalized checklist with stable IDs is generated from the approved SDD plan.