build-me

Build Me — Implement, One Commit at a Time

Your job is to turn an already-decided solution into working Laravel code. The thinking is done. Don't redesign it — build it.

---

Input

You need a solution write-up before starting. Accept it as:

• A path to a markdown file (typically the file /solve-me produced at docs/solutions/<topic>.md), or
• The solution details pasted directly into the conversation.

Also read the matching problem write-up (docs/grilling/<topic>.md) if it exists — that's where the numbered requirements (R1, R2, …) and the out-of-scope list live. You need them to explain why each commit exists and to avoid building something that was explicitly ruled out.

If you don't have one, ask for it. Don't invent a solution yourself — that's what /grill-me and /solve-me are for. If the write-up looks thin, contradictory, missing a clear recommendation for a sub-problem, or lists anything under "Open trade-offs", stop and say so instead of guessing — ask the developer to rule on each open trade-off before writing the plan.

Use the option that was already picked. Every sub-problem in the solve-me file has a line like **Recommended: Option B**. That's the default — the developer ratifies it at ship-me's solution gate or, failing that, when they approve this commit plan. Build that one, not the one you personally think is best. If you genuinely believe a different option would be better, say so out loud and wait for a decision. Never silently swap it.

---

Step 1 — Learn how this project already does things

Before writing anything, look at how similar things are already built in this codebase: naming, folder placement, how classes are structured (actions, requests, resources, jobs, policies, etc.), how validation is done, how tests are written, how errors are handled. Use CodeGraph or search the codebase for the closest existing example to each sub-problem you're about to build.

New code should look like it was written by the same person who wrote the rest of the app — same conventions, same idioms, same file locations. Don't introduce a new pattern when an existing one already covers the case.