Skip to main content

Master GIA's Guide to PRD Creation (RDS-GIA)

Intro​

Welcome to the GIA Hyperboost Experience—where I transform scattered product ideas into bulletproof PRDs that survive stakeholder scrutiny. My weapon? Investigative rigor, template fidelity, and iterative refinement. I challenge assumptions, expose gaps, and ensure every section of your PRD can defend itself in the boardroom. You bring the vision, I force-march it through critical examination until it's ready to ship.

  • Intro: I build PRDs that follow your official template exactly, no creative liberties. Every section populated with evidence or explicitly marked as needing research. Zero assumptions, maximum clarity.
  • Product Concept: You get complete documentation—validated requirements, version-controlled iterations, executive one-pager, and handoff guidance—all structured so design and engineering can run with it confidently.

Hyperboost Formula (Summary)​

  • Here's my approach: investigative rigor. Draft–Question–Refine. If sections aren't defensible under critical examination, I challenge them. After we validate the core PRD, we create the executive one-pager and prepare handoff documentation.
  • I follow the official template religiously, challenge weak claims respectfully, and version every three edits. No chaos, no drift, no mystery about what changed when.
  • Every phase delivers concrete artifacts: context summaries, version-controlled PRD drafts, section status tracking, and polished deliverables ready for stakeholder distribution.
  • The result? Not just a document, but a validated requirements system that guides design, development, and launch with confidence.

Process Overview​

You want the blueprint? Here's my step-by-step roadmap:

  • 00: Unified Welcome & Context Intake
  • 01: Comprehensive Analysis & Initial Draft
  • 02: Interactive Refinement
  • 03: Finalization Confirmation
  • 04: One-Pager
  • 05: Masterminds Conclusion

Phase 1: PRD Foundation & Iterative Refinement​

Before we ship a single section, I'm dragging your concept through rigorous validation. We intake complete context, draft the full PRD following the template exactly, then refine through critical questioning until every section is bulletproof.

Step 00: Unified Welcome & Context Intake​

  • I'll scan for Masterminds conversation exports or uploaded files to extract existing context automatically.
  • I'll request a clear, written explanation of what you're building, why, for whom, and what constraints exist—no assumptions, just facts.
  • I consolidate everything into a structured summary and present it back for your confirmation before drafting begins.
  • Only when context is complete and validated do we proceed—garbage in, garbage out is not acceptable.

Deliverables:

  • rds_gia_context_sources: JSON tracking what context sources were provided (exports, files, pasted text).
  • rds_gia_initial_context: Consolidated context summary presented in your language for approval.

Step 01: Comprehensive Analysis & Initial Draft​

  • I'll analyze all provided context and map it to every section of the official PRD template systematically.
  • I generate the complete first draft with all headings, sections, and tables following the template exactly—no deviations.
  • Where your context provides information, I populate those sections with evidence-based content.
  • Where information is missing, I mark it explicitly as [A ser preenchido] rather than guessing.
  • I initialize version control (v001), create section status tracking, and present the full draft for review.

Deliverables:

  • rds_gia_prd_sections_status: JSON tracking status of every PRD section (todo/doing/done).
  • rds_gia_prd_v001: Complete initial PRD draft following template.
  • rds_gia_prd_current_doc: Current working PRD document.
  • rds_gia_prd_versions: JSON array tracking all versions.
  • rds_gia_prd_current_version: String indicating current version (v001).
  • rds_gia_prd_edit_count: Number tracking edits in current version (0).

Step 02: Interactive Refinement​

  • I'll guide you through the template section by section, following order strictly unless you request a specific section.
  • After each change you request, I'll update relevant sections, show the full PRD, and update tracking variables.
  • I challenge weak claims with respectful questions: "What evidence supports this?" "How will we measure success?" "What's the rollback plan?"
  • Every three edits, I automatically create a new version, update tracking, and recommend you download a backup.
  • I never change existing content unless you explicitly request it—every edit is intentional and traceable.

Deliverables:

  • rds_gia_prd_current_doc: Updated PRD presented in full after each change.
  • rds_gia_prd_versions: JSON array with all versions including new ones.
  • rds_gia_prd_current_version: Current version identifier (v002, v003, etc.).
  • rds_gia_prd_edit_count: Updated edit count in current version.
  • rds_gia_prd_sections_status: Updated section completion status.

Step 03: Finalization Confirmation​

  • I'll ask the final confirmation question: are you satisfied with the PRD or do you want more refinement?
  • If you request changes, I route back to Step 02 seamlessly and continue the refinement loop.
  • If you confirm it's ready, I lock it as the final version and prepare to generate the one-pager.
  • No pressure, no deadlines—we proceed on validated confidence, not hope.

Deliverables:

  • rds_gia_prd_final_confirmed: Boolean flag indicating final confirmation.
  • rds_gia_prd_final_doc: Confirmed final PRD, unchanged from approved version.

Phase 2: Executive Deliverables & Handoff​

With the core PRD validated, we create executive summary artifacts and prepare handoff to design, development, and launch teams.

Step 04: One-Pager​

  • I'll generate the complete one-pager in Markdown first, following the embedded template structure exactly.
  • I render it to HTML using mm_html_doc with left sidebar section labels as text, formatted headers, and polished layout.
  • The one-pager is self-contained—readers can understand the initiative, scope, success criteria, and risks from this single artifact.
  • I'll remind you to download both PRD and one-pager as individual DOCX files to your company's standard Google Drive location.

Deliverables:

  • rds_gia_one_pager_md: Complete one-pager in Markdown with full content.
  • rds_gia_one_pager_html: Rendered HTML version with sidebar, headers, and formatting.

Step 05: Masterminds Conclusion​

  • I'll provide a concise completion summary highlighting key accomplishments from our session.
  • I suggest next appropriate Masterminds agents: Jony (design), Linus (delivery), Julie (launch) with context for each.
  • I give final reminders about downloading documents to proper Google Drive location per company standards.
  • Your PRD is ready to guide the next phases of product development confidently.

Deliverables:

  • rds_gia_completion_summary: Markdown summary of accomplishments, next steps, and operational reminders.

Congratulations. You've built a PRD that can withstand scrutiny from engineering, design, legal, executives, and the market. Use it wisely, keep it updated, and most importantly—download it to your Google Drive before closing this session.