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-polish.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: Production → Polish
**Required Artifacts:**
- [ ] The code root has active code organized into subsystems
- [ ] All core features from PRD are implemented (cross-reference `design/prd/` with the code root)
- [ ] Main core business workflow path is functional end-to-end
- [ ] Test files exist under the engine's test root — `tests/unit/` and `tests/integration/` (Jest/Vitest/Pytest) — covering Logic and Integration stories
- [ ] All Logic stories from this sprint have corresponding unit test files in the engine's unit-test location (`tests/unit/` or `tests/integration/`)
- [ ] Smoke check has been run with a PASS or PASS WITH WARNINGS verdict — report exists in `production/qa/` (a `quick` run, labelled `(quick — …)`, does not count: it skipped the coverage scan)
- [ ] At least one QA plan exists in `production/qa/` (generated by `/saas-qa-plan`) covering this sprint, the final production sprint, or this production phase — run `/saas-qa-plan` if missing (CONCERNS — advisory, not blocking)
- [ ] QA sign-off report exists in `production/qa/` (generated by `/saas-team-qa`) with verdict APPROVED or APPROVED WITH CONDITIONS
- [ ] At least 3 distinct usability test sessions documented in `production/qa/usability tests/`
- [ ] Usability test reports cover: new user experience, mid-product systems, and difficulty curve
- [ ] Value proposition hypothesis from Product Concept has been explicitly validated or revised
**Quality Checks:**
- [ ] Tests are passing (run test suite via Bash)
- [ ] No open S1 Critical bugs in any bug tracker or known issues
- [ ] Core business workflow functions as designed (compare to PRD acceptance criteria)
- [ ] Performance is within budget (check `performance.*` in `project.yaml`, else technical-preferences.md targets)
- [ ] Usability test findings have been reviewed and critical user experience issues addressed (not just documented)
- [ ] No "confusion loops" identified — no point in the application where >50% of usability testers got stuck without knowing why
- [ ] Difficulty curve matches the Difficulty Curve design doc (if one exists at `design/usage-limits-quota-model.md`)
- [ ] All implemented screens have corresponding UX specs (no "designed in-code" screens)
- [ ] Interaction pattern library is up-to-date with all patterns used in implementation
- [ ] Accessibility compliance verified against committed tier in `design/accessibility-requirements.md`
## 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`** — core features + Logic/Integration tests + smoke check (PASS or PASS WITH WARNINGS) + QA sign-off + 3+ usability tests all required
- **`standard`** — QA sign-off + per-story test coverage → recommended;
**core features + smoke check + functional end-to-end + 1+ documented
usability test + no open S1 Critical bugs** required
- **`minimal`** — **smoke check + functional end-to-end + no open S1 Critical
bugs** required; the core-features cross-check → recommended; everything
else **drops**. Reductions relax what must *exist*, never what must *work* —
a gate that closes production on "it boots" alone has not asked whether the
product works.
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 |