Skip to content

Basinfy/Basinfy-SaaS-Studio / .agents/skills/saas-gate-check

saas-gate-check

Unverified

Evaluate phase readiness across Director Gates (PASS / CONCERNS / NOT ASSESSED / FAIL).

references/gate-pre-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: Technical Setup → Pre-Production


**Required Artifacts:**
- [ ] Engine chosen (CLAUDE.md Technology Stack is not `[CHOOSE]`)
- [ ] Project config populated (`project.yaml` has engine/naming/performance set, or legacy `.claude/docs/technical-preferences.md` populated)
- [ ] Design tokens exists at `design/tokens/design-tokens.md` with at least Sections 1–4 (Visual Identity Foundation)
- [ ] At least 3 Architecture Decision Records in `docs/architecture/` covering
      Foundation-layer systems (scene management, event architecture, save/load)
- [ ] Stack reference docs exist in `docs/engine-reference/[engine]/`
- [ ] Test framework initialized: the stack's test root exists — `tests/unit/` and `tests/integration/` (Next.js / FastAPI), or `tests/` (Cloudflare); see `.claude/docs/directory-structure.md`
- [ ] CI/CD test workflow exists at `.github/workflows/tests.yml` (or equivalent)
- [ ] At least one example test file exists to confirm the framework is functional
- [ ] Master architecture document exists at `docs/architecture/architecture.md`
- [ ] Architecture traceability index exists at `docs/architecture/requirements-traceability.md`
- [ ] `/saas-architecture-review` has been run (a review report file exists in `docs/architecture/`)
- [ ] `design/accessibility-requirements.md` exists with accessibility tier committed
- [ ] `design/ux/interaction-patterns.md` exists (pattern library initialized, even if minimal)

**Which `/saas-architecture-review` report counts.** Read the `Mode:` line of each
`docs/architecture/saas-architecture-review-*.md`, and for each item below use the
newest report whose mode checked it:

| Item | Modes that check it |
|---|---|
| `/saas-architecture-review` has been run | `full` |
| Traceability matrix has zero Foundation layer gaps | `full`, `coverage`, `rtm` |
| Stack audit shows no deprecated API usage | `full`, `engine` |

A `single-prd` report saw one system and a `consistency` report only compared
ADRs, so neither counts here. When no report's mode checked an item,
that item is NOT ASSESSED, never passed on a narrower report: name the newest report's
mode and the run that closes it (run `/saas-architecture-review full`, or the mode
the table names). A report with no `Mode:` line was written before 1.2.0 and
does not say what it checked, so it counts for none of the three, as
`/saas-architecture-review` itself rules.

**Quality Checks:**
- [ ] Architecture decisions cover core systems (rendering, input, state management)
- [ ] Technical preferences have naming conventions and performance budgets set
- [ ] Accessibility tier is defined and documented (even "Basic" is acceptable — undefined is not)
- [ ] At least one screen's UX spec started (often the landing page or core App Shell is designed during Technical Setup)
- [ ] All ADRs have an **Engine Compatibility section** with engine version stamped
- [ ] All ADRs have a **PRD Requirements Addressed section** with explicit PRD linkage
- [ ] No ADR references APIs listed in `docs/engine-reference/[engine]/deprecated-apis.md`
- [ ] All HIGH RISK engine domains (per VERSION.md) have been explicitly addressed
      in the architecture document or flagged as open questions
- [ ] Architecture traceability matrix has **zero Foundation layer gaps**
      (all Foundation requirements must have ADR coverage before Pre-Production)

**ADR Circular Dependency Check**: run the deterministic graph builder rather than
reading every ADR to trace the graph by hand — a manual trace across a dozen ADRs
eventually misses an edge; the script cannot:
```
Bash: bash .claude/scripts/adr-dep-graph.sh
```
It prints `ADRS`, `EDGES` (one `adr-A -> adr-B` per Depends-On reference),
`NO_DEPS_SECTION` (ADRs with no Depends On), `UNFILLED_DEPS` (a Depends On row
still the template's placeholder), a `CYCLE:` line per ADR on a dependency cycle
with its edges into that cycle, `BLOCKED_BY_CYCLE` (ADRs on no cycle that depend
on one) and `ORDER` (the rest, dependencies first).
- **Any `CYCLE:` lines → FAIL**: "Circular ADR dependency: [the nodes on the
  `CYCLE:` lines]. Neither can reach Accepted while the cycle exists. Remove one
  'Depends On' edge shown on a `CYCLE:` line to break the cycle." Name the
  `BLOCKED_BY_CYCLE` ADRs as waiting on the cycle, not as part of it: none of
  their own edges is the one to remove.
- No `CYCLE:` lines → this check passes. But the acyclic result is only as
  trustworthy as the dependency sections are complete: if `NO_DEPS_SECTION` or
  `UNFILLED_DEPS` lists many ADRs, surface that as a CONCERNS note rather than a
  clean pass, naming each `UNFILLED_DEPS` ADR as unfilled (what it depends on is
  unknown, not none).

**Engine Validation** (read `docs/engine-reference/[engine]/VERSION.md` first):
- [ ] ADRs that touch post-cutoff engine APIs are flagged with Knowledge Risk: HIGH/MEDIUM
- [ ] `/saas-architecture-review` stack audit shows no deprecated API usage
- [ ] All ADRs agree on the same engine version (no stale version references)

## 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`** — engine + design tokens §1–4+ + 3+ ADRs + architecture + UX specs started + accessibility doc + traceability index all required
- **`standard`** — design tokens required **only if visual-asset stories exist**; ADRs reduced to **critical (Foundation-layer) only**; UX-specs-started, accessibility doc, interaction-patterns, traceability index → recommended
- **`minimal`** — only **engine configured** required (the minimal floor); everything else **drops**
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
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: 194kUpdated Claude CodeCodexVerifiedInstall