PRD Generator Flow
Product Manager Official v1.1.30Full product requirements document generation with stakeholder context, success metrics, and technical constraints
by skrptiq
Sign in to import this skrpt into your workspace.
Sign inWhat's included 16 nodes
PRD Generator Flow
End-to-end workflow for generating a complete product requirements document with stakeholder analysis, success metrics, and technical constraints
PRD Assembler
Assembling all pipeline outputs into a single, complete, reviewable product requirements document
Problem Statement
Crafting a clear, evidence-grounded problem statement that anchors the entire product requirements document
Success Metrics
Defining measurable, honest success criteria — North Star, secondary, leading, guardrail, and anti-metrics — for a product initiative
Technical Scoping
Assessing technical feasibility, identifying constraints, dependencies, and architectural implications
PRD Assembler
Assemble all pipeline outputs into a complete, reviewable product requirements document
Problem Statement Writer
Craft a clear, compelling problem statement that grounds the entire PRD
Requirements Elicitor
Elicit and structure functional and non-functional requirements with priority and traceability
Success Metrics Definer
Define measurable success criteria, KPIs, leading indicators, and guardrail metrics for a product initiative
Technical Constraints Documenter
Document technical constraints, dependencies, architecture impact, and migration considerations
User Persona Generator
Generate detailed user personas from research data and product context using the persona card template
PRD Reference Guide
Reference standards for PRD writing, including section definitions, quality criteria, and industry conventions
PRD Writing Standards
Internal standards and conventions for writing product requirements documents
Stakeholder Mapping Guide
Guide to stakeholder identification, influence mapping, and engagement planning for product initiatives
Persona Card Template
Template for user persona cards used in PRDs and product documentation
PRD Template
Template for the final product requirements document
Requirements 1 service, 4 data types
- LLM Service
- pii
- product requirements
- user research
- technical specifications
Security Passed
Detected
- Services: llm-service
- Permissions:
- Data Handling: pii
Version history 18 releases
GH#863 Wave 1 (#858-A1 class) — fix K-045 intent/output mismatch: the workflow shipped the prd-assembler, problem-statement-writer, and success-metrics-definer prompts but never invoked them, so it emitted polished intermediate analysis rather than the promised PRD. Wired all three as execution steps in dependency order (Problem Statement → Requirements → Personas → Technical Scoping → Success Metrics → Executive Summary → **PRD Assembler** → language-polish), each backed by a new skill (`problem-statement`, `success-metrics`, `prd-assembly`) so its title is `from_step`-addressable. Cross-step inputs are now explicit `from_step` bindings via named `context_params`. Repinned polish-language 1.0.1→1.0.6 (adds the bindable `source` slot) and bound language-polish `source` ← the assembled PRD, so the final output is the polished PRD rather than the last intermediate step. Skills 1→4, total 13→16.
GH#845 — republish with American English (en-US) content, completing the source-only GH#805 flip that never reached the Hub. Copy only — no functional or behaviour change.
GH#745 — declare per-step `output: {name, type}` on every execution step (requirements/text, personas/text, technical_scope/text, summary/text, polished_prd/text, consistency_verdict/decision, input_gaps/decision, compliance_verdict/decision). Lights up the #744 rich flow-map with named, typed outputs. **Also corrects the input-gap-check step to its intended `validation` type** — its `step_type` was mis-indented (outside the parallel item) and dropped at parse time, so the step previously ran untyped; it is now a validation gate. Content + structural fix (GH#748); no bindings changes.
GH#645 Row 3b — migrate to K-037 dep-referenced schema. Strip 14 inline shared-content files and declare 14 hub-shared deps (UUID id + slug name + version + checksum from `gen-dep-checksums.mjs`). Closes pre-Step-3 inline-vendoring for this bundle.
Wave 2: re-signed with canonical engine signing pipeline.
Signature fix — RELEASE_NOTES.md now included in integrity checksum.
Initial catalogue release with full structural and content-quality validation. All scanner checks pass.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
More from Product Manager
View all →Feature Spec Pipeline
Generate detailed feature specifications from rough ideas, including user stories, acceptance criteria, and edge cases
Roadmap Generation Flow
Full product roadmap generation from vision through to themed, time-bound initiatives with dependency mapping, resource allocation, and stakeholder-ready output
User Research Pipeline
Plan and synthesize user interviews, surveys, and feedback into actionable insights