Skip to content

Basinfy/Basinfy-SaaS-Studio / .claude/skills/saas-architecture-review

saas-architecture-review

Verified

Review PRD-to-ADR traceability, cross-ADR conflicts, and stack boundaries.

references/9-handoff.md

View on GitHub
# /saas-architecture-review — Phase 9: Handoff

> Part of `/saas-architecture-review`. `SKILL.md` names when to read this file; the settings it
> resolved and the rules under its later headings still apply here.

## Phase 9: Handoff

After completing the review and writing approved files, present:

1. **Immediate actions**: List the top 3 ADRs to create (highest-impact gaps first,
   Foundation layer before Feature layer)
2. **Pre-gate checklist**: Check whether these exist via Glob and mark each ✅ or ❌:
   - the stack's test root — `tests/unit/` and `tests/integration/` (Next.js / FastAPI), `tests/` (Cloudflare) — if ❌: run `/saas-test-setup`
   - `.github/workflows/tests.yml` — if ❌: run `/saas-test-setup`
   - `design/accessibility-requirements.md` — if ❌: run `/saas-ux-design`
   - `design/ux/interaction-patterns.md` — if ❌: run `/saas-ux-design`
   Present ❌ items as required steps before gate-check. Do not offer `/saas-gate-check`
   as an option if any item is ❌ — offer the missing skill to run instead.
3. **Rerun trigger**: "Re-run `/saas-architecture-review` after each new ADR is written
   to verify coverage improves"

Then close with `AskUserQuestion` tailored to the pre-gate checklist state:
- If ADR gaps remain or any pre-gate item is ❌:
  - "Architecture review complete. What would you like to do next?"
    - [A] Write a missing ADR — open a fresh session and run `/saas-architecture-decision [system]`
    - [B] Run `/saas-test-setup` — required before gate-check (only show if test infrastructure is ❌)
    - [C] Run `/saas-ux-design` — required before gate-check (only show if UX/accessibility files are ❌)
    - [D] Stop here for this session
- If all pre-gate checklist items are ✅ and no blocking ADR gaps remain:
  - "Architecture review complete. All pre-gate items confirmed. What would you like to do next?"
    - [A] Run `/saas-gate-check pre-production`
    - [B] Write a missing ADR — open a fresh session and run `/saas-architecture-decision [system]`
    - [C] Stop here for this session

---
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall