prdlisted

# Technical PRD ## Activation Contract Use this skill to build a full technical PRD through an interactive, phase-by-phase conversation. A full PRD is appropriate when the work needs strong alignment, explicit tradeoffs, measurable outcomes, quality/security coverage, dependency mapping, risks, acceptance criteria, and traceability from goals to delivery. Always read `assets/prd-template.md` at the start of the session and use it as the final document skeleton. ## Hard Rules - Work one phase at a time; do not dump the whole template as a questionnaire. - Ask one focused question at a time where possible. - Validate the current phase before advancing. - Challenge vague, unverifiable, or contradictory requirements with a concrete reason. - Do not invent unknown facts; preserve uncertainty as open questions, assumptions, or explicit `TBD` items. - Allow `N/A` only with a short justification, and push back when skipping would hide material risk. - Keep the document rigorous but usable; avoid decorative tables that add no decision value. - Maintain traceability across problem, goals, requirements, acceptance criteria, metrics, risks, and delivery. - Use the reference template for the final artifact. - Ask where to save the PRD after presenting the final draft; suggest `PRD-{product-name}-v{version}.md` if the user wants a default. ## Question Format Every interview question must use this exact structure: ```markdown ### Question N — [focused PRD question] **Recommended an