PRD

Keep the user's outcome, target design, and remaining work in one document. Planning-only requests end with the PRD; continue implementation when already requested.

Define the target

Read the project evidence needed to identify the problem, affected users, and observable success conditions. Ask about missing decisions that materially affect scope or correctness; record reasonable assumptions for other details.

Choose the simplest design that meets the need, correcting the foundation when necessary. Follow Unix philosophy: focused, composable parts, explicit interfaces, and policy and side effects at boundaries. APIs and internal tools also serve users, including developers and operators.