relentless

Convert markdown or text PRDs into structured relentless/prd.json files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams rapidly convert formal PRDs into the Relentless PRD JSON format, enabling automated planning and execution without manual re-keying.

Core Features & Use Cases

  • PRD to JSON conversion: Transforms markdown or text PRDs into a structured relentless/prd.json file.
  • Project scoping and branching: Generates a sensible Git branch name like relentless/<feature-name-kebab-case>.
  • Use Case Mapping: Extracts user stories and acceptance criteria ready for Relentless iteration.

Quick Start

Drop your PRD (markdown or plain text) into the project and run the converter to generate relentless/prd.json in the relentless/ directory.

Frequently Asked Questions about relentless

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

FAQPage Schema
How do I convert a markdown PRD to a structured JSON format for automated iteration planning?

To convert a markdown PRD to structured JSON, provide your text or markdown document to generate a relentless/prd.json file containing project, branchName, description, and userStories fields for automated iteration planning.

What fields are required when generating a prd.json file for autonomous agent execution?

Generating a prd.json file requires four enforced fields: project, branchName, description, and userStories, where each user story must include a Typecheck passes criterion and related acceptance criteria.

Can I use plain text PRDs to automatically generate a Git branch name and user stories?

Yes, you can use plain text PRDs to automatically generate a Git branch name formatted as relentless/<feature-name-kebab-case> and extract user stories mapped with acceptance criteria for execution.

Does the relentless prd.json conversion process support manual re-keying of acceptance criteria?

The relentless prd.json conversion process eliminates manual re-keying by automatically extracting user stories and acceptance criteria directly from the input PRD for autonomous iteration planning.

Why does my prd.json output enforce a Typecheck passes criterion for every user story?

The prd.json output enforces a Typecheck passes criterion for every user story to ensure the generated user stories meet the required validation standards of the autonomous agent system.

What is the best way to structure PRDs for autonomous agent system automation without manual re-keying?

The best way to structure PRDs for automation is converting markdown or text documents into a relentless/prd.json format, which extracts project details and maps user stories with acceptance criteria directly.