prd-generator

Generate and validate PRD artifacts with mandatory sections for Batuta projects.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/jota-batuta/batuta-dots --skill prd-generator-jota-batuta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-generator
Source: https://github.com/jota-batuta/batuta-dots/tree/main/BatutaClaude/skills/prd-generator
Command: npx skills add https://github.com/jota-batuta/batuta-dots --skill prd-generator-jota-batuta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The PRD (Product Requirements Document) is the single, central planning artifact that replaces the prior multi-document workflow. It consolidates problem definition, solution approach, success criteria, data sources, boundaries, and context into one living document, reducing miscommunication and rework.

Core Features & Use Cases

  • Centralized planning: Create and read PRD artifacts that contain problem, solution, success criteria, data sources, constraints, and scope.
  • Guided structure: Enforces mandatory sections (Problema, Solucion, Criterio de exito, Datos disponibles, Constraints, Fuera de alcance) and a maximum 1–2 page length.
  • Use Case: A CTO drafts a PRD for a new feature; the implementation team uses the PRD to guide design, development, and QA.

Quick Start

Create a PRD that follows the template and includes the sections for Problema, Solucion, Criterio de exito, Datos disponibles, Constraints, and Fuera de alcance.

Frequently Asked Questions about prd-generator

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

FAQPage Schema
How do I generate a PRD document that consolidates planning and avoids rework?

To generate a PRD document that avoids rework, consolidate problem definition, solution approach, success criteria, data sources, constraints, and scope into a single living artifact. This structured workflow reduces miscommunication by replacing multi-document setups with one actionable file.

What sections are mandatory for a PRD workflow in this framework?

The mandatory sections for this PRD workflow are Problema, Solucion, Criterio de exito, Datos disponibles, Constraints, and Fuera de alcance. Including these specific sections ensures cross-team alignment and maintains a strict 1-2 page maximum length.

Can I use this PRD generator for large projects with complex scope?

This PRD generator is designed for projects using Batuta's framework but enforces a strict 1-2 page maximum length, making it unsuitable for large projects with extensive scope. It applies to SPRINT and COMPLETO modes to guide cross-team alignment on focused changes.

What is the best way to structure a PRD for cross-team alignment?

The best way to structure a PRD for cross-team alignment is to enforce mandatory sections like Problema, Solucion, and Criterio de exito within a 1-2 page limit. This centralized planning approach replaces prior multi-document workflows to reduce miscommunication.

Does this PRD template support SPRINT and COMPLETO modes?

Yes, this PRD template supports both SPRINT and COMPLETO modes for projects using Batuta's framework. It guides cross-team alignment by consolidating problem definition, solution approach, and constraints into a single actionable document.

Why should I consolidate change management documentation into a single PRD?

You should consolidate change management documentation into a single PRD to reduce miscommunication and rework across implementation teams. Centralizing problem definition, data sources, and boundaries creates one living document that effectively guides design, development, and QA.