One-click install
npx skills add https://github.com/avansover/mathcraft --skill speckit-tasks-avansover
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/avansover/mathcraft/tree/main/.claude/skills/speckit-tasks
Command: npx skills add https://github.com/avansover/mathcraft --skill speckit-tasks-avansover

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit-tasks turns scattered design artifacts (plan.md and spec.md, plus optional docs) into an immediately actionable tasks.md with a clear dependency order, so teams can implement features without guessing what to build next.

Core Features & Use Cases

  • Automated task planning from artifacts: Reads feature design inputs like plan.md and spec.md, optionally adding guidance from data-model.md, contracts/, research.md, and quickstart.md.
  • User-story organized execution: Produces phases per user story (P1, P2, P3, etc.), including independent test criteria and implementation tasks when available.
  • MVP-first delivery structure: Creates a practical incremental plan (typically only User Story 1 for MVP) plus a final polish phase.

Quick Start

Run the skill with your feature context so it generates an executable tasks.md for the feature based on the available design artifacts in your spec-kit project.

Frequently Asked Questions about speckit-tasks

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

FAQPage Schema
How do I generate dependency-ordered tasks from a spec-kit plan and spec?

To generate dependency-ordered tasks, this skill reads plan.md and spec.md to produce a tasks.md file. It organizes implementation into user-story phases with independent test criteria and file-path specific checklists.

What is the best way to create an MVP-first implementation plan from design artifacts?

Creating an MVP-first implementation plan involves processing your design artifacts to structure incremental delivery. This skill generates a phased plan focusing on User Story 1 for the MVP, followed by a final polish phase.

Does spec-kit task generation support extension hooks for before and after tasks?

Spec-kit task generation supports extension hooks by reading .specify/extensions.yml. It orchestrates before_tasks and after_tasks without evaluating hook conditions, honoring only enabled hooks during the tasks.md generation process.

Can I include optional design documents like data models and contracts when generating user stories?

You can include optional design documents like data-model.md, contracts, research.md, and quickstart.md. The skill reads these supplementary artifacts alongside plan.md and spec.md to enrich the generated user-story phased implementation plan.

How do user stories get organized into phases for implementation?

User stories are organized into sequential phases like P1, P2, and P3 within the generated tasks.md. Each phase includes independent test criteria and specific implementation tasks ordered by their dependencies.

What limitations exist when orchestrating extension hooks during task generation?

A limitation of extension hook orchestration is that hook conditions are not evaluated. The skill reads .specify/extensions.yml for before_tasks and after_tasks but strictly honors only enabled hooks without processing conditional logic.