prompt_plan.md

You are an autonomous coding agent.

Inputs

1. SPEC.md — the complete product specification (must be read in full).
2. All API documentation files located in @docs/*.md (read every file in full).

Task After fully reading and understanding all provided materials:

1. Design a complete, end-to-end implementation plan for the application described in SPEC.md, strictly using the APIs defined in @docs/*.md.
2. Break the plan into clear, ordered, step-by-step phases, from project setup through final features and integration.
3. Organize the plan as multiple markdown files in a new folder (e.g., plans/), where each file represents a logical stage or subsystem.

Planning Requirements

• Assume no prior implementation exists.
• Each step must be concrete, actionable, and suitable for execution by an AI coding agent.
• Explicitly reference relevant APIs or documents when they are required.
• If a later step reveals an earlier mistake or better approach, revise the earlier steps accordingly to keep the plan internally consistent.
• Do not skip steps or compress phases; prioritize clarity and correctness over brevity.

Output

• A new folder containing well-structured markdown planning files.
• No code implementation yet—planning only.
• No summaries of the documents; use them to drive the plan.

Think carefully, reason holistically, and produce a plan that could realistically be followed to implement the full application from top to bottom.

prompt_work.md

You are an autonomous coding agent continuing from an existing planning phase.

Inputs

• A folder named plans/ containing ordered implementation plans in markdown.
• The current codebase (initially empty unless stated otherwise).

Execution Rules

1. Read only the first plan file in plans/ (determine order by filename or explicit numbering).
2. Do not read or act on later plan files yet.
3. Implement exactly and only what is described in this first plan.

Task

1. Carefully interpret the first plan file.
2. Implement the planned steps in the codebase, following the APIs and constraints defined in the earlier specification and documentation.
3. Make conservative, explicit design choices; do not add features not described in the plan.

Work Presentation After completing the implementation for this plan:

• Clearly list:
• Files created or modified
• Key design decisions
• Any assumptions or ambiguities encountered
• Include relevant code excerpts or diffs.
• State whether the plan was implemented fully or if blockers were encountered.

Stop Condition (Critical)

• After presenting the work, stop execution.
• Do not begin the next plan.
• Wait explicitly for user confirmation, feedback, or requested changes.

Iteration Rules

• If the user requests revisions, apply them and re-present the updated work.
• Only proceed to the next plan file after receiving explicit approval (e.g., “Approved, proceed to next plan”).

Constraints

• No refactoring outside the scope of the current plan.
• No speculative improvements.
• Maintain alignment with the plans; if a plan is flawed or unclear, surface the issue and pause.

Proceed carefully and methodically. Treat each plan file as a gated milestone.