feature-flow

Name: feature-flow
Availability: InStock
Author: thegeronimo

Coordinates Hyperopen feature changes via ExecPlan generation, test scaffolding, and reviewer handoffs.

44|8|Updated Jul 14, 2025

Search Tags:#workflow #testing #refactor #review #orchestrate #exec-plan

Ready to run

npx skills add https://github.com/thegeronimo/hyperopen --skill feature-flow-thegeronimo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-flow
Source: https://github.com/thegeronimo/hyperopen/tree/main/.agents/skills/feature-flow
Command: npx skills add https://github.com/thegeronimo/hyperopen --skill feature-flow-thegeronimo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill Flow coordinates large Hyperopen changes that require orchestration beyond a single-file implementation, providing a structured ExecPlan, review cycle, and test coverage scaffolding to keep efforts aligned and auditable.

Core Features & Use Cases

Orchestrates large feature work: generates and tracks an ExecPlan, aligns stakeholders, and provisions targeted tests.
Enforces guardrails and roles: restricts edits to the worker and ensures proper sequencing of planning, testing, and review.
End-to-end workflow support: coordinates planning, implementation, testing, validation, and signoff for complex, multi-file changes.

Quick Start

Describe a large feature change you want to implement and run the feature-flow skill to generate an ExecPlan and coordinate tests.

Frequently Asked Questions about feature-flow

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

FAQPage Schema

How do I orchestrate multi-file migrations and large refactors without losing track of changes?▼

Yes, testing is enforced through a deterministic workflow that provisions acceptance tests, edge case tests, and TDD test writers. This scaffolding ensures complex feature rollouts undergo staged validation before the final reviewer signoff.

What is the best way to plan staged validation for complex feature rollouts?▼

The best way to plan staged validation is using an ExecPlan to sequence implementation, testing, and review. This orchestrates feature rollouts by enforcing guardrails and restricting worker edits to ensure proper sequencing.

Can I restrict worker edits to specific directories during a multi-file migration?▼

Yes, you can restrict worker edits to specific directories like /hyperopen/src/** during orchestration. Enforcing these guardrails ensures workers only modify approved files while the ExecPlan tracks the overall progress.

How does an ExecPlan coordinate reviewer handoffs for large refactors?▼

An ExecPlan coordinates reviewer handoffs by enforcing a deterministic workflow that sequences planning, implementation, and testing before review. This ensures large refactors pass through staged validation and signoff.

Do I need an ExecPlan to coordinate complex feature changes across a codebase?▼

Yes, an ExecPlan is required to coordinate complex feature changes because it orchestrates test scaffolding and reviewer handoffs. This provides structured planning, guardrails, and staged validation for multi-file migrations.