prd-to-rfc

Convert a PRD into an approved RFC with associated tickets.

1|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/guardian-intelligence/apm2 --skill prd-to-rfc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd-to-rfc
Source: https://github.com/guardian-intelligence/apm2/tree/main/documents/skills/prd-to-rfc
Command: npx skills add https://github.com/guardian-intelligence/apm2 --skill prd-to-rfc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the end-to-end lifecycle of turning a Product Requirements Document (PRD) into a governed RFC with associated tickets, providing deterministic creation, review, and final orchestration artifacts.

Core Features & Use Cases

  • Deterministic RFC creation: Invokes the RFC council to generate an initial RFC and associated tickets for a PRD.
  • Iterative review loop: Repeats council reviews until the RFC is approved or terminal conditions are met.
  • End-to-end orchestration: Emits a complete evidence bundle summarizing the PRD -> RFC journey and final ticket state.
  • Use Case: Apply to product governance pipelines where PRDs must become structured RFCs with traceable tickets and approvals.

Quick Start

Use the prd-to-rfc skill to convert PRD-0005 into RFC-0010 by invoking the RFC council and iterating until APPROVED, emitting the final orchestration bundle.

Frequently Asked Questions about prd-to-rfc

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

FAQPage Schema
How do I convert a PRD into an approved RFC with associated tickets?▼

To convert a PRD into an approved RFC, the workflow invokes an RFC council to generate the initial RFC and tickets, then iteratively reviews until approval. It accepts configurable inputs like PRD_ID and max_iterations to govern the lifecycle.

Can I limit the number of review iterations when turning a PRD into an RFC?▼

Yes, you can limit PRD-to-RFC review iterations using the max_iterations input. The orchestration loop repeats council reviews until the RFC is approved or terminal conditions are met.

What is the RFC council process in product governance workflows?▼

The RFC council process in product governance generates a structured RFC from a PRD and performs iterative reviews. It ensures deterministic RFC creation, tracks iteration history, and emits a final evidence bundle.

Does PRD-to-RFC orchestration support dry-run mode for governance pipelines?▼

Yes, PRD-to-RFC orchestration supports a dry-run flag for product governance pipelines. This allows you to simulate the PRD-to-RFC conversion and review loop without committing final tickets or approval state changes.

How do I track the review history when generating an RFC from a PRD?▼

To track review history when generating an RFC, the workflow records iteration history during the council review loop. It ultimately emits a complete evidence bundle summarizing the PRD-to-RFC journey and final ticket state.