phase-argument-parsing

Parse and normalize phase references with zero-padding and decimal suffixes.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/gonz0w/bgsd-oc --skill phase-argument-parsing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phase-argument-parsing
Source: https://github.com/gonz0w/bgsd-oc/tree/main/skills/phase-argument-parsing
Command: npx skills add https://github.com/gonz0w/bgsd-oc --skill phase-argument-parsing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Multiple agents need to parse phase arguments from user input. This skill standardizes the extraction, normalization (zero-padding), and validation pattern so all agents handle phase references consistently — whether the user types "8", "08", or "8.1".

Core Features & Use Cases

  • Extraction: From $ARGUMENTS, extract phase number (first numeric argument), flags (prefixed with --), and remaining text is description (for insert/add commands).
  • Normalization & Validation: Normalize to two-digit integer parts and preserve decimal suffixes (e.g., 8 -> 08, 2.1 -> 02.1), and validate existence via the roadmap using the bgsd-tools plan:roadmap get-phase route.
  • Directory Lookup: Resolve the phase directory path for downstream planning tasks and ensure consistent routing across phases.

Quick Start

To get an immediate result, ask the AI to normalize a phase reference such as 8 or 08 or 2.1 and return the normalized phase and its directory path.

Frequently Asked Questions about phase-argument-parsing

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

FAQPage Schema
How do I normalize phase numbers consistently across different agents?

Phase argument parsing handles different input variations by extracting the first numeric argument, applying zero-padding to the integer part, and preserving decimal suffixes. It validates phase existence via the bgsd-tools plan route and resolves the full directory path for downstream tasks.

How do I parse decimal phase references like 8.1 without losing the suffix?

Directory lookup resolves the full phase directory path by validating the phase existence via the bgsd-tools plan:find-phase route. This ensures downstream planning tasks receive standardized phase formatting and accurate directory routing for consistent execution.

Can I use bgsd-tools to validate if a phase exists before running planning tasks?

Phase argument parsing extracts flags prefixed with -- alongside the phase number from user input. Remaining text after the numeric argument and flags becomes the description, enabling insert and add commands to receive structured input for downstream planning tasks.

What is the best way to standardize phase formatting for a multi-agent roadmap workflow?

Zero-padding phase numbers ensures consistent lexicographic sorting and uniform directory naming across the roadmap. Normalizing 8 to 08 prevents ordering anomalies and mismatched directory lookups when multiple agents reference different phases concurrently.

Do I need bgsd-tools installed to resolve phase directory paths?

Normalizing phase references with decimal suffixes handles inputs like 8.1 by padding only the integer component to 08.1. The parser isolates the decimal portion during extraction, ensuring the suffix remains unchanged through the zero-padding and validation process.