yap

Canonical procedure for authoring and executing a Yap implementation plan under z-yap/resources/plans/: plan shape, z-yap tracking (thread/queue/zettels/paper trail/session zettel), verification, and close-out reconciliation. Apply when the user asks for a plan, phased work, or a feature/refactor broken into milestones.

Load full Yap project and z-yap design-space state, and become aware of the support files and procedure skills for working in the knowledge base.

Spawn an independent reviewer agent to audit Yap code against the project's strict style contract. Use when the user asks to review, audit, or check code quality after implementation, or when a plan includes an audit/review pass. Detects: type assertions, mutation, else blocks, null usage, loose equality, narration comments, missing provenance, ts-pattern violations, fp-ts misuse.