tasks

Convert implementation plans into markdown task breakdowns with dependencies.

1|Updated Nov 22, 2025
One-click install
npx skills add https://github.com/gmliao/swift-state-tree --skill tasks-gmliao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tasks
Source: https://github.com/gmliao/swift-state-tree/tree/main/.agent/skills/SpecKit/tasks
Command: npx skills add https://github.com/gmliao/swift-state-tree --skill tasks-gmliao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams translate high-level implementation plans into a clear, ordered list of tasks with defined dependencies, enabling predictable progress and better collaboration.

Core Features & Use Cases

  • User story-based grouping: automatically organize tasks under each user story.
  • Dependency-aware sequencing: respect prerequisites and allow parallel work where possible.
  • Output-ready documentation: produce a markdown task document compatible with SpecKit/tasks workflow.

Quick Start

Provide your implementation plan reference (specs/FEATURE-ID/plan.md) and run the skill to generate specs/tasks.md.

Frequently Asked Questions about tasks

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

FAQPage Schema
How do I turn an implementation plan into actionable tasks?

Task breakdown organizes implementation plans by grouping tasks under user stories. It sequences dependencies to respect prerequisites while allowing parallel work, producing a markdown document for predictable progress.

How do I generate a task breakdown with dependencies from user stories?

Task breakdown organizes implementation plans by grouping tasks under user stories. It sequences dependencies to respect prerequisites while allowing parallel work, producing a markdown document for predictable progress.

Does task breakdown work with the SpecKit tasks workflow?

Task breakdown organizes implementation plans by grouping tasks under user stories. It sequences dependencies to respect prerequisites while allowing parallel work, producing a markdown document for predictable progress.

What is the best way to sequence development tasks based on prerequisites?

Task breakdown organizes implementation plans by grouping tasks under user stories. It sequences dependencies to respect prerequisites while allowing parallel work, producing a markdown document for predictable progress.

Can I use this task breakdown tool for software product development planning?

Task breakdown organizes implementation plans by grouping tasks under user stories. It sequences dependencies to respect prerequisites while allowing parallel work, producing a markdown document for predictable progress.