speckit-tasks

Generate structured implementation tasks from spec and plan artifacts.

95|39|Updated Dec 15, 2025
One-click install
npx skills add https://github.com/liuminxin45/auto-podcast --skill speckit-tasks-liuminxin45
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/liuminxin45/auto-podcast/tree/main/.agents/spec-kit/skills/speckit-tasks
Command: npx skills add https://github.com/liuminxin45/auto-podcast --skill speckit-tasks-liuminxin45

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns spec and plan artifacts into a clear, execution-ready tasks.md so teams can move from design to implementation without missing validation, review, or closure steps.

Core Features & Use Cases

  • Task plan generation: Builds bounded implementation slices, validation steps, and handoff tasks from existing feature artifacts.
  • Workflow-aware output: Preserves review notes, progress tracking, lessons capture, and acceptance closure in the right delivery order.
  • Use case: A product engineer has a spec, plan, and research notes for a new feature and needs a structured task list that an implementer can follow safely from start to finish.

Quick Start

Use the speckit-tasks skill to generate a complete tasks.md from the available spec and plan artifacts in this feature directory.

Frequently Asked Questions about speckit-tasks

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

FAQPage Schema
How do I turn feature specifications into an executable task plan?

To turn feature specifications into an executable task plan, this Skill generates a structured tasks.md file from your spec and plan artifacts, creating bounded implementation slices and validation steps for delivery-ready execution.

What is the best way to structure implementation tasks for safe feature delivery?

Structuring implementation tasks for safe feature delivery requires bounded validation, progress tracking, review artifacts, and closure gates. This ensures implementation slices remain safe and reviewable throughout the workflow.

Can I generate a task plan for bugfix and migration scenarios, or only new features?

You can generate a task plan for bugfix, migration, and new-feature planning scenarios. The workflow-aware output preserves review notes, progress tracking, and acceptance closure in the correct delivery order for each scenario.

How do I ensure my task list includes validation and review steps for implementation?

To ensure your task list includes validation and review steps, generate your tasks.md from existing feature artifacts. The output builds bounded implementation slices, validation steps, and handoff tasks directly into the delivery sequence.

Do I need existing spec and plan artifacts to generate a delivery-ready task list?

Yes, you need existing spec and plan artifacts in your feature directory to generate a delivery-ready task list. The Skill processes these research notes and design documents to produce a structured plan an implementer can safely follow.

Why does my feature implementation lack clear closure gates and reviewable slices?

Your feature implementation lacks clear closure gates and reviewable slices without a structured task plan. Generating tasks.md from spec artifacts applies bounded validation and progress tracking to keep implementation slices safe and reviewable.