all publishers

gmickel

@gmickel source repo

164 published skills · page 1 of 2

  1. ▌
    Flow Next Strategy 4 · gmickel bundle
    Create or update repo-root STRATEGY.md (problem, approach, users, metrics, tracks). Use for strategy or roadmap doc requests.
    724 repo stars
  2. ▌
    Flow Next Memory Migrate 3 · gmickel bundle
    Migrate legacy flat memory files (`.flow/memory/pitfalls.md`, `conventions.md`, `decisions.md`) into the categorized YAML schema. Triggers on /flow-next:memory-migrate, "migrate memory", "convert legacy memory", "lift pitfalls into categorized schema", "convert old memory format". Optional `mode:autofix` token in arguments runs without questions and accepts mechanical defaults for ambiguous classifications. Optional scope hint after the mode token narrows the migration to a specific legacy file (e.g. `pitfalls.md`).
    724 repo stars
  3. ▌
    Flow Next Resolve Pr 4 · gmickel bundle
    Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.
    724 repo stars
  4. ▌
    Flow Next Impl Review 4 · gmickel bundle
    Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.
    724 repo stars
  5. ▌
    Flow Next Plan Review 4 · gmickel bundle
    Carmack-level review of a flow-next spec or plan via the configured backend. Use when asked to review a plan or spec.
    724 repo stars
  6. ▌
    Flow Next Tracker Sync 4 · gmickel bundle
    Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
    724 repo stars
  7. ▌
    Flow Next Worktree Kit 4 · gmickel bundle
    Manage git worktrees (create/list/switch/cleanup) and copy .env files. Use for parallel feature work, isolated review, clean workspace, or when user mentions worktrees.
    724 repo stars
  8. ▌
    Flow Next Memory Migrate 4 · gmickel bundle
    Migrate legacy flat .flow/memory files to the categorized YAML schema. One-time ceremony. Use when asked to migrate flow memory.
    724 repo stars
  9. ▌
    Flow Next Spec Completion Review 3 · gmickel bundle
    Spec completion review - verifies all spec tasks implement the spec requirements. Triggers on /flow-next:spec-completion-review.
    724 repo stars
  10. ▌
    Flow Next Spec Completion Review 4 · gmickel bundle
    Verify that a spec's completed tasks fully implement the spec requirements. Use at spec completion before close.
    724 repo stars
  11. ▌
    Flow Next Drive 4 · gmickel bundle
    Drive any UI surface like a real user - a web app, a Chromium-backed desktop app (Electron / WebView2, reached over CDP), or a genuinely native app (macOS AppKit/SwiftUI, or a non-CDP webview) reached via the Cua Driver / Computer Use. Detects the surface, picks the best available driver, degrades gracefully. Use to navigate sites, verify deployed UI, test web or desktop apps, capture baseline screenshots, drive a sign-in flow, scrape data, fill forms, run an e2e check, or inspect current page state. Triggers on "check the page", "verify UI", "test the site", "test this app", "drive the app", "automate this desktop app", "read docs at", "look up API", "visit URL", "browse", "screenshot", "scrape", "e2e test", "login flow", "capture baseline", "see how it looks", "inspect current", "before redesign", "Electron app", "native app".
    724 repo stars
  12. ▌
    Flow Next Prime 4 · gmickel bundle
    Assess codebase agent and production readiness. Classifies the project, verifies commands run, leads with a verdict and ranked next actions.
    724 repo stars
  13. ▌
    Flow Next Impl Review 3 · gmickel bundle
    John Carmack-level implementation review via Codex, Copilot, Cursor, Claude or a host reviewer. Use when reviewing code changes, PRs, or implementations. Triggers on /flow-next:impl-review.
    724 repo stars
  14. ▌
    Flow Next Plan Review 3 · gmickel bundle
    Carmack-level plan review via Codex, Copilot, Cursor, Claude or a host reviewer. Use when reviewing Flow specs or design docs. Triggers on /flow-next:plan-review.
    724 repo stars
  15. ▌
    Flow Next Visual 4 · gmickel bundle
    Restate a spec, a task, a diff, or the current topic visually as a compact markdown digest. Use when asked to 'show me', 'explain this visually', 'restate that', 'digest the plan', 'walk me through the spec', 'walk me through the tasks', 'walk me through the diff', or when the output is too much text and a shape would land faster. Triggers on /flow-next:visual with an optional spec id, task id, git range, or free-form topic.
    724 repo stars
  16. ▌
    Flow Next Tracker Sync 3 · gmickel bundle
    Project a flow-next spec to Linear, GitHub, GitLab, or Jira and reconcile body, status, and comments. Use for tracker discovery, linking, create-first, push, pull, reconcile, comment, or unlink. Not /flow-next:sync, which is plan-sync.
    724 repo stars
  17. ▌
    Flow Next Worktree Kit 3 · gmickel bundle
    Manage git worktrees (create/list/switch/cleanup) and copy .env files. Use for parallel feature work, isolated review, clean workspace, or when user mentions worktrees.
    724 repo stars
  18. ▌
    Flow Next Capture 6 · gmickel bundle
    Save the current conversation as a source-tagged flow-next spec, then offer review or editing. Use when asked to capture this as a spec.
    724 repo stars
  19. ▌
    Flow Next Make Pr 6 · gmickel bundle
    Open a PR with a cognitive-aid body rendered from flow-next spec state via gh, or a GitLab merge request via glab. Use whenever asked to make or open a PR in a flow-next repo.
    724 repo stars
  20. ▌
    Flow Next Features 4 · gmickel bundle
    Seed or maintain the committed user-POV drive map at .flow/features/ so QA and drive reuse how a user reaches each feature.
    724 repo stars
  21. ▌
    Flow Next Prospect 6 · gmickel bundle
    Generate ranked new ideas grounded in the repo. Use when asked to brainstorm what to build; picking up existing specs or work goes to flow-next-flow.
    724 repo stars
  22. ▌
    Flow Next QA 4 · gmickel bundle
    Live-app QA pass derived from the spec. Drives the running app, files P0/P1/P2 findings with evidence, emits a YES or NO qa_verdict receipt.
    724 repo stars
  23. ▌
    Flow Next Features 3 · gmickel bundle
    Seed or maintain the committed user-POV feature map at `.flow/features/` so QA and drive reuse how a user reaches each feature. Two state-resolved modes: no `.flow/features/` (or explicit init intent) seeds it; a present map maintains it. Triggers on /flow-next:features, "seed the feature map", "maintain the feature map", "feature map", "init features". Never dispatched by `flow --auto`, land, or any autonomous driver.
    724 repo stars
  24. ▌
    Flow Next Prospect 5 · gmickel bundle
    Generate ranked candidate ideas grounded in the repo, upstream of /flow-next:flow. Triggers on /flow-next:prospect with an optional focus hint (concept, path, constraint, or volume).
    724 repo stars
  25. ▌
    Flow Next Strategy 3 · gmickel bundle
    Create or maintain `STRATEGY.md` — the product's target problem, our approach, who it's for, key metrics, and tracks of work. Use when starting a new product, updating direction, or when prompts like 'write our strategy', 'update the roadmap', 'what are we working on', or 'set up the strategy doc' come up. Also fires when `/flow-next:prospect`, `/flow-next:plan`, `/flow-next:refine`, or `/flow-next:capture` need upstream grounding and no strategy doc exists yet.
    724 repo stars
  26. ▌
    Flow Next Map 4 · gmickel bundle
    Build a semantic feature index of the repo via clawpatch map (opt-in). Use when asked to map the repo.
    724 repo stars
  27. ▌
    Flow Next Deps 4 · gmickel bundle
    Show spec dependency graph and execution order. Use when asking 'what's blocking what', 'execution order', 'dependency graph', 'what order should specs run', 'critical path', 'which specs can run in parallel'.
    724 repo stars
  28. ▌
    Flow Next Land 4 · gmickel bundle
    Resolve feedback and CI for one named pull request, then merge when authorized and ready. Emits LAND_VERDICT. Use when asked to land a pull request.
    724 repo stars
  29. ▌
    Flow Next Plan 6 · gmickel bundle
    Break a flow-next spec into reviewed tasks. Run only when asked for a plan or task breakdown, or routed by flow-next-flow; other build requests go to flow-next-flow.
    724 repo stars
  30. ▌
    Flow Next Sync 4 · gmickel bundle
    Manually trigger plan-sync to update downstream task specs after implementation drift. Use when code changes outpace specs.
    724 repo stars
  31. ▌
    Flow Next Work 4 · gmickel bundle
    Execute a flow-next spec or task with workers, gates and commits. Run when the work command is typed or flow-next-flow routes here; plain requests to implement fn-N go to flow-next-flow.
    724 repo stars
  32. ▌
    Flow Next Resolve Pr 3 · gmickel bundle
    Resolve PR review feedback — fetch unresolved threads, triage, dispatch per-thread resolver agents, validate, commit, reply + resolve via GraphQL. Triggers on /flow-next:resolve-pr.
    724 repo stars
  33. ▌
    Flow Next Audit 6 · gmickel bundle
    Audit .flow/memory/ entries against current code and keep, update, consolidate, replace, delete, or harden each. Use when asked to audit memory or graduate a recurring lesson into a gate.
    724 repo stars
  34. ▌
    Flow Next Chart 4 · gmickel bundle
    Decision-map discovery for one oversized unclear idea before capture. Resolve one decision per invocation, brief for capture. Use when asked to chart an idea or work a chart decision.
    724 repo stars
  35. ▌
    Flow Next Sync 3 · gmickel
    Manually trigger plan-sync to update downstream task specs after implementation drift. Use when code changes outpace specs.
    724 repo stars
  36. ▌
    Flow Next Work 3 · gmickel bundle
    Execute a Flow spec or task systematically with git setup, task tracking, quality checks, and commit workflow. Run only by /flow-next:work or when flow-next-flow routes a spec here; any other request to implement, build or work on a spec, Flow-Next named or not, goes to flow-next-flow. Triggers on /flow-next:work with Flow IDs (fn-1-add-oauth, fn-1-add-oauth.2, or legacy fn-1, fn-1.2, fn-1-xxx, fn-1-xxx.2).
    724 repo stars
  37. ▌
    Flow Next 4 · gmickel bundle
    Manage .flow/ tasks and specs. Use for show or list tasks, task status, what is ready, show fn-N. NOT for building or planning work (use flow-next-flow).
    724 repo stars
  38. ▌
    Flow Next Audit 5 · gmickel bundle
    Audit `.flow/memory/` entries against the current codebase and decide Keep / Update / Consolidate / Replace / Delete / Harden per entry. Triggers on /flow-next:audit, "audit memory", "review memory", "refresh learnings", "sweep stale memory", "consolidate overlapping memory entries", "graduate a recurring lesson into a gate". Optional `mode:autofix` token in arguments runs without questions and marks ambiguous as stale (Harden is never auto-applied). Optional scope hint after the mode token (concept, category, module, or path) narrows what gets audited.
    724 repo stars
  39. ▌
    Flow Next Chart 3 · gmickel bundle
    Decision-map discovery for one oversized/unclear idea before capture. Triggers on /flow-next:chart with an unshaped idea, chart id, decision pin, --status, or stored tracker URL. Prompt-first adaptive loop - ground, chart a frontier, resolve one D-ID per invocation, brief for capture.
    724 repo stars
  40. ▌
    Flow Next Drive 3 · gmickel bundle
    Drive any UI surface like a real user - a web app, a Chromium-backed desktop app (Electron / WebView2, reached over CDP), or a genuinely native app (macOS AppKit/SwiftUI, or a non-CDP webview) reached via the Cua Driver / Computer Use. Detects the surface, picks the best available driver, degrades gracefully. Use to navigate sites, verify deployed UI, test web or desktop apps, capture baseline screenshots, drive a sign-in flow, scrape data, fill forms, run an e2e check, or inspect current page state. Triggers on "check the page", "verify UI", "test the site", "test this app", "drive the app", "automate this desktop app", "read docs at", "look up API", "visit URL", "browse", "screenshot", "scrape", "e2e test", "login flow", "capture baseline", "see how it looks", "inspect current", "before redesign", "Electron app", "native app".
    724 repo stars
  41. ▌
    Flow Next Prime 3 · gmickel bundle
    Comprehensive codebase assessment for agent and production readiness. Classifies the project (lifecycle, topology, size, stack, shape), scans 8 pillars, verifies commands actually run, checks GitHub settings. Leads with a verdict + ranked next-actions; fixes agent readiness only. Triggers on /flow-next:prime.
    724 repo stars
  42. ▌
    Flow Next Setup 2 · gmickel bundle
    Optional local install of flowctl CLI and CLAUDE.md/AGENTS.md instructions, plus a commented model-routing example proposed into the project instruction file. Use when user runs /flow-next:setup.
    724 repo stars
  43. ▌
    Flow Next Visual 3 · gmickel
    Restate a spec, a task, a diff, or the current topic visually as a compact markdown digest. Use when asked to 'show me', 'explain this visually', 'restate that', 'digest the plan', 'walk me through the spec', 'walk me through the tasks', 'walk me through the diff', or when the output is too much text and a shape would land faster. Triggers on /flow-next:visual with an optional spec id, task id, git range, or free-form topic.
    724 repo stars
  44. ▌
    Flow Next Capture 5 · gmickel bundle
    Synthesize the current conversation context into a flow-next spec at `.flow/specs/<spec-id>.md` via `flowctl spec create --plan-file` — agent-native, source-tagged, with a saved-spec summary and editor follow-up. Triggers on /flow-next:capture, "capture spec", "lock down what we discussed", "make a spec from this conversation", "convert conversation to spec". Optional `mode:autofix` token runs without questions and requires `--yes` to write. Optional `--rewrite <spec-id>` overwrites an existing spec; `--from-compacted-ok` overrides the incomplete-evidence refusal after compaction; `--override-strategy` proceeds despite a contradiction with an active STRATEGY.md track (and prompts to record the override as a decision); `--no-plan` sets the spec-level `no_plan` field after the write (explicit opt-in on a user invocation, never inferred there); `from:flow` marks a run dispatched by `/flow-next:flow`, where capture applies the shared plan-versus-no-plan rule and sets the field itself when the rule resolves to dir
    724 repo stars
  45. ▌
    Flow Next Make Pr 5 · gmickel bundle
    Render a briefing from the aid artifact and open or update a PR via gh, a GitLab merge request via glab, or a Bitbucket Cloud pull request via bkt. Auto-detects the spec from the branch. Supports --draft, --ready, --base, --memory, --dry-run, --update, and mode:autonomous.
    724 repo stars
  46. ▌
    Flow Next Features · gmickel bundle
    Seed or maintain the committed user-POV feature map at `.flow/features/` so QA and drive reuse how a user reaches each feature. Two state-resolved modes: no `.flow/features/` (or explicit init intent) seeds it; a present map maintains it. Triggers on /flow-next:features, "seed the feature map", "maintain the feature map", "feature map", "init features". Never dispatched by `flow --auto`, land, or any autonomous driver.
    724 repo stars
  47. ▌
    Flow Next Strategy · gmickel bundle
    Create or maintain `STRATEGY.md` — the product's target problem, our approach, who it's for, key metrics, and tracks of work. Use when starting a new product, updating direction, or when prompts like 'write our strategy', 'update the roadmap', 'what are we working on', or 'set up the strategy doc' come up. Also fires when `/flow-next:prospect`, `/flow-next:plan`, `/flow-next:refine`, or `/flow-next:capture` need upstream grounding and no strategy doc exists yet.
    724 repo stars
  48. ▌
    Flow Next Resolve Pr · gmickel bundle
    Resolve PR review feedback — fetch unresolved threads, triage, dispatch per-thread resolver agents, validate, commit, reply + resolve via GraphQL. Triggers on /flow-next:resolve-pr.
    724 repo stars
  49. ▌
    Flow Next Impl Review · gmickel bundle
    John Carmack-level implementation review via Codex, Copilot, Cursor, Claude or a host reviewer. Use when reviewing code changes, PRs, or implementations. Triggers on /flow-next:impl-review.
    724 repo stars
  50. ▌
    Flow Next Plan Review · gmickel bundle
    Carmack-level plan review via Codex, Copilot, Cursor, Claude or a host reviewer. Use when reviewing Flow specs or design docs. Triggers on /flow-next:plan-review.
    724 repo stars
  51. ▌
    Flow Next Tracker Sync · gmickel bundle
    Project a flow-next spec to Linear, GitHub, GitLab, or Jira and reconcile body, status, and comments. Use for tracker discovery, linking, create-first, push, pull, reconcile, comment, or unlink. Not /flow-next:sync, which is plan-sync.
    724 repo stars
  52. ▌
    Flow Next Worktree Kit · gmickel bundle
    Manage git worktrees (create/list/switch/cleanup) and copy .env files. Use for parallel feature work, isolated review, clean workspace, or when user mentions worktrees.
    724 repo stars
  53. ▌
    Flow Next Memory Migrate · gmickel bundle
    Migrate legacy flat memory files (`.flow/memory/pitfalls.md`, `conventions.md`, `decisions.md`) into the categorized YAML schema. Triggers on /flow-next:memory-migrate, "migrate memory", "convert legacy memory", "lift pitfalls into categorized schema", "convert old memory format". Optional `mode:autofix` token in arguments runs without questions and accepts mechanical defaults for ambiguous classifications. Optional scope hint after the mode token narrows the migration to a specific legacy file (e.g. `pitfalls.md`).
    724 repo stars
  54. ▌
    Flow Next Spec Completion Review · gmickel bundle
    Spec completion review - verifies all spec tasks implement the spec requirements. Triggers on /flow-next:spec-completion-review.
    724 repo stars
  55. ▌
    Flow Next 3 · gmickel bundle
    Manage .flow/ tasks and specs. Triggers: 'show me my tasks', 'list specs', 'what tasks are there', 'add a task', 'create task', 'what's ready', 'task status', 'show fn-1-add-oauth'. NOT for /flow-next:plan or /flow-next:work.
    724 repo stars
  56. ▌
    Flow Next QA 3 · gmickel bundle
    Live-app real-user QA pass derived from the spec. Drives the running app via flow-next-drive, derives scenarios from the spec's AC / R-IDs / boundaries, files structured P0/P1/P2 findings with evidence, and ends with a YES/NO ship verdict receipt. Consumes `.flow/features/` navigation when present. Triggers on /flow-next:qa with a spec id. Runs user-invoked OR as the optional `pipeline.qa` stage of `flow --auto` (default off). Augments — never replaces — CI/staging/manual QA. FORBIDDEN from marking PASS by reading source — the verdict rests on captured evidence from the live app, never on agent narration.
    724 repo stars
  57. ▌
    Flow Next Map 3 · gmickel bundle
    Wrap `clawpatch map` to produce a semantic feature index of the repo (~20 languages, persisted at `.clawpatch/features/*.json`). Detects install, runs `clawpatch init` when `.clawpatch/` absent, invokes provider-free `clawpatch map --source heuristic` by default; `--source auto|agent` flows through as passthrough. Opt-in enrichment — scouts and prime read the resulting index, but flowctl never depends on clawpatch.
    724 repo stars
  58. ▌
    Flow Next Deps 3 · gmickel
    Show spec dependency graph and execution order. Use when asking 'what's blocking what', 'execution order', 'dependency graph', 'what order should specs run', 'critical path', 'which specs can run in parallel'.
    724 repo stars
  59. ▌
    Flow Next Land 3 · gmickel bundle
    Resolve feedback and CI for one named pull request, then squash merge when currently authorized and ready. Emits LAND_VERDICT. Use when asked to land a pull request.
    724 repo stars
  60. ▌
    Flow Next Plan 5 · gmickel bundle
    Break a spec or idea into reviewed tasks. Run only when the person asks for a plan or task breakdown, by /flow-next:plan, or when flow-next-flow routes here; any other request to design, build or implement a spec or idea goes to flow-next-flow. Triggers on /flow-next:plan with text descriptions or Flow IDs (fn-1-add-oauth, fn-1-add-oauth.2, or legacy fn-1, fn-1.2, fn-1-xxx, fn-1-xxx.2).
    724 repo stars
  61. ▌
    Flow Next · gmickel bundle
    Manage .flow/ tasks and specs. Triggers: 'show me my tasks', 'list specs', 'what tasks are there', 'add a task', 'create task', 'what's ready', 'task status', 'show fn-1-add-oauth'. NOT for /flow-next:plan or /flow-next:work.
    724 repo stars
  62. ▌
    Flow Next QA · gmickel bundle
    Live-app real-user QA pass derived from the spec. Drives the running app via flow-next-drive, derives scenarios from the spec's AC / R-IDs / boundaries, files structured P0/P1/P2 findings with evidence, and ends with a YES/NO ship verdict receipt. Consumes `.flow/features/` navigation when present. Triggers on /flow-next:qa with a spec id. Runs user-invoked OR as the optional `pipeline.qa` stage of `flow --auto` (default off). Augments — never replaces — CI/staging/manual QA. FORBIDDEN from marking PASS by reading source — the verdict rests on captured evidence from the live app, never on agent narration.
    724 repo stars
  63. ▌
    Flow Next Map · gmickel bundle
    Wrap `clawpatch map` to produce a semantic feature index of the repo (~20 languages, persisted at `.clawpatch/features/*.json`). Detects install, runs `clawpatch init` when `.clawpatch/` absent, invokes provider-free `clawpatch map --source heuristic` by default; `--source auto|agent` flows through as passthrough. Opt-in enrichment — scouts and prime read the resulting index, but flowctl never depends on clawpatch.
    724 repo stars
  64. ▌
    Flow Next Deps · gmickel
    Show spec dependency graph and execution order. Use when asking 'what's blocking what', 'execution order', 'dependency graph', 'what order should specs run', 'critical path', 'which specs can run in parallel'.
    724 repo stars
  65. ▌
    Flow Next Land · gmickel bundle
    Resolve feedback and CI for one named pull request, then squash merge when currently authorized and ready. Emits LAND_VERDICT. Use when asked to land a pull request.
    724 repo stars
  66. ▌
    Flow Next Sync · gmickel
    Manually trigger plan-sync to update downstream task specs after implementation drift. Use when code changes outpace specs.
    724 repo stars
  67. ▌
    Flow Next Work · gmickel bundle
    Execute a Flow spec or task systematically with git setup, task tracking, quality checks, and commit workflow. Run only by /flow-next:work or when flow-next-flow routes a spec here; any other request to implement, build or work on a spec, Flow-Next named or not, goes to flow-next-flow. Triggers on /flow-next:work with Flow IDs (fn-1-add-oauth, fn-1-add-oauth.2, or legacy fn-1, fn-1.2, fn-1-xxx, fn-1-xxx.2).
    724 repo stars
  68. ▌
    Flow Next Chart · gmickel bundle
    Decision-map discovery for one oversized/unclear idea before capture. Triggers on /flow-next:chart with an unshaped idea, chart id, decision pin, --status, or stored tracker URL. Prompt-first adaptive loop - ground, chart a frontier, resolve one D-ID per invocation, brief for capture.
    724 repo stars
  69. ▌
    Flow Next Drive · gmickel bundle
    Drive any UI surface like a real user - a web app, a Chromium-backed desktop app (Electron / WebView2, reached over CDP), or a genuinely native app (macOS AppKit/SwiftUI, or a non-CDP webview) reached via the Cua Driver / Computer Use. Detects the surface, picks the best available driver, degrades gracefully. Use to navigate sites, verify deployed UI, test web or desktop apps, capture baseline screenshots, drive a sign-in flow, scrape data, fill forms, run an e2e check, or inspect current page state. Triggers on "check the page", "verify UI", "test the site", "test this app", "drive the app", "automate this desktop app", "read docs at", "look up API", "visit URL", "browse", "screenshot", "scrape", "e2e test", "login flow", "capture baseline", "see how it looks", "inspect current", "before redesign", "Electron app", "native app".
    724 repo stars
  70. ▌
    Flow Next Prime · gmickel bundle
    Comprehensive codebase assessment for agent and production readiness. Classifies the project (lifecycle, topology, size, stack, shape), scans 8 pillars, verifies commands actually run, checks GitHub settings. Leads with a verdict + ranked next-actions; fixes agent readiness only. Triggers on /flow-next:prime.
    724 repo stars
  71. ▌
    Flow Next Setup · gmickel bundle
    Optional local install of flowctl CLI and CLAUDE.md/AGENTS.md instructions, plus a commented model-routing example proposed into the project instruction file. Use when user runs /flow-next:setup.
    724 repo stars
  72. ▌
    Flow Next Visual · gmickel
    Restate a spec, a task, a diff, or the current topic visually as a compact markdown digest. Use when asked to 'show me', 'explain this visually', 'restate that', 'digest the plan', 'walk me through the spec', 'walk me through the tasks', 'walk me through the diff', or when the output is too much text and a shape would land faster. Triggers on /flow-next:visual with an optional spec id, task id, git range, or free-form topic.
    724 repo stars
  73. ▌
    Flow Next Refine 2 · gmickel bundle
    Resolve ambiguous requirements and finalize project specifications by interviewing the user to capture critical decisions that only they can make.
    724 repo stars
  74. ▌
    Flow Next Flow · gmickel bundle
    Use first in a project that uses Flow-Next for any request to implement, build, continue or deliver its specs, whatever delivery or test steps the request adds, unless the user names another skill or asks to work directly. Also for a spec or task id, an idea or change request, a pasted bug report or traceback, a captured profile, trace or crash dump to explain, a mistake agents keep repeating, a prompt or skill change whose effect should be measured, "what could this break" or "is this safe to merge" about a diff, something slow to speed up or another number to move (hill-climbing), a behaviour-preserving cleanup, a design or behaviour choice to settle, an outcome to reach over several specs (a port, a migration, a PRD), a tracker issue, a branch, or "what should I do next". Only a quick question or a one-line edit may skip it. Flow routes the work and runs the right stage; --auto runs unattended.
    724 repo stars
  75. ▌
    Flow Next Refine · gmickel bundle
    Refine a spec, task, or spec file before building - one question pass for the decisions that would change what gets built, optionally focused by a free-text --scope lens (business, technical, qa, ...), or a read-only research pass (--scope=research) that resolves library versions, changed APIs, and gotchas from external docs into the spec. Use when a named product, authority, or costly-to-reverse technical decision is open, or when the spec names a library or API the repo does not already use. Triggers on /flow-next:refine with Flow IDs (fn-1-add-oauth, fn-1-add-oauth.2, or legacy fn-1, fn-1.2, fn-1-xxx, fn-1-xxx.2) or file paths.
    724 repo stars
  76. ▌
    Flow Next Flow 2 · gmickel bundle
    Use first in a Flow-Next repo for a spec id, change, bug, issue, slow code or metric, cleanup, design fork, dump to explain, repeated mistake, prompt change, what could break, what next. No quick asks
    724 repo stars
  77. ▌
    Flow Next Setup 4 · gmickel bundle
    Install or refresh flowctl and project instructions for flow-next in this repo. Use when asked to set up flow-next.
    724 repo stars
  78. ▌
    Flow Next Setup 3 · gmickel bundle
    Install or refresh flowctl and project instructions for flow-next in this repo. Use when asked to set up flow-next.
    724 repo stars
  79. ▌
    Gno 3 · gmickel bundle
    Search local documents, files, notes, and knowledge bases. Index directories, search with BM25/vector/hybrid, get AI answers with citations. Use when user wants to search files, find documents, query notes, look up information in local folders, index a directory, set up document search, build a knowledge base, needs RAG/semantic search, or wants to start a local web UI for their docs.
    724 repo stars
  80. ▌
    Flow Next Interview 6 · gmickel bundle
    In-depth Q&A to refine a spec, task, or spec file before building. Use when asked to flesh out, refine, or interrogate requirements.
    724 repo stars
  81. ▌
    Flow Next Ralph Init 4 · gmickel bundle
    Scaffold the repo-local Ralph autonomous harness and project hooks. Use when asked to set up Ralph.
    724 repo stars
  82. ▌
    Flow Next Export Context 4 · gmickel bundle
    Export RepoPrompt context to a markdown file for review with an external LLM (ChatGPT, Claude web, etc.). Use when you want Carmack-level review but prefer an external model. Triggers on "export context", "export for external review", "export plan for ChatGPT", "export impl review context", "review with an external model", "export review context".
    724 repo stars
  83. ▌
    Flow Next Plan 4 · gmickel bundle
    Create structured build plans from feature requests or Flow IDs. Use when planning features or designing implementation. Triggers on /flow-next:plan with text descriptions or Flow IDs (fn-1-add-oauth, fn-1-add-oauth.2, or legacy fn-1, fn-1.2, fn-1-xxx, fn-1-xxx.2).
    724 repo stars
  84. ▌
    Flow Next Audit 4 · gmickel bundle
    Audit `.flow/memory/` entries against the current codebase and decide Keep / Update / Consolidate / Replace / Delete per entry. Triggers on /flow-next:audit, "audit memory", "review memory", "refresh learnings", "sweep stale memory", "consolidate overlapping memory entries". Optional `mode:autofix` token in arguments runs without questions and marks ambiguous as stale. Optional scope hint after the mode token (concept, category, module, or path) narrows what gets audited.
    724 repo stars
  85. ▌
    Flow Next Capture 4 · gmickel bundle
    Synthesize the current conversation context into a flow-next spec at `.flow/specs/<spec-id>.md` via `flowctl spec create + spec set-plan` — agent-native, source-tagged, with mandatory read-back before write. Triggers on /flow-next:capture, "capture spec", "lock down what we discussed", "make a spec from this conversation", "convert conversation to spec". Optional `mode:autofix` token runs without questions and requires `--yes` to commit. Optional `--rewrite <spec-id>` overwrites an existing spec; `--from-compacted-ok` overrides the compaction-detection refusal; `--override-strategy` proceeds despite a contradiction with an active STRATEGY.md track (and prompts to record the override as a decision).
    724 repo stars
  86. ▌
    Flow Next Make Pr 4 · gmickel bundle
    Render a cognitive-aid PR body from flow-next state and open via gh. Triggers on /flow-next:make-pr with optional spec id and flags (--draft, --ready, --no-mermaid, --base <ref>, --memory, --dry-run). Auto-detects spec from current branch when no id given. NOT Ralph-blocked — autonomous loops can surface a draft PR for human review.
    724 repo stars
  87. ▌
    Flow Next Prospect 4 · gmickel bundle
    Generate ranked candidate ideas grounded in the repo, upstream of /flow-next:plan. Triggers on /flow-next:prospect with an optional focus hint (concept, path, constraint, or volume).
    724 repo stars
  88. ▌
    Flow Next Interview 4 · gmickel bundle
    Interview user in-depth about a spec, task, or spec file to extract complete implementation details. Use when user wants to flesh out a spec, refine requirements, or clarify a feature before building. Triggers on /flow-next:interview with Flow IDs (fn-1-add-oauth, fn-1-add-oauth.2, or legacy fn-1, fn-1.2, fn-1-xxx, fn-1-xxx.2) or file paths.
    724 repo stars
  89. ▌
    Flow Next Guide 3 · gmickel
    Prompt-first router that recommends the smallest sufficient flow-next workflow. Use when unsure which command to run next, which pre-build stage applies, or whether to skip chart/interview/plan. Triggers on /flow-next:guide with a free-form situation description.
    724 repo stars
  90. ▌
    Flow Next Pilot 3 · gmickel bundle
    Single-tick autonomous build-loop conductor for host drivers (/loop, /goal). Each invocation advances exactly ONE ready spec by ONE pipeline stage (plan, plan-review, work, qa [opt-in, gated on pipeline.qa==on], make-pr; with pipeline.chainStages==on, make-pr chains after a fresh qa verdict in the same tick — the only admissible second dispatch) and ends with a terminal PILOT_VERDICT line for the driver to read. Triggers on /flow-next:pilot, optionally with --spec <id>, --dry-run, --review=<backend>, --research=<grep|rp>, --depth=<level>. Autonomous by design — never asks the user questions; reports NEEDS_HUMAN instead.
    724 repo stars
  91. ▌
    Flow Next Prose 3 · gmickel
    Use while drafting any substantial reply, report, review walkthrough, or summary for the user - read the artifact prose contract before writing, not after, and draft under its rules. Do not use for short conversational turns, tool-call narration, the visual digest, or output that lands in a file, PR, or tracker (those artifact surfaces carry their own pointers). Also invocable directly as /flow-next:prose [draft].
    724 repo stars
  92. ▌
    Flow Next Interview 5 · gmickel bundle
    Interview user in-depth about a spec, task, or spec file to extract complete implementation details. Use when user wants to flesh out a spec, refine requirements, or clarify a feature before building. Triggers on /flow-next:interview with Flow IDs (fn-1-add-oauth, fn-1-add-oauth.2, or legacy fn-1, fn-1.2, fn-1-xxx, fn-1-xxx.2) or file paths.
    724 repo stars
  93. ▌
    Flow Next Ralph Init 3 · gmickel bundle
    Scaffold repo-local Ralph autonomous harness under scripts/ralph/. Use when user runs /flow-next:ralph-init.
    724 repo stars
  94. ▌
    Flow Next Guide 4 · gmickel bundle
    Recommend the smallest sufficient flow-next workflow from the starting state. Stateless router. Use when unsure which command or stage applies next.
    724 repo stars
  95. ▌
    Flow Next Pilot 4 · gmickel bundle
    Single-tick autonomous build-loop conductor. One spec or the backlog, one stage per tick (pipeline.chainStages chains qa into make-pr), emits PILOT_VERDICT. Use when asked to pilot a spec or backlog.
    724 repo stars
  96. ▌
    Flow Next Prose 4 · gmickel bundle
    Use while drafting a substantial reply, report, or summary for the user - read the prose contract before writing and draft under its rules. Not for short turns or file/PR output.
    724 repo stars
  97. ▌
    Flow Next Export Context 3 · gmickel
    Export RepoPrompt context to a markdown file for review with an external LLM (ChatGPT, Claude web, etc.). Use when you want Carmack-level review but prefer an external model. Triggers on "export context", "export for external review", "export plan for ChatGPT", "export impl review context", "review with an external model", "export review context".
    724 repo stars
  98. ▌
    Gno 2 · gmickel bundle
    Search local documents, files, notes, and knowledge bases. Index directories, search with BM25/vector/hybrid, get AI answers with citations. Use when user wants to search files, find documents, query notes, look up information in local folders, index a directory, set up document search, build a knowledge base, needs RAG/semantic search, or wants to start a local web UI for their docs.
    724 repo stars
  99. ▌
    Flow Next Plan 2 · gmickel bundle
    Create structured build plans from feature requests or Flow IDs. Use when planning features or designing implementation. Triggers on /flow-next:plan with text descriptions or Flow IDs (fn-1-add-oauth, fn-1-add-oauth.2, or legacy fn-1, fn-1.2, fn-1-xxx, fn-1-xxx.2).
    724 repo stars
  100. ▌
    Flow Next 2 · gmickel bundle
    Manage .flow/ tasks and specs. Use for show or list tasks, task status, what is ready, show fn-N. NOT for planning or executing (use the plan and work skills).
    724 repo stars