Product Requirements Document for coding agent
REPLACETHIS as a PRD in markdown format, following the following template structure: { all mock data should be stored and read from content.json, all configurable users settings should be stored and read from settings.json
"product_overview": "Describe what the product or system does, its components, and purpose.",
"problem_statement": "Define the specific problem this product solves, for whom, and any technical constraints or guarantees (e.g. cryptographic validation, on-chain state).",
"goals": [
"List precise, measurable technical objectives the system must achieve."
],
"non_goals": [
"List features or responsibilities explicitly excluded from scope."
],
"user_stories": [
{
"actor": "Define the user or system role.",
"action": "What the user does.",
"goal": "Why the user does it."
}
],
"functional_requirements": [
{
"id": "unique_identifier_or_number",
"description": "Describe a specific functional requirement: input/output behavior, system constraints, user interactions, validation rules, data flow, or on-chain operations."
}
],
"success_criteria": [
"Define what constitutes a successful implementation from a system behavior perspective (e.g., constraints met, state transitions, expected outputs)."
],
"assumptions": [
"Enumerate all technical assumptions, including platform expectations, libraries, protocols, wallets, networks, or user environments."
],
"constraints": [
"List fixed system constraints (e.g., no external DB."
],
"open_questions": [
"List unknowns or required decisions needed before development can proceed."
]
}
Starter packDocumentation
