Generate dependency-mapped task lists from spec-kit plan.md and spec.md files.
npx skills add https://github.com/juvenal/openrender --skill speckit-tasks-juvenal
Please help me install this Agent Skill. Skill: speckit-tasks Source: https://github.com/juvenal/openrender/tree/main/.qwen/skills/speckit-tasks Command: npx skills add https://github.com/juvenal/openrender --skill speckit-tasks-juvenal
This Skill eliminates the manual effort of translating high-level implementation plans into structured, executable task lists, reducing planning overhead and ensuring alignment with user story priorities for development teams.
Use the speckit-tasks skill to generate a structured task list for your current feature implementation plan.
High-intent search queries and answers about installing and using this skill.
To break down an implementation plan into actionable tasks, parse standard spec-kit project documents like plan.md and spec.md to generate a dependency-mapped, checklist-formatted tasks.md file. This aligns ordered tasks with user story priorities and identifies parallel execution opportunities.
Generate a tasks.md file from user stories by applying dependency mapping to spec-kit structured projects. The process extracts requirements from plan.md and spec.md, outputting checklist-formatted tasks with independent test criteria for each user story.
Dependency mapping in task generation identifies relationships between implementation steps, creating ordered task lists that highlight parallel execution opportunities. It ensures tasks within a tasks.md file align with user story priorities and constraints extracted from spec-kit documents.
A data-model.md file is not required to generate dependency-mapped task lists. The skill parses standard spec-kit documents including plan.md and spec.md, while treating supporting design documents like data-model.md and interface contracts as optional inputs.
Yes, you can use spec-kit task generation for projects without interface contracts. The skill parses plan.md and spec.md as required inputs, while interface contracts in the contracts directory are optional supporting documents for generating the tasks.md file.
Generated task lists align with user story priorities by extracting requirements directly from spec-kit structured plan.md and spec.md files. If alignment fails, verify that your implementation plan explicitly defines user stories and that the supporting spec-kit documents contain clear constraints.
ApothecaryManGenerate a dependency-ordered tasks.md file from spec-kit design artifacts.
CongtrinhhGenerate a dependency-ordered tasks.md from plan.md and spec.md.
lofidonut3Analyze spec.md, plan.md, and tasks.md for cross-artifact inconsistencies.
fhltaGenerate dependency-ordered tasks.md files from spec-kit design artifacts.
