tasks

Generate tasks.md and plan-to-tasks.yaml from design documents.

Updated Mar 20, 2026

Search Tags:#workflow #planning #checkpoints #traceability #project-management #spec-to-plan #task-generation

Ready to run

npx skills add https://github.com/lakshmithite127/Lakshmi-Thite --skill tasks-lakshmithite127

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tasks
Source: https://github.com/lakshmithite127/Lakshmi-Thite/tree/main/.ghcp-appmod/skills/tasks
Command: npx skills add https://github.com/lakshmithite127/Lakshmi-Thite --skill tasks-lakshmithite127

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the generation of detailed, organized tasks.md for feature implementation based on design documents, ensuring plan-to-tasks traceability.

Core Features & Use Cases

Generates a complete tasks.md from design documents (spec.md, plan.md, knowledge graph) with per-story organization and traceability to plan items.
Loads and validates prerequisites and upstream checkpoints to ensure readiness before task generation.
Creates a plan-to-tasks checkpoint at FEATURE_DIR/checkpoints/plan-to-tasks.yaml and a summary of coverage and traceability.
Produces a dependency-aware, phased task structure aligned to user stories in spec.md.

Quick Start

Provide the repository root and feature directory; run the task-generation skill to produce tasks.md and plan-to-tasks.yaml based on design documents.

Frequently Asked Questions about tasks

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

FAQPage Schema

How do I generate detailed tasks from design documents automatically?▼

You can generate detailed tasks from design documents by providing your repository root and feature directory containing spec.md and plan.md. The skill extracts user stories and plan items to produce a dependency-aware tasks.md file.

What is plan-to-tasks traceability and how does it ensure feature coverage?▼

Plan-to-tasks traceability maps extracted user stories and plan items directly to generated tasks. It validates dependencies and coverage, outputting a plan-to-tasks.yaml checkpoint to ensure comprehensive rollout without missing requirements.

How do I create a dependency-aware phased task structure from a spec.md file?▼

To create a dependency-aware phased structure from spec.md, run the task-generation skill on your feature directory. It aligns tasks to user stories and outputs a structured tasks.md validating all coverage and dependencies.

Do I need a knowledge graph to generate tasks from design documents?▼

You do not need a knowledge graph strictly, but the skill supports projects with design artifacts like spec.md, plan.md, and knowledge graphs. It loads and validates these prerequisites to ensure readiness before generating tasks.

What's the best way to organize tasks.md by user stories for feature implementation?▼

The best way to organize tasks.md by user stories is to automate generation from design documents. The skill extracts stories from spec.md, maps them to phased tasks, and validates dependencies for a comprehensive rollout.

Why does task generation fail when upstream prerequisites are missing?▼

Task generation fails when upstream prerequisites are missing because the skill loads and validates design artifacts like spec.md and plan.md to ensure readiness. It requires these checkpoints to establish plan-to-tasks traceability before proceeding.