convert

Convert tasks.md into prd.json with routing metadata via relentless CLI.

96|5|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/ArvorCo/Relentless --skill convert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convert
Source: https://github.com/ArvorCo/Relentless/tree/main/.claude/skills/convert
Command: npx skills add https://github.com/ArvorCo/Relentless --skill convert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts a tasks.md into a prd.json enriched with automatic routing metadata, enabling cost-aware feature planning and execution.

Core Features & Use Cases

  • Automatically convert tasks.md into prd.json with routing metadata to guide task execution.
  • Validate story structure, dependencies, and acceptance criteria, producing a consistent PRD workflow.
  • Generate supporting artifacts like prd.md and a progress/log trail to track feature development.

Quick Start

Run relentless convert relentless/features/NNN-feature/tasks.md --feature <feature-name> to generate the prd.json with routing and the associated artifacts.

Frequently Asked Questions about convert

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

FAQPage Schema
How do I convert tasks.md into a prd.json for feature planning?

You can convert tasks.md into a prd.json by running the relentless CLI, which validates story structure and dependencies to produce routing metadata, a prd.md, and a progress log.

What is automatic routing metadata in a product requirements document?

Automatic routing metadata in a prd.json classifies feature stories and estimates costs, ensuring each task is mapped correctly to guide cost-aware feature planning and execution.

Do I need the relentless CLI to generate prd.json from markdown tasks?

Yes, the relentless CLI is required to perform the conversion and routing classification, ensuring each feature's stories are mapped and costs estimated within the prd.json.

Can I validate story dependencies and acceptance criteria during markdown to PRD conversion?

Yes, converting tasks.md validates story structure, dependencies, and acceptance criteria to produce a consistent PRD workflow alongside the prd.json and progress log artifacts.

What artifacts are generated when converting tasks.md for feature management?

The conversion generates a prd.json enriched with routing metadata, a prd.md document, and a progress log trail to track feature development and validate story dependencies.