spec-tasks

Generate structured task lists from spec.md and plan.md design artifacts.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/eavichay/mycli --skill spec-tasks-eavichay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-tasks
Source: https://github.com/eavichay/mycli/tree/main/.cursor/skills/spec-tasks
Command: npx skills add https://github.com/eavichay/mycli --skill spec-tasks-eavichay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of translating high-level feature specifications into granular, execution-ready task lists that are organized by user story and priority.

Core Features & Use Cases

  • Automated Task Generation: Parses design artifacts like plan.md and spec.md to create a structured tasks.md file.
  • Execution Metadata: Initializes a dual-execution loop (SYNC/ASYNC) to track task progress and quality gates.
  • Use Case: When starting a new feature branch, use this Skill to automatically generate a checklist of implementation tasks, test requirements, and parallelization opportunities based on your existing project documentation.

Quick Start

Run the spec-tasks skill to generate a new tasks.md file for the current feature branch based on the existing design documents in the repository.

Frequently Asked Questions about spec-tasks

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

FAQPage Schema
How do I generate actionable task lists from project specification documents?

Generating actionable task lists from specification documents requires parsing planning artifacts like plan.md and spec.md to map user stories into granular, testable tasks ordered by dependencies and priority.

What is dependency-ordered task generation for feature implementation?

Dependency-ordered task generation is the process of mapping high-level user stories into execution-ready tasks organized by priority and dependencies, classifying each with SYNC or ASYNC execution metadata to track implementation progress.

Do I need a specific repository structure to automate task generation from design artifacts?

Yes, automating task generation from design artifacts requires a repository structure compliant with the spec-kit standard, and the repository must contain feature-specific design artifacts like plan.md and spec.md.

How do I track parallelization opportunities when planning development workflows?

Tracking parallelization opportunities when planning development workflows involves initializing a dual-execution loop that classifies tasks as SYNC or ASYNC, identifying which implementation tasks can run concurrently.

What's the best way to translate high-level specifications into granular, testable tasks?

Translating high-level specifications into granular, testable tasks is best achieved by using an automated workflow tool that parses existing design documents to map user stories into execution-ready checklists complete with test requirements and dependency ordering.

When should I not use automated task list generation for software engineering planning?

You should avoid automated task list generation when your repository lacks a spec-kit compliant structure or feature-specific design artifacts, as the parser requires existing plan.md and spec.md files to map user stories into tasks.