Skip to content
Back to skills

Controlflow Executability Verifier

ASecurity

Use when a saved plan should be tested for cold-start executability before coding, especially for large tasks, weak-confidence plans, or plans whose early phases may be too vague for a fresh executor to follow without hidden context.

  • 13 stars
  • 0 votes
  • 0 copies
  • 6 views
  • Added May 27, 2026
data-ai

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 6, 2026

npx -y skills add Smithbox-ai/ControlFlow --skill controlflow-executability-verifier --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Controlflow Executability Verifier?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Controlflow Executability Verifier
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/smithbox-ai-controlflow-executability-verifier/badge)](https://www.skillsdirectory.com/skills/smithbox-ai-controlflow-executability-verifier)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: controlflow-executability-verifier
description: "Use when a saved plan should be tested for cold-start executability before coding, especially for large tasks, weak-confidence plans, or plans whose early phases may be too vague for a fresh executor to follow without hidden context."
---

# ControlFlow Executability Verifier

## Overview

Simulate the plan as if a fresh agent had only the saved artifact and the repository. This skill adapts ControlFlow's ExecutabilityVerifier to Codex by identifying whether the first tasks are specific enough to execute without invisible assumptions.

## Workflow

1. Read the saved plan artifact first.
2. Simulate only the first few phases or tasks that matter for cold-start execution.
3. For each task, apply an 8-point checklist from [references/executability-checklist.md](references/executability-checklist.md):
   - what_clear
   - where_clear
   - how_clear
   - inputs_defined
   - outputs_defined
   - dependencies_met
   - verify_command_complete
   - test_specifics_concrete
4. Walk through the task using the TDD walk-through from [references/executability-checklist.md](references/executability-checklist.md):
   - open_file
   - read_existing_code
   - write_test_red
   - run_test
   - write_implementation_green
   - run_test_again
   - refactor
5. Stop at the first real blocker for a task and record exactly why it blocks execution.
6. Save the verdict to `plans/artifacts/<task-slug>/executability-verifier.md` using `../../templates/executability-verifier-report-template.md`.
7. Return a structured verdict:
   - `PASS`
   - `FAIL`
   - `WARN`
   - `ABSTAIN`

## Output Shape

- **Status**
- **Tasks Simulated**
- **Per-Task Checklist**
- **Walkthrough Summary**
- **Blocked Steps**
- **Recommendation**
- **Failure Classification** when needed

## Common Mistakes

- Simulating the plan with extra unstated context from memory.
- Continuing a task after a genuine blocker instead of stopping and recording it.
- Treating vague instructions as executable just because an experienced human could guess the intent.

## References

- `references/executability-checklist.md`
- `../../templates/executability-verifier-report-template.md`

Files in this skill

  • SKILL.md2.2 KB
  • references/executability-checklist.md2.7 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.