flow-next-guide

Recommends the smallest sufficient flow-next workflow route from the current starting state.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When working with the flow-next pipeline, it is often unclear which command or stage applies next—strategy, prospect, chart, capture, interview, plan, or work. This Skill removes that ambiguity by acting as a stateless router that matches your current situation to exactly one recommended next workflow.

Core Features & Use Cases

  • Stateless routing matrix: Matches your starting state (no direction, oversized idea, ready spec, planned tasks, and more) against an exact decision table and recommends one route.
  • Read-only operation: Never mutates .flow/ state, never creates specs or tasks, and only runs optional read-only flowctl probes like brief or list to ground its recommendation.
  • Skip guidance: Every recommendation states when a stage can be safely skipped and whether the skip is signal absent or despite unresolved risk, so evidence, consent, and review contracts are never silently dropped.
  • Use Case: You have a vague, oversized idea like multi-tenant billing with unknown pricing risks. Invoke the guide and it routes you to chart first, then briefing, then capture—rather than jumping straight into planning.

Quick Start

Ask the guide which flow-next workflow to run next given that you have a ready spec with unresolved judgment questions.

Frequently Asked Questions about flow-next-guide

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

FAQPage Schema
How do I know which flow-next command to run next?

Invoke the flow-next-guide skill with a description of your current situation. It matches your starting state against a routing matrix and returns one recommended route with a natural-language next prompt, the matching signal, and safe skip conditions.

What is the difference between flow-next chart and capture?

Chart applies when one singular idea is too large for a single capture and consequential unknowns block stating intent. Capture applies when the idea's intent and boundaries can already be stated. Chart is optional and never a mandatory pipeline stage.

Does the flow-next guide modify specs or tasks?

No. The guide is strictly read-only: it never writes under .flow/, never creates charts, specs, or tasks, and never runs flowctl mutation subcommands. It may only run read-only probes like flowctl brief or list to ground a recommendation.

When should I skip the chart stage in flow-next?

Skip chart when intent and boundaries are already stateable—go directly to capture or author the spec. Chart is only warranted for a singular oversized effort whose unknowns block stating intent, and it is never required onboarding.

Can the flow-next guide ask clarifying questions?

Yes, but at most one plain-text numbered prompt per invocation, and only when two routes would materially differ in cost, consent, or discovery-versus-build path. Otherwise it recommends a single route directly.