bts-recipe-blueprintlisted

# Recipe: Blueprint Create a bulletproof implementation spec for: $ARGUMENTS **This recipe creates a SPEC DOCUMENT, not code.** Do NOT write source code files (.ts, .js, .go, .py, .rs, etc.) during this recipe. Only create documents in `.bts/specs/recipes/{id}/`. Code implementation happens in `/bts-implement` AFTER this recipe completes with `<bts>DONE</bts>`. ## Settings Read `.bts/config/settings.yaml` for project-specific limits. Use settings values if present, otherwise use defaults noted in each step. ## Resume Check Before starting, check for an existing recipe: ```bash bts recipe status ``` If active, check the phase to determine resume strategy: **If phase is `discovery`:** Read intent.md. - Status EXPLORING → continue discovery conversation using AskUserQuestion - Status CONFIRMED → proceed to Vision & Roadmap Check **If phase is `scoping`:** Check vision/roadmap state first (in order): 1. If `.bts/specs/vision.md` exists with Status: DRAFT → re-present vision for confirmation. After vision confirmed, check roadmap below. 2. If `.bts/specs/vision.md` CONFIRMED but `.bts/specs/roadmap.md` missing → go to Vision & Roadmap Check step 3b (create roadmap from confirmed vision). 3. If `.bts/specs/roadmap.md` exists with Status: DRAFT → re-present roadmap for confirmation. 4. If scope.md exists → follow the Scoping Loop "On resume" protocol below — re-present if Status is DRAFT, or skip to adaptive loop if CONFIRMED. 5. If scope.md does not exist → go to S