hoavdc/CodexKit / skills/codexkit-execution-planner
codexkit-execution-planner
VerifiedTurn ambiguous requests into an executable implementation plan with assumptions, sequence, acceptance checks, and rollback thinking.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.2 KB |
| agents/openai.yaml | config | 228 B |
| examples/common-mistakes.md | markdown | 791 B |
| examples/good-output.md | markdown | 742 B |
| references/plan-template.md | markdown | 169 B |
| verification/checklist.md | markdown | 1.3 KB |
verification/checklist.md
View on GitHub# 4C Verification Checklist — Execution Planner
> Use this checklist after generating output. Answer each question honestly.
## Correctness — Is it right?
- [ ] Every task has a single accountable owner — no "TBD" allowed
- [ ] Dependencies are mapped and sequenced correctly (no circular refs)
- [ ] Timeline estimates are justified by evidence, not default padding
## Completeness — Is it done?
- [ ] All workstreams from the brief are represented as tasks
- [ ] Risk mitigations are paired with every High/Critical risk
- [ ] Success criteria are defined before execution starts
## Context-fit — Does it match?
- [ ] Plan granularity matches the audience (exec summary vs team sprint plan)
- [ ] Resource assumptions reflect actual team capacity, not wishful thinking
- [ ] Milestones align with known external deadlines (board meetings, launches)
## Consequence — Is it safe to use?
- [ ] If a critical-path task slips by 1 week, is the impact visible in the plan?
- [ ] If this plan is shared with the CEO, are any gaps in reasoning exposed?
- [ ] If a new team member reads this, can they find their tasks within 2 minutes?
---
**Final question:** _If this output were used immediately in production, what is the single biggest risk?_
Write the answer here before considering the skill output complete.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 466k | Updated | Claude CodeCodex | Verified | Install |
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 466k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |