blueprint-workspace-scanlisted

# /blueprint:workspace-scan Refresh the monorepo root blueprint's `workspaces.children` registry by walking the filesystem for child `docs/blueprint/manifest.json` files, reading their `feature-tracker.json` when present, and writing cached rollup stats back to the root manifest. ## When to Use This Skill | Use this skill when... | Use `/blueprint:status` instead when... | |------------------------|-----------------------------------------| | Adding or removing a child blueprint | Just inspecting overall blueprint state | | Root `workspaces.children` looks stale | You do not run a monorepo | | Migrating to `format_version` 3.3.0 | You only want per-project details | ## Context - Root manifest: !`find docs/blueprint -maxdepth 1 -name manifest.json` - Candidate child manifests: !`find . -maxdepth 6 -type d \( -name node_modules -o -name .git -o -name dist -o -name build \) -prune -o -type f -path '*/docs/blueprint/manifest.json' -print` - Current scan time: !`date -u +%Y-%m-%dT%H:%M:%SZ` ## Parameters Parse these from `$ARGUMENTS`: - `--dry-run`: Preview discovered children and the JSON that would be written — make no changes. - `--max-depth N`: Maximum directory depth to search (default 4). Increase for deeply nested monorepos. ## Execution Execute this workspace scan: ### Step 1: Verify a root manifest exists If `docs/blueprint/manifest.json` is missing, stop and report that the current directory is not a blueprint root. Suggest `/blueprint:init` for new projects.