Menu
Verify batch implementation matches plan specification exactly - checks plan adherence, not code quality
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Use boolean decision trees instead of imperatives for 100% compliance under pressure
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
Use when completing tasks, implementing major features, or before merging to verify work meets requirements - dispatches cipherpowers:code-review-agent subagent to review implementation against plan or requirements before proceeding
Establish workflow boundary checklists with clear pass/fail criteria and escalation procedures
Use when you've developed a broadly useful skill and want to contribute it upstream via pull request - guides process of branching, committing, pushing, and creating PR to contribute skills back to upstream repository
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
| name | verifying-plan-execution |
| description | Verify batch implementation matches plan specification exactly - checks plan adherence, not code quality |
| when_to_use | after executing plan batches, during /cipherpowers:verify execute, when checking if implementation matches plan |
| version | 1.0.0 |
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)