cy-create-tasks

Decompose PRDs and TechSpecs into detailed markdown task files with metadata.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/rhuangabrielsantos/skills --skill cy-create-tasks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cy-create-tasks
Source: https://github.com/rhuangabrielsantos/skills/tree/main/skills/cy-create-tasks
Command: npx skills add https://github.com/rhuangabrielsantos/skills --skill cy-create-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Translating high‑level product requirements and technical specifications into granular, independently implementable task files is time‑consuming, error‑prone, and often lacks consistent metadata and dependency tracking.

Core Features & Use Cases

  • Automated Decomposition – Converts PRDs and TechSpecs into detailed task markdown files with full front‑matter metadata.
  • Codebase Enrichment – Augments each task with relevant file paths, integration points, and test specifications discovered via codebase exploration.
  • Dependency Management – Generates a master task list, resolves task dependencies, and ensures no circular references.

Quick Start

Use the cy-create-tasks skill to generate tasks for a feature by providing its name and the associated PRD or TechSpec file.

Frequently Asked Questions about cy-create-tasks

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

FAQPage Schema
How do I generate tasks from a PRD or TechSpec?

Generating tasks from a PRD or TechSpec involves decomposing the document into granular markdown files. This skill automates that by creating individual task files with front-matter metadata, a master task list, and dependency tracking.

How does codebase enrichment work for task generation?

Codebase enrichment augments generated tasks with relevant file paths, integration points, and test specifications. The skill explores the codebase to discover implementation details and attaches them to each individual markdown task file.

What is the best way to manage dependencies when decomposing a TechSpec into tasks?

The best way to manage dependencies is to generate a master task list that resolves task dependencies and ensures no circular references exist. This skill automatically maps dependencies when creating the task files.

Can I create task files with full metadata from a product requirement document?

Yes, you can create task markdown files with full front-matter metadata directly from a product requirement document. The skill converts PRDs into independently implementable tasks enriched with codebase context.

Does task generation resolve circular dependencies in the master task list?

Task generation resolves dependencies and prevents circular references in the master task list. The skill ensures that the decomposed task files form a valid execution order without dependency loops.

When do I need to decompose a TechSpec into individual task files?

You need to decompose a TechSpec into individual task files when a feature specification exists and you must translate high-level requirements into granular, independently implementable units with consistent metadata.