Break down system design documents into prioritized development tasks with dependencies.
npx skills add https://github.com/ab300819/skills --skill devdocs-dev-tasks
Please help me install this Agent Skill. Skill: devdocs-dev-tasks Source: https://github.com/ab300819/skills/tree/main/devdocs-dev-tasks Command: npx skills add https://github.com/ab300819/skills --skill devdocs-dev-tasks
This Skill breaks down a comprehensive system design into a structured list of executable development tasks, enabling clear sprint planning and task distribution across modules.
Ask the skill to generate a task breakdown from your system design documents. For example: "Dev tasks for the sprint based on docs/devdocs/01-requirements.md, docs/devdocs/02-system-design.md, and docs/devdocs/03-test-cases.md".
High-intent search queries and answers about installing and using this skill.
To break down a system design into development tasks for sprint planning, use an automated task extraction tool that consumes pre-existing requirements, system design, and test case documents to output a prioritized, executable task list with mapped dependencies.
Development tasks for sprint backlog integration should be formatted as a structured markdown file containing prioritized T-IDs, such as T-01 to T-04, with associated F-XXX and AC-XXX mappings to ensure clear traceability across project modules.
Yes, you can generate a prioritized task list directly from existing requirements and test case documents by processing 01-requirements.md, 02-system-design.md, and 03-test-cases.md together to automatically extract concrete development tasks with dependencies.
Before generating executable development tasks, you need to prepare three pre-existing markdown documents: 01-requirements.md, 02-system-design.md, and 03-test-cases.md. These provide the foundational design and test artifacts required for accurate task breakdown.
Task dependencies and feature mappings are handled by assigning unique task identifiers like T-01 and mapping them directly to associated feature identifiers F-XXX and acceptance criteria AC-XXX, ensuring structured traceability throughout the sprint planning process.
Yes, the task breakdown output supports optional split files when the development task list is too large. It primarily outputs a main file at docs/devdocs/04-dev-tasks.md but can divide the task distribution across modules as needed.
jpoutrinGenerate agent-ready prompts from task specification files.
DavidsonGomesCoordinate sprint planning, task assignment, and status reporting for cross-functional teams.
kardelitaituStructure tasks, estimates, and roadmaps for project planning workflows.
GGPromptsBreak down epics and features into backlog tasks with dependencies.
