Task Planning

Name: Task Planning
Availability: InStock
Author: larus-peritus

Break down approved designs into structured implementation tasks with requirements traceability.

Updated Jan 19, 2026

Search Tags:#testing #requirements traceability #sprint planning #task planning #spec-driven development #design-to-implementation

Ready to run

npx skills add https://github.com/larus-peritus/pel_web --skill task-planning-larus-peritus

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Task Planning
Source: https://github.com/larus-peritus/pel_web/tree/main/.claude/skills/tasks-skill
Command: npx skills add https://github.com/larus-peritus/pel_web --skill task-planning-larus-peritus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break down approved designs into actionable implementation tasks. Use when the user wants to create development tasks, plan implementation steps, sequence work, or move from design to implementation in spec-driven development. Helps convert technical designs into sequential, testable coding tasks.

Core Features & Use Cases

Task analysis and mapping: convert design components into tasks
Two-level task hierarchy (epics and tasks)
Requirements tracing and testing plan alignment
Workflow guidance: step-by-step to move from design to code

Quick Start

Provide an approved design and requirements, then request a task breakdown: "Task Planning: break down the approved design into implementation tasks".

Frequently Asked Questions about Task Planning

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

FAQPage Schema

How do I break down an approved technical design into actionable development tasks?▼

To break down an approved technical design into actionable development tasks, provide the design and requirements to generate a structured two-level hierarchy of epics and tasks with clear requirements traceability.

How does spec-driven development handle requirements traceability during sprint planning?▼

Spec-driven development handles requirements traceability by mapping generated implementation tasks directly to data models, services, APIs, tests, and acceptance criteria throughout the sprint planning process.

What is the best way to convert design components into a testable workflow?▼

The best way to convert design components into a testable workflow is to analyze the design and map each component into sequential, testable coding tasks aligned with a testing plan.

Do I need approved requirements before starting task planning for a software project?▼

Yes, you need approved requirements and a finalized design before starting task planning, because the process relies on converting those technical designs into structured implementation steps.

Can I map design components to APIs and data models during task analysis?▼

Yes, task analysis maps design components to APIs and data models, ensuring every generated implementation task aligns with services and acceptance criteria for clear requirements traceability.

Why does task planning use a two-level hierarchy for implementation steps?▼

Task planning uses a two-level hierarchy of epics and tasks to sequence work effectively, moving step-by-step from design to code while maintaining testable coding tasks and tracing requirements.