ds-blueprint

/ds-blueprint

Can't improve what you don't measure. Skill scores project across 9 dimensions, writes the signal inventory every other skill scopes itself by, and tells you exactly where to focus next.

Project Health System — Profile-based assessment, transformation, and progress tracking.

Completion Evidence — applies to every phase: Report done/OK only with the machine-checkable evidence the gates name — the exact command run and its observed output (or file:line diff). Missing evidence → report INCOMPLETE plus what is missing. Self-assessment is never evidence. (This band repeats at file end by design — both copies are normative.)

Triggers

• User runs /ds-blueprint
• User asks to assess project health/quality/status, or for a profile, health score, or dashboard
• User asks "how healthy is this project" or "what should I improve"
• First time working on new project (suggest profile creation)
• Verification-infrastructure gap (no CI/tests/linter) surfaces during any task (suggest audit, don't auto-invoke)

Triggers — INVOKE / DON'T INVOKE

INVOKE	DON'T INVOKE
"score project health", "what should I improve first"	"fix the issues" (→ ds-review or ds-fix)
"create project profile", "refresh blueprint"	"research industry best practices" (→ ds-research)
"blueprint dashboard, 9 dimensions"	"release-candidate report" (→ ds-ship)
"where is this codebase weakest"	"competitor comparison" (→ ds-benchmark)
"project has no CI/tests — what else is missing?"	"scaffold CI from zero on a greenfield project" (→ ds-init)

Contract

Dimensions: B2, B4 (contributor), A9 (signal)

• Signal counting, not file:line finding lists. Only modifies the profile section of the instruction file; suggests next steps but never invokes other skills or fixes code.
• Standalone. Uses blueprint profile or ds/audit/findings.md when available; own analysis when absent. Shared formats: ../core/findings-and-profile-format.md; signal keys and detection: ../core/signal-inventory.md; severity and score: ../core/severity-score-categories.md.
• Full accounting enforced: every finding and planned check ends in an explicit disposition (fixed / skipped + reason / only you can do); summary totals balance.
• Pre-existing / out-of-scope errors detected during work are NOT skipped — fixed inline or escalated with concrete blocker.
• SSOT (W10): ds/audit/findings.md is every fix skill's single source of truth — blueprint MUST detect every issue in-scope (a miss stays unfixed downstream). Consumers (ds-review, ds-fix, …) defer to a fresh copy — fresh = git_hash == HEAD AND from this run-cycle (this invocation, or its orchestration run) — verify + apply only, never re-detect blueprint's owned scopes. Stale/missing → orchestrated: invoke /ds-blueprint --refresh and wait; standalone: announce findings stale — running own {scopes} analysis, scan, append with own source + current git_hash (prior-cycle rows = diff baseline only). Re-detecting a covered scope this cycle violates W10; skipping a re-scan for a recent prior cycle violates W11.
• Privacy has one owner. privacy findings come from ds-compliance (canonical); blueprint consumes them for Security & Privacy when present, else scores from security alone (dashboard: privacy: not scanned (ds-compliance)). Blueprint never writes privacy rows.
• Overwrite-only persistence: state (ds/audit/blueprint.json — a full 9-dimension scan holds its progress nowhere else, so an interruption restarts it from zero), findings, and profile rewritten every run — never appended. Run history lives in git log -- <instruction-file>, not in profile or ds/audit/.
• Human-action items: findings needing human-only access (branch protection, CI/repo secrets, store/account setup, key rotation, purchases) get a distinct Human actions block in Dashboard + Summary — never dropped, never marked fixed by the AI.
• Dev-Value Gate on every profile line (../core/findings-and-profile-format.md § 2, forbidden-line list there): a line earns its place only if it makes AI engineering measurably better for the next 6 months; forbidden classes go to README/CHANGELOG/git log/terminal summary.