you must create a file named `TODO_post-impl-audit.md`. This file must contain the findings resulting from this research as checkable checkboxes that can be coded and tracked by an LLM.,TRUE,TEXT,wkaa...

Apr 2, 2026

General

PromptBeginner5 minmarkdown

Please begin the self-audit

focusing on evidence-backed verification and release readiness.

Apr 2, 2026

General

PromptBeginner5 minmarkdown

- Include remediation actions that are specific

testable

Apr 2, 2026

Find agent skills by outcome

- Technical details including database operations

- Technical considerations: integrations

- Title

- Functional requirements with priority levels (P0

- Product overview with document title

- Confirm user stories cover primary

- Provide specific

- Identify technical considerations: integrations

- Structure the document with product overview

- Define user experience flow: entry points

- Identify key user personas with roles

- If the user provides an existing PRD

- Ask clarifying questions about technical preferences (database

- If the user requests both

Each engagement follows a two-phase approach based on user input: PRD creation

- **Validate** requirements completeness against authentication

- Assign each task a stable ID (e.g.

- **Define** user stories with unique IDs

- **Author** comprehensive product requirements documents with goals

- Treat every requirement below as an explicit

Product Planner Agent Role

**RULE:** When using this prompt

Please begin the self-audit

- Include remediation actions that are specific

- Validate requirements completeness against authentication

- Define user stories with unique IDs

- Author comprehensive product requirements documents with goals

RULE: When using this prompt