flow-next-features

Seeds and maintains a committed user-POV feature drive map at .flow/features/ for QA reuse.

692|55|Updated Dec 26, 2025
One-click install
npx skills add https://github.com/gmickel/gmickel-claude-marketplace --skill flow-next-features
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-next-features
Source: https://github.com/gmickel/gmickel-claude-marketplace/tree/main/plugins/flow-next/codex/skills/flow-next-features
Command: npx skills add https://github.com/gmickel/gmickel-claude-marketplace --skill flow-next-features

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA and drive workflows repeatedly re-derive how a user reaches each feature of an application, wasting verification runs on navigation discovery and known traps. This Skill builds and maintains a committed, user-point-of-view feature map at .flow/features/ so agents can drive features directly from documented routes.

Core Features & Use Cases

  • Seed mode: Interviews the repo to detect surfaces (web, CLI, desktop), proves each route with one live drive, and writes an index plus one contract-shaped file per proven feature.
  • Maintain mode: Audits the existing map against the live app with read-only source readers, live re-drives, and triage of findings into doc drift, harness gaps, or product bugs, shipping corrections as a single chore PR.
  • Proof standards: Enforces doctor checks, action-plus-state evidence capture, real user paths only, and named verdicts (SEEDED, CLEAN, CHANGED, BLOCKED, REFUSED).
  • Use Case: After shipping a new settings page, run the maintain mode to re-drive existing features, detect the unmapped surface, prove it live, and open a PR updating the feature map.

Quick Start

Ask the agent to run the flow-next features skill to seed the user-POV feature map for this repository.

Frequently Asked Questions about flow-next-features

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

FAQPage Schema
How do I create a feature map for QA test automation?

Run the skill in seed mode against a repo with a drivable surface. It interviews the checkout for surface, run command, and drive mechanism, proves each route with one live drive, then writes an index and one file per proven feature under .flow/features/.

How do I keep a feature map up to date as the product changes?

Run maintain mode, which audits the existing map with read-only source readers, re-drives features live, and triages findings into doc drift, harness gaps, or product bugs. Proven corrections ship as a single chore PR; product bugs are reported, never edited.

Does the feature map work with CLI applications?

Yes. CLI surfaces drive directly by running the documented command in a run-owned session and capturing stdout, stderr, and exit code. UI surfaces use the flow-next-drive skill's ladder, and multi-surface repos get per-surface feature groups under one index.

Why does a features run end with BLOCKED or REFUSED?

REFUSED occurs for autonomy markers, no drivable surface, no usable driver, or a broken checkout. BLOCKED occurs for orphaned ports owned by other processes, concurrent isolation failures, or source-reader collapse; the reason line names the specific blocker.

Can autonomous agents trigger the feature map seeding?

No. The skill is user-invoked only and scans environment variables for autonomy markers such as FLOW_RALPH or REVIEW_RECEIPT_PATH. Any hit refuses the run with a typed FEATURES_VERDICT=REFUSED line before any work begins.