handoff-to-buildlisted

Ship a locked pack + blueprint to a build repository that is SEPARATE from the idea workspace, so the coding agents there arrive already knowing the specs exist, that they are frozen, how to resolve an id, and where a spec defect goes. Only for the two-repo case - when the code lives in the same repo as the idea workspace there is nothing to generate, because the plugin already does this natively. Use after gate BP passes, after every blueprint amendment, and whenever a build session in that repo reports it had to guess.
vuongdam2k01/SaaS-idea-brainstorm · ★ 0 · AI & Automation · score 70

Install: claude install-skill vuongdam2k01/SaaS-idea-brainstorm

Load `method-rules`; read `state.json`. Everything here is generated from artifacts that are already locked: this skill adds **no** founder judgement and authors **no** product statement. ## First, check whether it is needed at all **If the code will live in the same repository as `ideas/<slug>/` — stop. There is nothing to run.** The plugin covers that case natively, with nothing generated, nothing to regenerate after an amendment, nothing to collide with another plugin, and nothing that can go stale: | already native | what it does | |---|---| | `session-start.js` | injects the standing build contract every session (and after a compaction) whenever a blueprint is locked: the two layers, amendment-log-first, and the product-vs-technical line | | `spec-awareness.js` (PostToolUse on `Read`) | on the first spec file a session opens, injects the anchor mechanism, the id vocabulary, "read-only", and the routing for a defect | | `guard-thresholds.js` (PreToolUse) | blocks an edit to a locked artifact and names `amend-blueprint` | | `/saas-idea-brainstorm:spec` | resolves any id to the file, section and text that **defines** it, built from the artifacts on demand | | `/saas-idea-brainstorm:spec-gap` | triages a suspected gap and routes a real one to `amend-blueprint` | Say that plainly and stop. The generator refuses a same-repo target anyway: a copy inside the tree the pipeline guards would be a freely editable twin of a frozen file, because the guard hooks scope to paths unde