PRD Skill — Stages & Information Flow
Socratic discovery across four depth levels, seven phases, and six reference files to produce a build-ready requirements document. Grounded in the PuRDy methodology: platform-agnostic, quantification-forward, failure-pattern-aware.
The discovery flow
The reality check routes the request to one of four depth paths — each path runs the same phases at a deeper cut. Every phase is its own node, exactly as the skill draws it.
Each depth path runs the same phases at a deeper cut. Phase-by-phase detail follows.
Phase reference
classification
5 initiative types: Data Integration, Process Automation, Tool Selection, Cross-Functional, Reporting/Analytics. Signal-phrase matching, hybrid detection, gap detection by type. Standard/Deep confirm classification with the user; Light notes it silently.
deep-dive
Current-process mapping, pain points, scale quantification, 5 Whys root-cause analysis, 3M waste classification (Muda / Mura / Muri). Depth decides how deep: Minimal = 2–3 questions, Light = 3–5 min, Standard = 7–10 min with 5 Whys on the primary pain, Deep = full 5 Whys on every pain point + full 3M.
map
Role + decision-power scoring (1–5), resistance analysis, maintainer identification, missing-voices check. Standard covers key stakeholders and approvers. Deep adds full RACI, power/interest scoring, and an explicit resistance strategy for every potential blocker.
inventory
Each system’s role, integration type (API / manual / file transfer), data sensitivity / PII flags, what can’t change, integration-complexity score. Deep adds data-ownership mapping, quality assessment, and transformation-complexity scoring.
criteria
Quantified metrics (current → target), MVP scope boundaries, explicit out-of-scope list. Standard/Deep add a pilot plan and timeline. This is the one phase that never gets skipped — even Minimal asks “what does success look like?”
dependencies
Risk + mitigation pairs, timeline / budget constraints, dependency map. 7-pattern failure scan: Integration Complexity, Ghost Town Build, Pre-Scale Paralysis, Cost Avalanche, Feature Gravity Well, Technical Debt Spiral, Reality Distortion. Standard scans top 3–4; Deep scans all 7. The 40-hour threshold routes large initiatives to formal approval.
prioritization
Impact / effort matrix on the ranked opportunities.
PRD
Build the full or light requirements document from the gathered inputs. Optionally produce a visual diagram first.
Depth levels at a glance
Four escalation levels controlled by project type — the skill scales depth to match scope.
A throwaway sketch.
A buildable first version.
A real internal product.
A platform bet.
Reference files
Six reference files pulled in by phase. The skill reads prd-template.md before starting and scans the others during the conversation.
| Reference file | Used by | Content |
|---|---|---|
| prd-template.md | Phase 7 | Full and Light PRD templates with all sections. |
| initiative-taxonomy.md | Phase 0 | 5 initiative types, signal phrases, failure patterns per type, success benchmarks. |
| question-banks.md | Phases 1, 2, 3 | Context-specific questions: internal tools, stakeholder, training, workflow integration. |
| a3-framework.md | Phase 1 | Current → Target → Gap → Root Cause → Countermeasures structure. |
| failure-patterns.md | Phase 5 | 7 failure patterns with warning signs, prevention strategies, cascade models, immunity scorecard. |
| scale-effort.md | Phases 1, 4, 5 | Kiddie / Olympic / Ocean scale, S/M/L/XL effort tiers, 40-hour threshold, impact/effort matrix. |