blueprint-init

Initialize Blueprint Development in this project. ## When to Use This Skill | Use this skill when... | Use blueprint-upgrade instead when... | |---|---| | The project has no `docs/blueprint/manifest.json` yet | The project already has a manifest at an older format version | | You're bootstrapping a new project's PRD/ADR/PRP directories | You're migrating v1.x→v2, v2→v3, or v3.x→v3.y | | You want to enable feature tracking and decision detection from scratch | Use blueprint-derive-plans to populate PRDs/ADRs/PRPs after init | | You're configuring task scheduling for the first time | Use blueprint-execute instead when you want auto-detection of next step | ## Steps 1. **Check if already initialized**: - Look for `docs/blueprint/manifest.json` - If exists, read version and ask user: ``` Use AskUserQuestion: question: "Blueprint already initialized (v{version}). What would you like to do?" options: - "Check for upgrades" → run /blueprint:upgrade - "Reinitialize (will reset manifest)" → continue with step 2 - "Cancel" → exit ``` 1a. **Detect monorepo context** (format_version 3.3.0+): - Walk upward from the current directory looking for an ancestor `docs/blueprint/manifest.json` (stop at the repo root or `$HOME`). - If an ancestor root manifest exists, this init is creating a **child** workspace. Capture the relative path from the child back to the root. - Additionally scan descendants (max depth 4, skippi...