From cipherpowers
Verifies batch code implementation exactly matches plan specifications for adherence, not quality. Use after plan batch execution, during /cipherpowers:verify execute, or before next batch.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cipherpowers:verifying-plan-executionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Verify that implementation matches plan specification exactly. This is plan adherence verification, NOT code quality review.
Verify that implementation matches plan specification exactly. This is plan adherence verification, NOT code quality review.
Your only job: Did implementation match what the plan specified? Not your job: Is the code good? (that's code-review-agent)
Announce at start: "I'm using the verifying-plan-execution skill to check plan adherence."
/cipherpowers:verify executeFor the specified batch, extract:
Review all code changes:
For each task:
Task [N]: [specification from plan]
Verification:
- Required: [what plan specified]
- Found: [what implementation contains]
- Status: COMPLETE / INCOMPLETE / DEVIATED
COMPLETE = Task implemented exactly as specified
INCOMPLETE = Task partially done, missing requirements, or skipped
DEVIATED = Task done differently than plan specified
Save to: .work/{YYYY-MM-DD}-verify-execute-{HHmmss}.md
Report structure:
# Execute Completion Review - Batch [N]
## Metadata
- Review Date: {YYYY-MM-DD HH:mm:ss}
- Batch: [number]
- Plan File: [path]
- Tasks Reviewed: [identifiers]
## Summary
- Tasks Complete: X/Y
- Tasks Incomplete: X/Y
- Tasks Deviated: X/Y
- BLOCKING Issues: X
- NON-BLOCKING Issues: X
## BLOCKING (Must Fix)
[issues with Task, Plan specified, Implementation, Status, Impact, Action]
## NON-BLOCKING
[same structure or "None"]
## Tasks Verified Complete
[verified tasks with confirmation]
## Overall Assessment
COMPLETE / INCOMPLETE / PARTIAL
End with: STATUS: OK (all complete) or STATUS: BLOCKED (issues found)
npx claudepluginhub cipherstash/cipherpowers --plugin cipherpowersAudits post-implementation plans against changes by parsing checkboxes for completeness and accuracy. Supports autonomy modes (Autopilot, Critical, Verbose) and file-review. Invoke via /verify-plan.
Verifies code implementation against plan document: reads plan from disk, inspects codebase independently, runs full tests. Outputs structured PASS/FAIL review to file. Use post-execution.
Audits plan execution by checking file existence, content changes, deletions, and commands against the session plan file. Use as final step after implementing plans.