generate-tasks

Convert feature plan artifacts into TDD-ready task specifications embedded in PLAN-*.md files.

Updated Apr 24, 2026

Search Tags:#tdd #collaboration #spec #tasks #plan #generate #plan-feature

Ready to run

npx skills add https://github.com/Utchash007/TermTales --skill generate-tasks-utchash007

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: generate-tasks
Source: https://github.com/Utchash007/TermTales/tree/main/.agents/skills/generate-tasks
Command: npx skills add https://github.com/Utchash007/TermTales --skill generate-tasks-utchash007

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform feature plans into precise, TDD-ready task specifications, enabling clear handoffs and test-driven development from plan to implementation.

Core Features & Use Cases

Collaborative planning: engages with the developer to extract requirements from a feature plan and draft a comprehensive test plan.
In-plan task embedding: outputs task specs directly into the same PLAN-*.md file to keep context intact and avoid sprawl.
Gap and risk identification: highlights ambiguities, edge cases, and dependencies to inform scope and decisions.

Quick Start

Execute this task in conversation with the developer to convert the feature plan into a TDD-ready task spec and append it to the PLAN-*.md file.

Frequently Asked Questions about generate-tasks

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

FAQPage Schema

How do I convert a feature plan into TDD-ready task specifications?▼

To convert a feature plan into TDD-ready task specifications, apply the generation process to PLAN-*.md files or direct briefs to draft a test plan, align with plan decisions, and capture edge cases as actionable task requirements.

What is the best way to generate test plans from existing plan documents?▼

Generating test plans from existing plan documents is best handled by embedding the resulting task specs directly into the same PLAN-*.md file, which preserves context, avoids document sprawl, and maintains clear handoffs for test-driven development.

How does collaborative planning work when creating task specs from a feature plan?▼

Collaborative planning for task specs engages directly with the developer to extract requirements from a feature plan, identifies gaps and risks like ambiguities or dependencies, and drafts a comprehensive test plan to inform scope decisions.

Can I use direct briefs instead of PLAN-*.md files to generate TDD task specs?▼

Yes, you can use direct briefs instead of PLAN-*.md files to generate TDD task specs, allowing you to capture edge cases and constraints as actionable task requirements even without a pre-existing markdown plan document.

Why should I embed task specifications into the same plan document?▼

Embedding task specifications into the same plan document keeps the context intact and avoids file sprawl, ensuring that the test plan, plan decisions, and actionable task requirements remain together for clear implementation handoffs.

What are the limitations of generating TDD task specs from feature plans?▼

Limitations of generating TDD task specs include relying on the clarity of the initial feature plan, as the process highlights ambiguities, edge cases, and dependencies to inform scope, requiring developer collaboration to resolve identified gaps.