tasks

Convert specs.md and plan.md into a phase-organized tasks.md with dependencies.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/XinheLIU/human-leverage --skill tasks-xinheliu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tasks
Source: https://github.com/XinheLIU/human-leverage/tree/main/.claude/skills/tasks
Command: npx skills add https://github.com/XinheLIU/human-leverage --skill tasks-xinheliu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Breaks feature specs and plan documents into an ordered, phase-organized tasks.md checklist to accelerate delivery and maintain traceability.

Core Features & Use Cases

  • Converts specs.md and plan.md into a phase-organized tasks.md aligned with MVP slices and user-story priorities (P1/P2/P3).
  • Enforces a structured workflow: Setup → Foundational → Unit US phases → Polish, with checkpoints and independent testability.
  • Generates a Dependencies & Execution Order section to clarify sequencing and cross-story dependencies.

Quick Start

Follow the prompt to produce a complete tasks.md for the current feature by referencing specs and plans.

Frequently Asked Questions about tasks

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

FAQPage Schema
How do I turn feature specs into an executable MVP task list?

To turn feature specs into an executable MVP task list, this skill analyzes your specs.md and plan.md to generate a structured tasks.md. It organizes tasks by user stories, validates prerequisites, and outputs a ready-to-implement checklist.

What is the best way to organize tasks by user stories and execution order?

Organizing tasks by user stories and execution order is handled by splitting work into Setup, Foundational, Unit US, and Polish phases. It generates a Dependencies & Execution Order section to clarify sequencing and cross-story dependencies.

How do I generate a phase-organized tasks.md from a plan document?

To generate a phase-organized tasks.md from a plan document, the skill references your existing plan.md and specs.md. It enforces a structured workflow with checkpoints and aligns tasks with MVP slices and P1/P2/P3 priorities.

Do I need both specs.md and plan.md files to generate tasks?

Yes, you need both specs.md and plan.md files because the skill analyzes these inputs to validate prerequisites and ensure consistent formatting. It cross-references both documents to produce a complete tasks.md.

Can I align generated tasks with MVP slices and P1/P2/P3 priorities?

You can align generated tasks with MVP slices and P1/P2/P3 priorities directly through the conversion process. The output tasks.md reflects these priorities, ensuring traceability and accelerating delivery of the most critical features.

What limitations exist when breaking down feature specs into a tasks checklist?

A limitation when breaking down feature specs into a tasks checklist is the strict dependency on having pre-existing specs.md and plan.md files. Without properly structured input documents, the generated execution order and task phases may lack accuracy.