Basinfy/Basinfy-SaaS-Studio / .agents/skills/saas-gate-check
saas-gate-check
UnverifiedEvaluate phase readiness across Director Gates (PASS / CONCERNS / NOT ASSESSED / FAIL).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.3 KB |
| references/2b-workflow-tier.md | markdown | 7.2 KB |
| references/3-run-gate-check.md | markdown | 9.5 KB |
| references/4-assessment.md | markdown | 8.0 KB |
| references/5-verdict.md | markdown | 8.9 KB |
| references/6-update-stage.md | markdown | 3.2 KB |
| references/7-next-steps.md | markdown | 8.3 KB |
| references/gate-polish.md | markdown | 3.5 KB |
| references/gate-pre-production.md | markdown | 5.8 KB |
| references/gate-production.md | markdown | 7.9 KB |
| references/gate-release.md | markdown | 3.6 KB |
| references/gate-systems-design.md | markdown | 1.8 KB |
| references/gate-technical-setup.md | markdown | 2.4 KB |
references/gate-production.md
View on GitHub> Gate definition, loaded by `/saas-gate-check` for the TARGET PHASE ONLY.
> Never load the other five — one gate applies per invocation.
# Gate: Pre-Production → Production
**Required Artifacts:**
- [ ] Vertical slice exists in `prototypes/` with a REPORT.md (run `/saas-vertical-slice`) — **recommended, not blocking**; if absent, surface as CONCERNS
- [ ] First sprint plan exists in `production/sprints/`
- [ ] Design tokens specification is complete and DS-DESIGN-TOKENS sign-off verdict is recorded in `design/tokens/design-tokens.md` — where `review_mode` skips that gate (`lean`, `solo`), a `SKIPPED` sign-off line `/saas-design-tokens` records stands in for it, and a header still reading `[Not yet reviewed]` on such a project reads "sign-off skipped — [mode] mode", never missing
- [ ] Entity inventory exists at `design/assets/entity-inventory.md` (recommended — run `/saas-asset-spec` with no arguments to generate collaboratively from PRDs + design tokens)
- [ ] All MVP-tier PRDs from systems index are complete
- [ ] Master architecture document exists at `docs/architecture/architecture.md`
- [ ] At least 3 ADRs covering Foundation-layer decisions exist in `docs/architecture/`
- [ ] All Foundation and Core layer ADRs have status `Accepted` (not `Proposed`) — stories cannot be unblocked until their governing ADR is accepted
- [ ] Control manifest exists at `docs/architecture/control-manifest.md`
(generated by `/saas-create-control-manifest` from Accepted ADRs)
- [ ] Epics defined in `production/epics/` with at least Foundation and Core
layer epics present (use `/saas-create-epics layer: foundation` and
`/saas-create-epics layer: core` to create them, then `/saas-create-stories [epic-slug]`
for each epic)
- [ ] Vertical Slice build exists and runs end-to-end (not just scope-defined) — **recommended, not blocking**; if absent, surface as CONCERNS
- [ ] Vertical Slice has been tested with real users in at least 1 documented session — **recommended, not blocking**; if absent, surface as CONCERNS
- [ ] Vertical Slice usability test report exists at `production/qa/usability-tests/` or equivalent — **recommended, not blocking**; if absent, surface as CONCERNS
- [ ] UX specs exist for key screens: dashboard/home, main application shell, core workflows (at `design/ux/`)
- [ ] App shell navigation spec exists at `design/ux/app-shell-navigation-spec.md`
- [ ] All key screen UX specs have passed `/saas-ux-review` (verdict APPROVED or NEEDS REVISION accepted)
**Quality Checks:**
- [ ] **Core value workflow is validated** — usability test data confirms the central workflow is smooth, responsive, and functional. Explicitly check the Vertical Slice report.
- [ ] UX specs cover all UI Requirements sections from MVP-tier PRDs
- [ ] Interaction pattern library documents patterns used in key screens
- [ ] Accessibility tier from `design/accessibility-requirements.md` is addressed in all key screen UX specs
- [ ] Sprint plan references real story file paths from `production/epics/`
(not just PRDs — stories must embed PRD req ID + ADR reference)
- [ ] **Vertical Slice is COMPLETE**, not just scoped — the build demonstrates the full core workflow end-to-end. At least one complete workflow cycle works.
- [ ] Architecture document has no unresolved open questions in Foundation or Core layers
- [ ] All ADRs have Stack Compatibility sections stamped with the stack version
- [ ] All ADRs have ADR Dependencies sections (even if all fields are "None")
- [ ] Manual validation confirms PRDs + architecture + epics are coherent
(run `/saas-review-all-prds` and `/saas-architecture-review` if not done recently)
- [ ] **Core value proposition is delivered** — at least one user independently completed the core workflow and achieved the target outcome.
**Vertical Slice Validation** (only run these checks if a Vertical Slice was built):
- [ ] A user has completed the core workflow without developer guidance
- [ ] The product communicates value and onboarding steps within the first 2 minutes of use
- [ ] No critical blocker bugs exist in the Vertical Slice build
- [ ] The UI interactions feel responsive and intuitive (ask the user)
> **Verdict rules for Vertical Slice:**
> - **Slice was built AND any validation item is NO** → verdict is automatically FAIL. A broken
> or unfun vertical slice should not advance to Production.
> - **Slice was built but its report says NOT ASSESSED** (nobody has played it) → it is not a
> PROCEED, and its validation items were not checked (they are not NO): the Vertical Slice
> Validation block does not run, so the FAIL rule above does not apply. The gate item is NOT
> ASSESSED, never passed — and a "not yet" to "a human has played it" means the same.
> - **Slice was not built (skipped)** → downgrade to CONCERNS only, not FAIL. Surface the risk
> clearly: "Advancing without a validated Vertical Slice increases the risk of late-stage design
> pivots. Recommended before committing full production scope." The user decides.
> - Skipping is a valid solo dev or time-constrained call. Shipping a broken one is not.
## Workflow tier reductions
The checklist above is the **`full` baseline**. At lower tiers apply the
reduction for the resolved tier; items not named keep their status above.
Reductions only ever *relax* a requirement — `workflow_overrides` is the
only thing that adds one.
- **`full`** — sprint plan + complete (9-section) design tokens + epics + UX specs + control manifest all required; **Vertical Slice keeps its Section 2 status** (see note) — its usability test is recommended, 1 documented session with 3+ better
- **`standard`** — epics + sprint plan required; design tokens complete + UX specs + control manifest → recommended; **Vertical Slice keeps its Section 2 status**
- **`minimal`** — the minimal floor only: a filled **`design/product-brief.md`** with its build order, and **stories** under `production/epics/` (`workflow-modes.md` — the brief's build order is the plan, so there is **no sprint plan**); everything else **drops** — sprint plan, epics, usability tests, design tokens, entity inventory, MVP PRDs, the master architecture document, both ADR items, control manifest, the UX items (key screen specs, App Shell document, `/saas-ux-review`), and the Vertical Slice items (the slice, its usability test, and the Vertical Slice Validation block) — the two current-build checks below replace them
**Quality checks at `minimal`:** every check that reads a dropped artifact drops with it — the sprint-plan, architecture, both ADR, PRD-coherence, UX and accessibility checks, and the persona workflow check (no PRD holds one). Two still apply, to the current build instead of a slice: **the core workflow delivers value** (ask the user, or read a usability test note if one exists) and **it runs end to end** — one complete trigger → action → outcome cycle. A "no" to either is FAIL, as a NO on a built slice is at the other tiers; a "not yet" to the value question means nobody has tested the build — NOT ASSESSED.
> **The Vertical Slice keeps its Section 2 status at `full` and `standard`.** The
> Pre-Production → Production "prototype/Vertical Slice" floor is NOT upgraded to
> blocking by the tier table — the Vertical Slice artifacts stay *recommended,
> not blocking* (absent → CONCERNS, not FAIL) exactly as Section 2 defines, at
> `full` and `standard` alike. At `minimal` they drop — the minimal route never
> builds a slice — and the two current-build checks replace them. The
> genuinely-required floor item at this gate is the **sprint plan** at `standard`
> and `full`, and the **brief's build order plus stories** at `minimal`. The one
> hard rule that binds at every tier: if a Vertical Slice *was built* and any of
> its validation items is NO (at `minimal`, if the current build fails either of
> its two checks), the verdict is FAIL regardless of tier — tier reductions relax
> what must *exist*, never what must *work*.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |