prd

Generate an 11-file PRD documentation suite from a project vision.

10|3|Updated May 26, 2026
One-click install
npx skills add https://github.com/agentik-os/OmegaOS --skill prd-agentik-os
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/agentik-os/OmegaOS/tree/main/skills/prd
Command: npx skills add https://github.com/agentik-os/OmegaOS --skill prd-agentik-os

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates a full PRD documentation suite from a project's vision, transforming a brief into a structured artifact bundle that accelerates planning and alignment across teams.

Core Features & Use Cases

  • Generates a complete 11-file documentation suite (VISION.md, PRD.md, TECH-ARCHITECTURE.md, DESIGN-SYSTEM.md, LAYOUTS.md, DATA-MODEL.md, AGENT-PLAYBOOK.md, TESTING-STRATEGY.md, CHANGELOG-TEMPLATE.md, GLOSSARY.md, and a FEATURES/ directory with per-feature specs).
  • Supports flexible workflow integration: standalone generation or as part of the /vision -> /prd -> /team pipeline, with flags like --new, --input, --platform, --skip-design-system, and --skip-testing.
  • Provides structured output and guidance for cross-functional teams, including dependency mapping, governance checks, and feature specification alignment.
  • Provides an extensible template system that can be reused to bootstrap future projects from a vision brief.

Quick Start

Run /prd to generate the complete PRD documentation suite for your current vision, creating all core docs and feature specs in /docs.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I generate a complete PRD documentation suite from a project vision?

To generate a complete PRD documentation suite from a project vision, run the /prd command. It transforms a brief into a structured 11-file artifact bundle, including VISION.md, PRD.md, and TECH-ARCHITECTURE.md, accelerating planning and team alignment.

What files are included in an automated product requirements document bundle?

An automated product requirements document bundle includes 11 core files: VISION.md, PRD.md, TECH-ARCHITECTURE.md, DESIGN-SYSTEM.md, LAYOUTS.md, DATA-MODEL.md, AGENT-PLAYBOOK.md, TESTING-STRATEGY.md, CHANGELOG-TEMPLATE.md, GLOSSARY.md, and a FEATURES directory with per-feature specs.

Can I skip generating the design system and testing strategy when creating product management docs?

Yes, you can skip generating the design system and testing strategy when creating product management docs. The suite supports flags like --skip-design-system and --skip-testing to tailor the scope and content of the output documentation to your specific needs.

Does the PRD generator support integration into an existing product vision and team pipeline?

Yes, the PRD generator supports integration into an existing product vision and team pipeline. You can use it standalone or as part of a /vision -> /prd -> /team pipeline workflow, applying flags like --new and --input to manage your project briefs.

How do product management tools ensure traceability across technical architecture and feature specs?

Product management tools ensure traceability across technical architecture and feature specs by applying structured output generation. This provides dependency mapping, governance checks, and feature specification alignment across the entire documentation bundle.

What is the best way to bootstrap future projects from a vision brief?

The best way to bootstrap future projects from a vision brief is using an extensible template system. It converts briefs into comprehensive documentation bundles with consistent structure, allowing teams to reuse the framework for rapid project initialization.