angainor

Convert Markdown or text PRDs into Angainor prd.json files.

Updated Jan 18, 2026
One-click install
npx skills add https://github.com/thepriceisright/angainor --skill angainor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: angainor
Source: https://github.com/thepriceisright/angainor/tree/main/skills/angainor
Command: npx skills add https://github.com/thepriceisright/angainor --skill angainor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the transformation of PRDs into Angainor's prd.json format, eliminating manual formatting errors and speeding up setup for autonomous agent iterations.

Core Features & Use Cases

  • Convert a PRD written in Markdown or plain text into a structured prd.json file located at the project root.
  • Derive a branchName in the form angainor/[feature-name-kebab-case] for versioning and collaboration.
  • Produce one-iteration-ready user stories with clear acceptance criteria suitable for PRD-based automation.
  • Standardize PRD inputs to enable repeatable workflows across projects and teams.

Quick Start

Place your PRD document in the project root and run the Angainor PRD converter. The tool will generate prd.json in the project root with a kebab-cased feature branch name and a set of ready-to-run user stories.

Frequently Asked Questions about angainor

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

FAQPage Schema
How do I convert a PRD to JSON format for autonomous execution?

To convert a PRD to JSON format, place your Markdown or text PRD in the project root and run the converter. It generates a structured prd.json file with kebab-cased feature branch names and one-iteration-ready user stories.

What is the prd.json schema and when do I need it for product management automation?

The prd.json schema is a structured format that standardizes product requirements for autonomous agent execution. You need it when automating PRD-based workflows, ensuring user stories have clear acceptance criteria and pass Typecheck iterations.

Can I use a Markdown PRD to generate a feature branch and user stories automatically?

Yes, you can use a Markdown PRD to generate a feature branch and user stories automatically. The tool derives an angainor/[feature-name-kebab-case] branch and produces one-iteration-ready user stories with enforced acceptance criteria.

Does the PRD conversion tool enforce any limits on user story iterations?

Yes, the PRD conversion tool enforces a one-iteration rule for each user story. This means every generated story in the prd.json must be completed in a single iteration, including passing Typecheck, to ensure autonomous execution readiness.

Where does the prd.json file get created when converting a PRD?

The prd.json file is created in the project root directory when converting a PRD. This standard placement ensures autonomous agents can easily locate the structured requirements and execute the derived user stories.

Why does PRD conversion to JSON eliminate manual formatting errors?

PRD conversion to JSON eliminates manual formatting errors by automating the transformation of Markdown or text PRDs into a schema-compliant prd.json. This standardizes inputs, ensuring repeatable workflows and consistent user story structures across projects.