jp-task-list

Convert approved PRDs into structured YAML task lists.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/jinglemansweep/agent-resources --skill jp-task-list
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jp-task-list
Source: https://github.com/jinglemansweep/agent-resources/tree/main/plugins/jplan/skills/jp-task-list
Command: npx skills add https://github.com/jinglemansweep/agent-resources --skill jp-task-list

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converting an approved PRD into a structured YAML task list enables downstream planning and execution by producing tasks.yaml and serving as the bridge between PRD review and task validation.

Core Features & Use Cases

  • PRD-to-task conversion that yields a complete, machine-readable task list suitable for planning and tracking.
  • Phase-aware workflow integration with jp-prd-review and jp-task-review to ensure PRD integrity and validation.
  • Output generation for phase directories: creates <phase-path>/tasks.yaml for consumption by jp-plan and jp-execute.

Quick Start

Use /jp-task-list [phase-path] to generate a tasks.yaml from an approved PRD in the phase directory.

Frequently Asked Questions about jp-task-list

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

FAQPage Schema
How do I convert an approved PRD into a structured YAML task list?

To convert an approved PRD into a structured YAML task list, apply a PRD-to-task conversion workflow that generates a machine-readable tasks.yaml file, serving as the bridge between PRD review and downstream task validation.

What is the best way to generate tasks.yaml for agile project management?

Generating tasks.yaml for agile project management involves phase-aware workflow integration that discovers phase directories from an approved PRD and outputs structured YAML tasks suitable for planning and tracking.

How does phase-path discovery work when creating a YAML task list from a PRD?

Phase-path discovery works by specifying the phase directory as an input constraint, reading the approved PRD within that location, and generating the corresponding tasks.yaml output directly into the discovered phase path.

Do I need an approved PRD before generating a YAML task list?

Yes, an approved PRD is required before generating a YAML task list, because the conversion process relies on PRD integrity to ensure downstream planning and execution pipelines receive validated inputs.

Can I use a YAML task list for downstream execution and planning pipelines?

Yes, you can use the generated YAML task list for downstream execution and planning pipelines, as the tasks.yaml output is specifically structured for consumption by subsequent planning and execution phases.

What are the limitations of converting PRDs into YAML task lists without phase directory conventions?

Without phase directory conventions, converting PRDs into YAML task lists fails because phase-path discovery cannot locate the approved PRD or correctly output the generated tasks.yaml file for downstream pipelines.