buildlisted

# Blueprint: build Read `${CLAUDE_PLUGIN_ROOT}/FORMAT.md` first (or `FORMAT.md` at the repo root if you are working inside the blueprint repo itself). One task per invocation. Stop when it is done. That boundary is the point of this skill — it is what keeps a diff reviewable. ## Select the task Argument may be a slug, a task id (`T4`), both, or nothing. 1. Resolve the feature: argument slug → single `.blueprint/*/tasks.md` → ask. 2. Explicit `T<n>` given → use it, but refuse if its `(after ...)` dependencies are unchecked. Say which. 3. Otherwise take the first `[ ]` task, in phase order, whose dependencies are all `[x]`. 4. All tasks checked → say so, and go to **Phase close** below. ## Load only what the task cites This is the discipline that makes the change focused. For task `T7 ... → C2 | R1.AC1, R1.AC2`, read: - the `### C2` section of architecture.md — files, interface, dependencies - the `R1.AC1` and `R1.AC2` lines of requirements.md - the files the task names, and their existing tests - whatever those files actually call, as far as you need to understand them Do **not** read the whole spec, and do not implement anything that is not in the cited component. Work you notice is needed but that no task covers is a finding, not a licence — note it and raise it at the end. ## Execute 1. If on the repository's default branch, create a feature branch first (`blueprint/<slug>`). Do not commit to `main` directly. 2. Make the change. Match the surrounding cod