prd-task

Convert Markdown PRDs into executable JSON task lists.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/Kuass/kiro-gateway-plus --skill prd-task-kuass
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-task
Source: https://github.com/Kuass/kiro-gateway-plus/tree/main/.opencode/skill/prd-task
Command: npx skills add https://github.com/Kuass/kiro-gateway-plus --skill prd-task-kuass

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the conversion of human-readable Product Requirement Documents (PRDs) written in Markdown into structured, executable JSON task lists, streamlining the process of translating requirements into actionable development items.

Core Features & Use Cases

  • Automated Task Generation: Parses markdown PRDs to extract tasks, descriptions, verification steps, and metadata.
  • Standardized Output: Generates JSON files conforming to a defined schema for consistent task representation.
  • Workflow Integration: Designed to be part of a larger development lifecycle, specifically converting PRDs into tasks for autonomous execution.
  • Use Case: After defining a new feature in a prd.md file, use this skill to instantly generate a prd.json file that can be fed into an automated execution system.

Quick Start

Use the prd-task skill to convert the prd.md file located in .beads/artifacts/br-123/ into a prd.json file.

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 to JSON tasks for autonomous execution?

To convert a markdown PRD to JSON tasks, you can parse the `## Tasks` and `## Bead Metadata` sections to extract descriptions and verification steps, generating an executable `prd.json` file.

What is the best way to generate standardized JSON from product requirement documents?

Generating standardized JSON from product requirement documents involves parsing markdown files using schema validation, which yields consistent `prd.json` files suitable for automated development workflows.

Does prd-task work with specific markdown sections to extract task metadata?

Yes, prd-task works by specifically parsing `## Tasks` and `## Bead Metadata` sections in your markdown file to extract tasks, descriptions, verification steps, and metadata.

Can I validate the generated JSON output against a defined schema?

You can validate the generated JSON output against a defined schema using `references/prd-schema.json` to ensure the structured task list conforms to required formats before execution.

How to initialize progress tracking after converting a PRD to JSON?

To initialize progress tracking after converting a PRD to JSON, the system automatically generates `.beads/artifacts/<bead-id>/progress.txt` alongside the `prd.json` file during the conversion process.

Where are the generated JSON task lists stored during the PRD conversion process?

The generated JSON task lists are stored in the `.beads/artifacts/<bead-id>/prd.json` directory, ensuring structured artifact management for your development lifecycle.