gz-plan-audit
Verifies that ADR intent, OBPI scopes, and implementation plans are perfectly aligned before development starts.
Install
mkdir -p .claude/skills/gz-plan-audit && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10184" && unzip -o skill.zip -d .claude/skills/gz-plan-audit && rm skill.zipInstalls to .claude/skills/gz-plan-audit
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Pre-flight alignment audit — verify ADR intent, OBPI brief scope, and plan are aligned before implementation begins. Use when exiting plan mode, before starting implementation, or to catch scope drift between ADR intent and the active OBPI brief.Key capabilities
- →Verify ADR intent against OBPI brief scope
- →Check plan alignment with OBPI requirements
- →Generate alignment audit receipt
- →Identify scope drift and gaps
How it works
It performs a structured comparison between ADR intent, OBPI brief scope, and execution plans to detect drift before implementation.
Inputs & outputs
When to use gz-plan-audit
- →Validate plan alignment before starting tasks
- →Check for scope drift in OBPI
- →Verify ADR consistency with execution steps
About gz-plan-audit
Performs a systematic audit to confirm that Architectural Decision Records (ADR), OBPI briefs, and project plans share the same intent and scope. It prevents implementation errors by identifying discrepancies before code is written.
Pre-flight alignment audit — verify ADR intent, OBPI brief scope, and plan are aligned before implementation begins. Use when exiting plan mode, before starting implementation, or to catch scope drift between ADR intent and the active OBPI brief.
When not to use it
- →When the OBPI ID is missing or incorrect
- →When skipping the ADR-to-OBPI alignment check
Prerequisites
Limitations
- →Requires valid OBPI and ADR identifiers
- →Cannot fix ADR defects automatically
How it compares
It uses a deterministic, hook-enforced audit process rather than relying on casual reading to ensure alignment.
Compared to similar skills
gz-plan-audit side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| gz-plan-audit (this skill) | 0 | 3mo | Review | Advanced |
| confidence-check | 13 | 6mo | Review | Beginner |
| specification-architect | 13 | 10mo | Review | Advanced |
| drift-analysis | 2 | 7mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by tvproductions
View all by tvproductions →You might also like
confidence-check
SuperClaude-Org
Pre-implementation confidence assessment (≥90% required). Use before starting any implementation to verify readiness with duplicate check, architecture compliance, official docs verification, OSS references, and root cause identification.
specification-architect
adrianpuiu
A rigorous, traceability-first system that generates five interconnected architectural documents (blueprint.md, requirements.md, design.md, tasks.md, and validation.md) with complete requirements-to-implementation traceability. Use this skill when users need to architect systems, create technical specifications, or develop structured project documentation with guaranteed traceability.
drift-analysis
avifenesh
This skill should be used when the user asks about "plan drift", "reality check", "comparing docs to code", "project state analysis", "roadmap alignment", "implementation gaps", or needs guidance on identifying discrepancies between documented plans and actual implementation state.
flow-next-plan-review
gmickel
Carmack-level plan review via RepoPrompt or Codex. Use when reviewing Flow epic specs or design docs. Triggers on /flow-next:plan-review.
rfc-check
meta-pytorch
Determine if proposed changes require an RFC. Use when planning significant changes, before starting major work, or when asked whether an RFC is needed.
feature-planning
mhattingpete
Break down feature requests into detailed, implementable plans with clear tasks. Use when user requests a new feature, enhancement, or complex change.