agile-2-create-prd

Convert a validated Vision Doc into a structured Confluence PRD page.

Updated May 16, 2026
One-click install
npx skills add https://github.com/cedricfarinazzo/agile-skills --skill agile-2-create-prd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agile-2-create-prd
Source: https://github.com/cedricfarinazzo/agile-skills/tree/main/agile-product/skills/agile-2-create-prd
Command: npx skills add https://github.com/cedricfarinazzo/agile-skills --skill agile-2-create-prd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converting a validated Vision Doc into a complete PRD in Confluence creates a single source of truth, aligns stakeholders, and speeds up product delivery.

Core Features & Use Cases

  • Scans the Vision Doc and Jira/Confluence for existing PRD context and gaps.
  • Drafts a PRD as a Confluence child page under the project root, mapping Vision statements to PRD sections (User Problems, Goals, KPIs, Roadmap).
  • Guides an interactive interview with the user to fill missing PRD details and reconciles them with the Vision Doc.
  • Provides a structured PRD ready for review, approval, and downstream work (Epics, Stories).

Quick Start

Draft a PRD by scanning the Vision Doc and existing PRDs, then create a Confluence PRD page under the project root and link it to the Vision Doc.

Frequently Asked Questions about agile-2-create-prd

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

FAQPage Schema
How do I create a PRD in Confluence from a Vision Doc?

To create a PRD in Confluence from a Vision Doc, the Skill scans existing context, maps Vision statements to structured sections like user problems and KPIs, and generates a child page under the project root.

What sections are required in a structured PRD for stakeholders?

A structured PRD for stakeholders requires sections for user problems, user journeys, requirements, risks, and KPIs to establish a single source of truth and align product delivery.

How to align stakeholder requirements with Confluence documentation?

Align stakeholder requirements with Confluence documentation by translating validated Vision statements into an exact PRD structure, reconciling missing details through an interactive interview process.

Do I need an existing Vision Doc to generate a product requirements document?

Yes, you need an existing validated Vision Doc to generate a product requirements document, as the Skill applies this context to map goals and user problems into structured PRD sections.

Can I update an existing PRD and maintain traceability in Confluence?

Yes, you can update an existing PRD and maintain traceability in Confluence, as the Skill reconciles gaps in existing PRDs and records all changes with timestamps to support traceability.