ferrox-phase

Modify roadmap phases in ROADMAP.md with numbering and order preservation.

21|9|Updated Jul 21, 2026
One-click install
npx skills add https://github.com/FerroxLabs/ferrox-factory --skill ferrox-phase
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ferrox-phase
Source: https://github.com/FerroxLabs/ferrox-factory/tree/main/skills/ferrox-phase
Command: npx skills add https://github.com/FerroxLabs/ferrox-factory --skill ferrox-phase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you safely modify the roadmap itself without manually editing phase structure, numbering, or workflow order.

Core Features & Use Cases

  • Add phases: Append a new integer phase to the current milestone when work expands normally.
  • Insert urgent work: Create decimal phases such as 72.1 to fit important tasks between existing phases.
  • Remove or edit phases: Delete future phases, renumber follow-on items, or update an existing phase in place.
  • Use Case: A planning agent needs to slip in a blocker fix between two scheduled roadmap phases while preserving the rest of the sequence.

Quick Start

Use the ferrox-phase skill to insert phase 72.1 after phase 72 with a short description of the urgent work.

Frequently Asked Questions about ferrox-phase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I insert an urgent phase between two existing roadmap milestones?

To insert urgent roadmap phases, use a safe command to create a decimal entry like 72.1 between scheduled phases. This preserves the original numbering and execution order without manually renumbering the entire structured release plan.

What is the safest way to modify milestone phases in a ROADMAP.md file?

Modifying milestone phases safely requires automated workflow routing, validation gates, and state-aware operations. This ensures additions, insertions, or edits preserve the structural integrity and execution order of your release roadmap.

Can I remove a future phase and automatically renumber the follow-on items?

Yes, removing future phases automatically renumbers follow-on items to maintain a continuous sequence. State-aware phase operations validate the roadmap structure during deletion to prevent numbering gaps in your milestone planning.

When do I need to use decimal phases for release planning?

Decimal phases are needed for release planning when an urgent scope change or blocker fix must slip in between two existing integer phases. This allows you to inject important tasks without disrupting the current milestone sequence.

Does roadmap editing support in-place corrections to existing phase entries?

Yes, roadmap editing supports in-place corrections to update existing phase entries directly. Validation gates ensure these edits do not break the workflow routing or the execution order of subsequent phases.