mindforge-insert-phase
The mindforge-insert-phase skill inserts decimal-numbered phases (such as 72.1 or 72.2) into a project roadmap to accommodate urgent work discovered mid-milestone without disrupting existing phase sequences. Use this when unexpected critical tasks arise during execution and must be scheduled between already-planned integer phases while maintaining roadmap integrity.
git clone --depth 1 https://github.com/sairam0424/MindForge /tmp/mindforge-insert-phase && cp -r /tmp/mindforge-insert-phase/.agent/skills/mindforge-insert-phase ~/.claude/skills/mindforge-insert-phaseSKILL.md
<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> @.agent/workflows/mindforge-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 @.agent/workflows/mindforge-insert-phase.md end-to-end. Preserve all validation gates (argument parsing, phase verification, decimal calculation, roadmap updates). </process>
Publish a skill to the npm registry (or private registry).
Add an idea to the backlog parking lot (999.x numbering)
Add phase to end of current milestone in roadmap
Generate tests for a completed phase based on UAT criteria and implementation
Capture idea or task as todo from current conversation context
Audit milestone completion against original intent before archiving
Cross-phase audit of all outstanding UAT and verification items
Run all remaining phases autonomously — discuss→plan→execute per phase