A Product Requirement Prompt (PRP) is a specification artifact discussed in Agentic Software Engineering: Foundational Pillars and a Research Roadmap that captures a task’s goals, justification, acceptance criteria, and curated context as a “minimum viable packet” for an AI coding agent. The paper describes industry tools such as Amazon’s Kiro as already demonstrating this spec-driven development pattern.
Usage
The paper describes a PRP as typically structured into five sections: (1) Goal & Why, setting the objective and business value; (2) What & Success Criteria, defining scope with verifiable conditions and invariants; (3) All Needed Context, curating relevant documentation and known pitfalls without overloading the agent’s context; (4) Implementation Blueprint, providing strategic guidance and constraints rather than a low-level plan; and (5) Validation Loop, codifying the acceptance-testing strategy. It is used within a Plan-Do-Assess-Review (PDAR) (PDAR) loop, and the paper aligns PRPs with SASE’s own BriefingScript, noting both insist on structured, testable intent.