plan-execution
How to read and execute feature plans from the imas-codex plans/ directory. Use when implementing features from plan documents or when the fleet orchestrator dispatches work.
74
62%
Does it follow best practices?
Impact
93%
1.24xAverage score across 3 eval scenarios
Passed
No known issues
Fix and improve this skill with Tessl
tessl review fix ./.github/skills/plan-execution/SKILL.mdEvaluation results
97%
19%Routing Analysis for Feature Plan
Task complexity scoring and agent routing
Dimension scoring present
83%
100%
Task 1a → @engineer
83%
100%
Task 1b → @architect
33%
100%
Task 2a → @architect
33%
100%
Task 2b → @engineer
83%
100%
Parallel tasks identified
100%
70%
Phase ordering respected
100%
100%
Justification per task
100%
100%
Subsection labels used
100%
100%
84%
8%Implement Feature Plan: HTTP Client Retry Logic
Plan execution workflow and commit conventions
Full plan read first
100%
100%
Phase 1 before Phase 2
100%
100%
Task 1a before Task 1b
100%
100%
Phase 1 tests run after phase
100%
100%
Phase 2 tests run after phase
100%
100%
Acceptance criteria noted
0%
100%
Conventional commit format
0%
0%
No plan phase in commit title
100%
70%
Files, tests, acceptance criteria noted per task
50%
75%
Phase subsection labels used
100%
100%
100%
27%Wrap Up a Completed Feature Implementation
Plan lifecycle completion and documentation updates
Plan file deleted
0%
100%
AGENTS.md updated
100%
100%
AGENTS.md has export flags
100%
100%
README.md updated
100%
100%
plans/README.md updated
100%
100%
Completion log produced
100%
100%
Plan deletion rationale in log
30%
100%
- Repository
- iterorganization/imas-codex
- Commit
b0d769b
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.