prd-task

Parse Markdown PRDs into structured prd.json artifacts with progress tracking.

Updated Jan 18, 2026
One-click install
npx skills add https://github.com/deloreyj/.dotfiles --skill prd-task-deloreyj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-task
Source: https://github.com/deloreyj/.dotfiles/tree/main/home/.config/opencode/skill/prd-task
Command: npx skills add https://github.com/deloreyj/.dotfiles --skill prd-task-deloreyj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manually translating Markdown PRDs into a machine-readable JSON plan is error-prone and slows automation.

Core Features & Use Cases

  • Converts a Markdown PRD into a structured prd.json that can drive autonomous task execution.
  • Creates a dedicated state directory under .opencode/state/<prd-name>/, moves the original PRD to prd.md for traceability, and stores the resulting JSON and progress marker.
  • Preserves the PRD's end-state focus and verification steps to enable automated validation and auditing.

Quick Start

Load a markdown PRD named prd-<name>.md and run the prd-task workflow to generate the corresponding prd.json.

Frequently Asked Questions about prd-task

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

FAQPage Schema
How do I convert a markdown PRD into a JSON format for task automation?

To convert a markdown PRD into JSON, a workflow parses the file, extracts tasks with verification steps, and writes a structured prd.json artifact to drive autonomous execution. It also moves the original PRD to a state directory for traceability.

What is deterministic task decomposition from a PRD?

Deterministic task decomposition is the process of parsing a markdown PRD to extract structured tasks and verification steps, outputting a machine-readable JSON artifact. This enables automated task execution, state management, and progress tracking without manual translation errors.

How do I track progress and state for an automated PRD workflow?

You can track progress by creating a dedicated state directory under .opencode/state/, where the workflow stores the original prd.md, the executable prd.json, and an empty progress.txt indicator. This setup preserves context and enables automated validation and auditing.

Do I need to format my PRD in a specific way to generate executable JSON tasks?

Your PRD must be authored in Markdown and include clear end-state focuses and verification steps. The workflow reads the markdown file, extracts these verification steps, and preserves them in the JSON output to enable automated validation.

What is the best way to preserve context like patterns and key files when converting PRDs?

The best way to preserve context is to move the original PRD into a dedicated state directory and generate a structured JSON artifact alongside it. This maintains traceability while keeping key files and patterns accessible for autonomous execution.

Why does manually translating markdown PRDs into JSON slow down automation?

Manually translating markdown PRDs into JSON is error-prone and creates a bottleneck for automation because it requires human intervention to structure tasks and verification steps. Generating a deterministic JSON artifact eliminates this manual overhead.