prd-architect

Generate structured Product Requirements Documents with architectural feasibility analysis.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams and engineering leads rapidly craft comprehensive Product Requirements Documents (PRDs) by aligning product value with technical feasibility. It streamlines discovery, documentation, and stakeholder alignment throughout a project's early stages.

Core Features & Use Cases

  • Iterative PRD generation: Translate a project idea into a structured PRD with executive summary, scope, success metrics, milestones, and success criteria.
  • Gaps & questions: Identify missing information (personas, journeys, technical stack, data model, edge cases, monetization) and prompt targeted questions until the PRD reaches the required completeness.
  • Guided workflow: Follow the defined process (Ingest & Analyze, Assess Gaps, The 85% Threshold loop, Final Output) to produce a production-ready PRD.

Quick Start

Draft a PRD for a new mobile app that enables remote collaboration, and include executive summary, core features, personas, data model, and initial technology recommendations.

Frequently Asked Questions about prd-architect

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

FAQPage Schema
How do I generate a Product Requirements Document from an app idea?

To generate a Product Requirements Document, input your app idea and let the skill ingest and analyze the project. It assesses gaps in personas, data models, and technical stack, prompting targeted questions until the PRD reaches an 85% completeness threshold for final output.

What sections should a comprehensive PRD include for stakeholder alignment?

A comprehensive PRD should include an executive summary, scope, user stories, success metrics, milestones, data models, API sketches, and non-functional considerations. Generating these structured sections ensures technical feasibility aligns with product strategy.

Can I use this to identify missing requirements in a product strategy draft?

Yes, you can identify missing requirements through a guided gap analysis. The skill analyzes your draft for missing personas, journeys, monetization details, and edge cases, then prompts targeted questions to iteratively refine the product strategy.

Does this PRD workflow handle both product value and architectural feasibility?

Yes, this PRD workflow combines product value with architectural feasibility. It translates project ideas into structured milestones and success criteria while ensuring the data model and API sketches satisfy non-functional technical considerations.

What is the best way to structure milestones and success criteria for a new project?

The best way to structure milestones and success criteria is through an iterative generation loop. The skill translates your project idea into a structured PRD, guiding you through gap analysis until the document reaches an 85% completeness threshold.

Why does PRD generation require answering targeted questions during the workflow?

PRD generation requires answering targeted questions to satisfy the 85% completeness threshold. This iterative loop assesses missing information like technical stacks, edge cases, and user journeys to ensure the final output is production-ready.