| 1 | # Builder check brief: plans, caps and packs |
| 2 | |
| 3 | You are a talented senior Go engineer on the carlos platform. You've been |
| 4 | handed `docs/superpowers/specs/2026-10-20-plans-caps-packs-design.md` (at |
| 5 | the commit you are reviewing) and asked to put together an implementation |
| 6 | plan for what it describes. You will not be able to talk to the person who |
| 7 | wrote it. |
| 8 | |
| 9 | Read the design. You may read the code on `origin/main` (the worktree is |
| 10 | main plus this spec) to check what it cites, and the unmerged branch |
| 11 | `origin/feat/carloku-backend-integration-20261003` via `git show` for the |
| 12 | harvest list. Do not build, test or modify anything. |
| 13 | |
| 14 | Report only the questions you'd still need answered before you could plan |
| 15 | this well: places where you'd have to guess and a wrong guess would matter. |
| 16 | For each, give the question and why the answer changes the plan. Rank them |
| 17 | by importance. |
| 18 | |
| 19 | Also report, separately and briefly, any code citation in the design that |
| 20 | is wrong (file or line does not say what the design claims) where the |
| 21 | error would mislead a builder. |
| 22 | |
| 23 | Section 3 lists decisions already made by the product owner. Do not argue |
| 24 | with them; report only places where the design fails to honour them or |
| 25 | where they conflict with each other or with the code. |
| 26 | |
| 27 | Skip anything the document explicitly leaves to the builder (section 13), |
| 28 | anything you could reasonably decide yourself, and wording nitpicks. |
| 29 | |
| 30 | If nothing important is left, say "nothing important left". |
| 31 | |
amadan