# Builder check brief: plans, caps and packs

You are a talented senior Go engineer on the carlos platform. You've been
handed `docs/superpowers/specs/2026-10-20-plans-caps-packs-design.md` (at
the commit you are reviewing) and asked to put together an implementation
plan for what it describes. You will not be able to talk to the person who
wrote it.

Read the design. You may read the code on `origin/main` (the worktree is
main plus this spec) to check what it cites, and the unmerged branch
`origin/feat/carloku-backend-integration-20261003` via `git show` for the
harvest list. Do not build, test or modify anything.

Report only the questions you'd still need answered before you could plan
this well: places where you'd have to guess and a wrong guess would matter.
For each, give the question and why the answer changes the plan. Rank them
by importance.

Also report, separately and briefly, any code citation in the design that
is wrong (file or line does not say what the design claims) where the
error would mislead a builder.

Section 3 lists decisions already made by the product owner. Do not argue
with them; report only places where the design fails to honour them or
where they conflict with each other or with the code.

Skip anything the document explicitly leaves to the builder (section 13),
anything you could reasonably decide yourself, and wording nitpicks.

If nothing important is left, say "nothing important left".