plan-extend

Append milestones to an active Cycle in a YAML workflow.

24|3|Updated Apr 22, 2026

Search Tags:#automation #workflow #planning #state-management #milestone #cycle #prompt-generation

Ready to run

npx skills add https://github.com/HypoxanthineOvO/Hypo-Workflow --skill plan-extend

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-extend
Source: https://github.com/HypoxanthineOvO/Hypo-Workflow/tree/main/skills/plan-extend
Command: npx skills add https://github.com/HypoxanthineOvO/Hypo-Workflow --skill plan-extend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Append new milestones to an active Cycle without closing or reopening the Cycle, preserving history and workflow continuity.

Core Features & Use Cases

Interactive milestone extension: add one or more milestones to the current active Cycle.
Automated prompt generation and state updates: create prompts under .pipeline/prompts/ and append milestones to state.yaml; refresh cycle metadata as needed.
Safe integration with existing workflow: update PROGRESS.md and log.yaml when present, without disturbing existing milestones.

Quick Start

Run /hw:plan:extend to append new milestones to your active Cycle.

Frequently Asked Questions about plan-extend

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

FAQPage Schema

How do I add new milestones to an active workflow cycle without closing it?▼

Extending an active cycle requires appending new milestones directly to the current workflow. This process targets active cycles by updating cycle.yaml and state.yaml, allowing interactive milestone splitting and prompt generation while preserving workflow continuity and existing history.

Can I append milestones to a cycle if the state.yaml file is missing?▼

Appending milestones requires a present .pipeline/state.yaml file and a valid .pipeline/cycle.yaml with cycle.status set to active. Without these required state tracking configurations, the interactive milestone extension cannot safely integrate with the existing workflow.

How does milestone extension update existing workflow state and progress logs?▼

Milestone extension safely updates workflow state by appending milestones to state.yaml and refreshing cycle metadata. When present, it also updates PROGRESS.md and log.yaml without disturbing existing milestones, preserving workflow continuity and history.

When do I need to extend a cycle instead of closing and reopening it?▼

You need to extend a cycle when appending new milestones to an active workflow while preserving history and continuity. This avoids the disruption of closing and reopening the cycle, ensuring safe integration with existing milestones and state tracking.

Does extending an active cycle generate prompts for the new milestones?▼

Extending an active cycle includes automated prompt generation for new milestones. It creates prompts under the .pipeline/prompts/ directory, utilizing an optional prompts directory to support the newly added workflow milestones.