post-prd-expanderlisted

# Post-PRD Expander ## Purpose Expand a completed PRD into the full execution-readiness artifact package. A good PRD is necessary but not sufficient. A project is still not execution-ready if it lacks: - explicit scope boundaries - open questions tracking - business and system logic clarity - architecture decisions - dependency and stack rationale - validation and test planning - implementation and issue breakdown - risk visibility - memory and anti-hallucination guardrails - operational runbook context This skill bridges the gap between a strong PRD and a truly build-ready project package. ## When to Use Use this skill when: - PRD.md exists and has passed PRD quality gates - The PRD contains scope, success criteria, and constraints - The project has enough context (problem statement, target user) - The project is ready to move from specification into execution preparation ## When Not to Use Do not use this skill when: - The PRD is still in discovery-only form - The PRD lacks scope, success criteria, or constraints - The project context is too weak (no problem statement, no target user) - The user wants to stay in PRD refinement mode ## Entry Rule The expansion starts only when all of the following are true: - the problem statement is stable enough - the target user is stable enough - core success criteria are visible - major constraints are visible - the PRD is no longer in discovery-only form - the PRD can already support breakdown into implementation planning ##