tasks

Convert PRD markdown into structured prd.json with task IDs and priorities.

539|61|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/snarktank/compound-product --skill tasks-snarktank
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tasks
Source: https://github.com/snarktank/compound-product/tree/main/skills/tasks
Command: npx skills add https://github.com/snarktank/compound-product --skill tasks-snarktank

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts PRD markdown documents into a machine-readable prd.json format so AI agents can autonomously plan and execute tasks.

Core Features & Use Cases

  • PRD to JSON conversion: Extracts tasks, stories, and requirements from a PRD and expands them into granular, verifiable subtasks for execution loops.
  • Task orchestration: Generates a prioritized, investigation-first task list ready for automation with agent-based tooling.
  • Use Case: A product team writes a PRD; this skill produces a ready-to-run prd.json for the automation pipeline.

Quick Start

Place a PRD markdown at tasks/prd-feature-name.md and run the skill to generate prd.json.

Frequently Asked Questions about tasks

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

FAQPage Schema
How do I turn PRD markdown into a structured JSON format for automation pipelines?

Converting PRD markdown into machine-readable tasks involves extracting requirements, expanding them into granular subtasks, assigning IDs, and outputting a prd.json file. This structured output includes project metadata, branch names, and task objects with acceptance criteria and priorities.

How do I generate granular, executable tasks from a PRD for AI agents?

You can generate granular, executable tasks from a PRD by parsing the unstructured markdown to extract requirements and expanding them into verifiable subtasks. The skill produces a prioritized, investigation-first task list within a prd.json file ready for AI agent orchestration.

What is the best way to structure product requirements for task orchestration?

Structuring product requirements for task orchestration involves formatting them as a prd.json file containing project details, branch names, and task objects. Each task includes an ID, title, acceptance criteria, priority, passes, and notes to drive automation pipelines.

Does this PRD to JSON conversion work with agile project planning workflows?

PRD to JSON conversion supports agile project planning by generating a prioritized, investigation-first task list ready for automation. It extracts user stories and requirements from the PRD markdown to create verifiable subtasks for agile execution loops.

How do I start using the skill to convert my PRD markdown into tasks?

Start converting PRD markdown into tasks by placing your PRD document at tasks/prd-feature-name.md and running the skill. It processes the unstructured markdown and outputs a ready-to-run prd.json file for your automation pipeline.

What specific data fields are included in the generated prd.json output?

The generated prd.json output includes project, branchName, description, and a list of task objects. Each task object contains an id, title, acceptanceCriteria, priority, passes, and notes to ensure machine-readable execution.