speckit-tasks

Name: speckit-tasks
Availability: InStock
Author: yarelicamacho

Generate dependency-ordered tasks.md files from feature plans and specs.

Updated May 22, 2026

Search Tags:#planning #software engineering #markdown #user stories #tasks #spec-kit #dependency ordering

Ready to run

npx skills add https://github.com/yareliCamacho/AppCalendario --skill speckit-tasks-yarelicamacho

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/yareliCamacho/AppCalendario/tree/main/.cursor/skills/speckit-tasks
Command: npx skills add https://github.com/yareliCamacho/AppCalendario --skill speckit-tasks-yarelicamacho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns feature plans, specs, and supporting design notes into a clear, dependency-ordered task list so teams can move from idea to execution without manually structuring work.

Core Features & Use Cases

Breaks a feature into setup, foundational, user story, and polish phases.
Maps tasks to priorities, contracts, data models, and research artifacts when they exist.
Produces checklist-formatted tasks that are ready for direct implementation and review.
Use it when you need a consistent tasks.md for a spec-kit project, especially for incremental delivery and independently testable stories.

Quick Start

Ask the skill to generate a tasks.md file from the available spec, plan, and supporting documents in the current feature folder.

Frequently Asked Questions about speckit-tasks

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

FAQPage Schema

How do I generate a dependency-ordered tasks.md file from feature specs?▼

A tasks.md file for incremental delivery organizes work into setup, foundational, user story, and polish phases. It structures feature plans into checklist-formatted tasks mapped to story dependencies and data models for direct implementation.

How do I break feature specs into independently testable user stories?▼

Break feature specs into independently testable user stories by mapping tasks to story dependencies and tracing optional contracts. This validates specific testable items throughout incremental delivery phases.

Do I need a spec-kit project to organize work into implementation phases?▼

Yes, a spec-kit project is required to organize work into implementation phases. The task generation applies specifically to spec-kit projects, mapping feature plans into setup, foundational, user story, and polish phases.

What is the best way to map dependencies for incremental software delivery?▼

The best way to map dependencies for incremental software delivery is using story-based dependency mapping to order tasks. This ensures foundational work is completed before user story tasks, producing a structured checklist.

Can I trace data models and contracts when generating task lists?▼

Yes, you can trace data models and contracts when generating task lists. The process maps tasks to priorities, contracts, data models, and research artifacts when they exist in the feature folder.