df:insert-objective

Insert decimal-numbered objectives between existing roadmap items without renumbering.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/AO-Cyber-Systems/devflow-claude --skill df-insert-objective
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: df:insert-objective
Source: https://github.com/AO-Cyber-Systems/devflow-claude/tree/main/skills/df-insert-objective
Command: npx skills add https://github.com/AO-Cyber-Systems/devflow-claude --skill df-insert-objective

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Insert urgent mid-milestone work as a decimal objective between existing objectives, preserving roadmap integrity while accommodating priority shifts.

Core Features & Use Cases

  • Decimal insertion: place new objectives with decimal identifiers (e.g., 72.1) into the roadmap without renumbering existing items.
  • Validation gates: ensures proper argument structure, validates the target decimal position, and updates the roadmap consistently.
  • Use Case: during a milestone, a high-priority task arises that must be slotted between 72 and 73; this skill inserts 72.1 and leaves 72.2, 72.3 intact.

Quick Start

Insert a new urgent objective after 72 with description 'security review' and assign it the decimal label 72.1.

Frequently Asked Questions about df:insert-objective

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

FAQPage Schema
How do I insert an urgent objective between existing roadmap milestones without renumbering?

Insert an urgent mid-milestone objective by applying decimal numbering to place a new item, such as 72.1, between existing entries. This preserves roadmap integrity while accommodating priority shifts without altering the original sequence.

What is decimal objective insertion in roadmap management?

Decimal objective insertion is a roadmap management technique that slots urgent work as a decimal-numbered objective, such as 72.1, between existing milestones. It calculates precise decimal positions to accommodate priority shifts while preserving the original sequence.

How to add a high-priority task between milestones 72 and 73 in a roadmap?

Insert a decimal objective labeled 72.1 into the roadmap between milestones 72 and 73. Validation gates verify the target decimal position and update the roadmap consistently to ensure precise sequencing is preserved.

Does decimal objective insertion support validation for argument parsing and position verification?

Decimal objective insertion implements validation gates for argument parsing, objective verification, decimal calculation, and roadmap updates. These validation checks ensure proper argument structure and validate the target decimal position before applying changes.

When do I need to use decimal numbering for roadmap objectives?

You need decimal numbering for roadmap objectives when a high-priority task arises mid-milestone and must be slotted between existing items, such as between 72 and 73. It accommodates priority shifts while maintaining precise sequencing and roadmap integrity.

What are the limitations of inserting decimal objectives into an existing roadmap?

A limitation of inserting decimal objectives is that it requires precise decimal calculation and validation gates to avoid sequencing conflicts. You must verify the target decimal position carefully to prevent issues when multiple urgent objectives are inserted between the same milestones.