Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Insert urgent work as decimal phase (e.g., 72.1) between existing phases
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-09 | ✗→✓ | ▲ Improved | -30% | 0% |
| case-10 | ✗→✓ | ▲ Improved | -59% | 0% |
| case-15 | ✗→✓ | ▲ Improved | 4% | 0% |
| case-20 | ✗→✓ | ▲ Improved | -55% | 0% |
| case-23 | ✗→✓ | ▲ Improved | -65% | 0% |
<objective> Insert a decimal phase for urgent work discovered mid-milestone that must be completed between existing integer phases.
Uses decimal numbering (72.1, 72.2, etc.) to preserve the logical sequence of planned phases while accommodating urgent insertions.
Purpose: Handle urgent work discovered during execution without renumbering entire roadmap. </objective>
<execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/insert-phase.md </execution_context>
<context> Arguments: $ARGUMENTS (format: <after-phase-number> <description>)
Roadmap and state are resolved in-workflow via init phase-op and targeted tool calls. </context>
<process> Execute the insert-phase workflow from @${CLAUDE_PLUGIN_ROOT}/workflows/insert-phase.md end-to-end. Preserve all validation gates (argument parsing, phase verification, decimal calculation, roadmap updates). </process>
Other measured skills in the registry, with their headline benchmark lift.