prd-task

Parse Markdown PRDs into executable JSON state definitions.

2|Updated Jun 23, 2022
One-click install
npx skills add https://github.com/magoz/.dotfiles --skill prd-task-magoz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-task
Source: https://github.com/magoz/.dotfiles/tree/main/opencode/.config/opencode/skill/prd-task
Command: npx skills add https://github.com/magoz/.dotfiles --skill prd-task-magoz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert Markdown PRDs into executable JSON state definitions for autonomous task execution.

Core Features & Use Cases

  • Converts Markdown PRDs with end-state and verification tasks into executable JSON state files.
  • Generates a traceable artifact set in .opencode/state/<prd-name>/ including prd.md, prd.json, and progress.txt for progress tracking.
  • Enables reproducible project analysis and task generation for automation pipelines and auditing.

Quick Start

Provide a Markdown PRD and run the prd-task skill to generate the corresponding prd.json in the .opencode/state directory.

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 an executable JSON state definition?

To convert a Markdown PRD into executable JSON, provide the document to the parser and it generates a structured prd.json state file within the .opencode/state/<prd-name>/ directory for autonomous task execution.

What is the best way to generate traceable task artifacts from a Markdown PRD?

Generating traceable task artifacts from a Markdown PRD involves parsing the document to produce prd.md, prd.json, and progress.txt files, creating a reproducible audit trail for automation pipelines.

Do I need my PRD to include verification tasks to generate executable JSON?

Yes, your PRD must include an end-state and verifiable tasks to generate executable JSON, as the parser relies on these defined parameters to produce a valid state definition for autonomous execution.

How does parsing a PRD into JSON state files enable autonomous task execution?

Parsing a PRD into JSON state files enables autonomous task execution by translating project context and verification tasks into a structured format that an agent can directly process and act upon.

Can I use this Markdown to JSON conversion for progress tracking in task management?

Yes, this Markdown to JSON conversion supports task management progress tracking by generating a progress.txt file alongside the prd.json state definition within the target state directory.

What limitations exist when translating project context from Markdown to JSON state definitions?

A key limitation is that the Markdown to JSON translation requires PRDs authored with clearly defined end-states and verifiable tasks; unstructured documents without these elements cannot produce valid executable state files.