Basinfy/Basinfy-SaaS-Studio / .claude/skills/saas-architecture-review
saas-architecture-review
VerifiedReview PRD-to-ADR traceability, cross-ADR conflicts, and stack boundaries.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.7 KB |
| references/1-load.md | markdown | 10.0 KB |
| references/2-extract-requirements.md | markdown | 3.6 KB |
| references/3-traceability.md | markdown | 5.8 KB |
| references/4-conflicts.md | markdown | 4.0 KB |
| references/5-engine.md | markdown | 5.7 KB |
| references/6-document-coverage.md | markdown | 1.0 KB |
| references/7-report.md | markdown | 3.7 KB |
| references/8-write.md | markdown | 8.4 KB |
| references/9-handoff.md | markdown | 2.0 KB |
references/6-document-coverage.md
View on GitHub# /saas-architecture-review — Phase 6: Architecture Document Coverage
> 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 6: Architecture Document Coverage
**If `docs/architecture/architecture.md` does not exist, say so in the report** —
`Architecture document coverage: NOT ASSESSED — no docs/architecture/architecture.md`
— and carry it into the Phase 7 verdict per the trigger list below. Silently
producing no Phase 6 findings reads as an architecture document that was checked
and found clean, which is the opposite of what happened.
If it exists, validate it against PRDs:
- Does every system from `features-modules-index.md` appear in the architecture layers?
- Does the data flow section cover all cross-system communication defined in PRDs?
- Do the API boundaries support all integration requirements from PRDs?
- Are there systems in the architecture doc that have no corresponding PRD
(orphaned architecture)?
---
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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 implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |