← ClaudeAtlas

surveylisted

After building a feature (or evaluating a plan), verify it matches what was planned, respects the project's declared architecture and standards, and is production-ready. Reports issues clearly and routes broken behavior to dredge or contested judgment calls to watershed.
partikularwaters/Banka · ★ 3 · AI & Automation · score 76
Install: claude install-skill partikularwaters/Banka
Building is not done when the code runs. It is done when the code is correct — and "correct" is judged against what *this project itself* has declared, never a generic external assumption about what the project must be. ## Context Contract **Required:** the implementation plan from `charter`, if one exists, or the feature description/task given · the resolved tier's declared files (Standard: `architecture.md`, `code-standards.md`, `ui-tokens.md`, and `ui-rules.md`, plus `ui-registry.md` for reuse checks; Core: `architecture.md` and `design.md`; Minimal: the Banka-owned `AGENTS.md` block's Project Overview). **Conditional:** whether the resolved architecture file declares a security, encryption, or access-isolation invariant — only then does Layer 3 treat a violation as high severity, per its own Sensitive-data severity rule. **Excluded by default:** repository content beyond the resolved tier files and the supplied plan/task — survey does not invent invariants the project never declared. **Outputs:** a three-layer review report with reviewer disclosure, a severity-graded issue list, a per-claim production evidence ledger, and — when warranted — a routing recommendation to `dredge` or `watershed`. **Write authority:** none. It does not fix anything itself. ## Resolve Banka state first Before reading project state, inspect `AGENTS.md`, the complete contents of `CLAUDE.md`, `/core/`, `/context/`, and the required tier files. Active schema 2 requires one complete Banka bl