← ClaudeAtlas

stage-6-blueprint-templateslisted

Artifact templates for stage 6 of the SaaS validation pipeline. Load when writing that stage's artifacts.
vuongdam2k01/SaaS-idea-brainstorm · ★ 0 · Data & Documents · score 70
Install: claude install-skill vuongdam2k01/SaaS-idea-brainstorm
# Stage 6 — Implementation Blueprint templates (ideas/<slug>/blueprint/) Shared frontmatter for every **pipeline** file below (values per file; `deferred-register.md` is the one maintenance-phase exception, see its own block): ```yaml --- artifact: <matches filename> # e.g. fs-01-upload-report, data-schema idea: <slug> stage: 6 gate: BP status: draft # ready when its checklist has no unanswered cell; locked at gate BP evidence_grade: none # blueprint files are design contracts, not evidence claims rung: baseline-auto pipeline_version: 1.13.0 updated: YYYY-MM-DD --- ``` **Join keys and anchors are load-bearing, not decoration** — `scripts/validate-blueprint.js` parses the first markdown table after each `<!-- bp:… -->` anchor, and joins documents on the id vocabularies below. Keep every anchor, id shape, and fixed token exactly as written (they are identifiers per method-rules §Language — never translated), while all prose and cell contents follow `state.language`: | vocabulary | shape | declared in | referenced by | |---|---|---|---| | feature spec | `fs-NN` (filename `fs-NN-<slug>.md`) | feature-specs/ | overview index, test-plan, event dictionary | | acceptance criterion | `AC-NN-<n>` (NN = its FS) | FS acceptance table | test-plan coverage map | | field | `entity.field` (lowercase snake) | data-schema entities | FS field tables, api-contract cells (`entity.field: type`) | | screen | `SC-<n>` | ux-spec screen inventory | FS states, flo