mattgierhart/PRD-driven-context-engineering

Architecture Design defines how system components connect and where boundaries, integrations, and constraints belong. Use it when turning stack choices, risks, and features into architecture decisions and system diagrams.

Competitive Landscape Mapping documents current user workarounds, competitor options, and gaps before positioning a product. Use it when moving from problem framing into market definition and competitive analysis.

Environment Setup documents the local tools, packages, config files, and verification steps needed for consistent development. It also records CI/CD and production environment requirements when those are part of the project.

Feature Value Planning defines and prioritizes features with traceability to outcomes, moat, and pricing tiers. Use it when scoping an MVP, mapping parity vs. delta features, or deciding which capabilities belong in each tier.

Gate Check validates whether a PRD stage is ready to advance by reading readiness scores and reporting PASS, WARN, or BLOCK with top blockers. Use it before moving from v0.X to v0.Y or when running /ghm-gate-check.

Harvest extracts durable insights from temp files into source-of-truth documents during EPIC Phase E. Use it when an EPIC finishes or when you explicitly run /ghm-harvest to create new entries and an archive manifest.

ID Register validates and registers new Source of Truth IDs with cross-reference checks. Use it when creating BR, UJ, API, or CFD entries and need a formatted SoT record with confidence and links.

Moat Definition assesses competitor defensibility and switching costs during PRD v0.3 commercial model work. Use it to decide where to compete, where to wedge in, and what targeting rules to document.

Outcome Definition defines measurable success metrics and KPI thresholds for a product PRD. Use it when you need to decide what to measure, set evidence-based targets, and establish go/no-go criteria.

PRD CE Init seeds a fresh repository with PRD-Driven Context Engineering starter files such as PRD.md, SoT, epics, and agent MEMORY templates. Use it when initializing a new project with the methodology scaffold.

PRD-Driven Context Engineering helps turn a product requirement into a structured, testable output with checkpoints and evidence. Use it when working from a PRD or other spec and you need a repeatable handoff with quality gates.

Persona Definition synthesizes behavioral personas from prior-stage evidence for PRD v0.4 journey mapping and marketing. Use it to define users, target segments, and feature relationships from CFD, BR, and FEA artifacts.

Pricing Model Selection chooses and validates a pricing model for a PRD’s commercial plan. Use it to set tiers, pricing floors, competitive positioning, and willingness-to-pay checks when deciding what to charge.

Problem Framing transforms vague product ideas into evidence-anchored problem statements for PRD v0.1. It creates CFD entries, gap assessments, and a structured Why section when starting a new product or feature.

Product Type Classification helps choose whether to build a Clone, Unbundle, Undercut, Slice, Wrapper, or Innovation product from competitive landscape evidence. It records the decision and inherited GTM constraints after PRD v0.2 analysis.

Risk Discovery Interview surfaces market, technical, adoption, resource, dependency, and timing risks through guided questions. Use it during PRD red team review to record mitigations, owners, and priority before stack selection.

Screen Flow Definition turns user journeys into a screen inventory, navigation paths, and shared UI components. Use it when defining screens, information architecture, or wireframe structure from PRD journeys and feature plans.

Self Install installs the PRD-driven context engineering framework into a fresh or existing repository. It runs a wizard, drives the installer, and verifies hooks and readiness without overwriting protected product files.

SoT Builder creates new Source of Truth files when existing templates do not fit a product’s artifact types. Use it to define a new SoT schema, ID prefix, and update protocol for durable tracked records.

Status Sync updates README.md dashboard sections from PRD.md and the active EPIC session state. Use it after gate changes, EPIC status changes, or a `/ghm-status-sync` command.

Technical Stack Selection determines which technologies to reuse, buy, integrate, or build for a product based on features, screens, risks, and existing assets. Use it during PRD v0.5 to document tech decisions and feed architecture design.

Template Sync detects when a repo is behind its template version and prepares a safe migration plan. It checks for missing, stale, and structurally outdated files while protecting product-specific content.

User Journey Mapping turns personas, features, and KPIs into step-by-step user paths from trigger to value moment. Use it when defining user journeys, user flows, or the pain-to-value sequence for a PRD.

User Value Articulation transforms validated pain points into quantified value statements for PRD v0.1. It is used after problem framing to turn CFD pain entries into value hypotheses with evidence tiers and MVP scope signals.

Visual Prototype Gate turns SCR entries into structured prompts for Stitch or similar UI generators, one screen at a time. Use it when you need a visual demo and a feedback template tied back to existing screen IDs.