Back to Skills

validate-implementation-plan

Audits an implementation plan for requirements traceability, avoidable complexity, risky assumptions, and evidence gaps. Use when reviewing an AI-generated or human-authored plan, design proposal, implementation outline, task breakdown, or architecture plan and the user wants a standalone audit report without overwriting the source plan.

1starsUpdated 8/5/2026

Security Assessment

Safe(96/100)
Security Score96/100

About validate-implementation-plan

This skill is an orchestrator that audits an implementation plan for requirements traceability, avoidable complexity, risky assumptions, and evidence gaps, producing a standalone audit report without ever overwriting the source plan. It solves the problem of AI-generated or human-authored plans containing untraceable scope, speculative complexity, or unstated assumptions that only surface during implementation.

A notable feature is its security-first design: the source plan is explicitly treated as untrusted data. Only a dedicated plan-snapshotter subagent reads the raw plan path, and every later stage works from a sanitized, redacted snapshot, numbered requirements, and structured findings rather than raw plan text. Execution is modeled as a strict finite-state machine with a mermaid flow diagram and transition table, retry budgets, and terminal states, and the orchestrator coordinates specialized subagents: a requirements extractor and auditor for traceability, a YAGNI auditor for speculative scope, an assumptions auditor for weak assumptions, an optional technical researcher for local evidence, and a plan annotator that writes the final report. It maintains a strict allow-list of readable paths, refuses to widen it, treats project-specific external website proof as never being valid evidence, and only writes to the snapshot and output paths. The output is a contract-shaped report with pass/fail/blocked/error status and counts of critical, warning, and info findings plus open questions.

Target users are engineering leads, architects, and developers who want a rigorous, tamper-resistant review of a design or implementation plan before committing to build. It is read-and-report oriented with careful trust boundaries and no destructive behavior.

FAQ

Does it modify my original plan?

No. It only writes a sanitized snapshot and a separate audit report; it never overwrites the source plan path.

What inputs does it need?

A required plan path and origin context describing the intended outcome, plus optional output path and source-context paths for baseline and local technical evidence.

How does it treat the plan content for safety?

It treats the plan as untrusted data: only the plan-snapshotter subagent reads the raw file, and downstream stages use a redacted snapshot and structured findings instead of raw text.

What does the audit actually check?

Requirements traceability against numbered requirements, speculative or avoidable complexity (YAGNI), weak or unresolved assumptions, and evidence gaps, with an optional local technical-claim review.

What does the final report contain?

An AUDIT status of PASS, FAIL, BLOCKED, or ERROR, the output path, sections covered, counts of critical, warning, and info findings, open questions, and a one-line reason.

All Files

14 files
flow-diagram.md4.9 KB
View
references/audit-protocol.md7.4 KB
View
references/external-sources.md3.2 KB
View
references/report-example.md3.7 KB
View
references/trust-boundary.md3.6 KB
View
SKILL.md6.3 KB
View
state-machine.md8.1 KB
View
subagents/assumptions-auditor.md4.1 KB
View
subagents/plan-annotator.md3.4 KB
View
subagents/plan-snapshotter.md3.0 KB
View
subagents/requirements-auditor.md2.8 KB
View
subagents/requirements-extractor.md2.7 KB
View
subagents/technical-researcher.md2.4 KB
View
subagents/yagni-auditor.md2.5 KB
View

Install validate-implementation-plan

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill