gmickel/flow-next

flow-next-make-pr

Open a PR with a cognitive-aid body rendered from flow-next spec state via gh. Use whenever asked to make or open a PR in a flow-next repo.

원문 언어: 영어

flow-next-make-pr

Render a briefing from the aid artifact and open or update a PR via gh. Auto-detects the spec from the branch. Supports --draft, --ready, --base, --memory, --dry-run, --update, and mode:autonomous.

원문 언어: 영어

flow-next-audit

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.

원문 언어: 영어

flow-next-capture

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.

원문 언어: 영어

flow-next-features

Seed or maintain the committed user-POV drive map at .flow/features/ so QA and drive reuse how a user reaches each feature.

원문 언어: 영어

flow-next-memory-migrate

Migrate legacy flat .flow/memory files to the categorized YAML schema. One-time ceremony. Use when asked to migrate flow memory.

원문 언어: 영어

flow-next-audit

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…

원문 언어: 영어

flow-next-capture

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…

원문 언어: 영어

flow-next-features

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-memory-migrate

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",…

원문 언어: 영어

flow-next-spec-completion-review

Verify that a spec's completed tasks fully implement the spec requirements. Use at spec completion before close.

원문 언어: 영어

flow-next-work

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.

원문 언어: 영어

flow-next-spec-completion-review

Spec completion review - verifies all spec tasks implement the spec requirements. Triggers on /flow-next:spec-completion-review.

원문 언어: 영어

flow-next-work

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…

원문 언어: 영어

flow-next-qa

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.

원문 언어: 영어

flow-next-qa

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-next-flow

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

원문 언어: 영어

flow-next-flow

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…

원문 언어: 영어

flow-next-land

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.

원문 언어: 영어

flow-next-land

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.

원문 언어: 영어

flow-next-prime

Assess codebase agent and production readiness. Classifies the project, verifies commands run, leads with a verdict and ranked next actions.

원문 언어: 영어

flow-next-prime

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…

원문 언어: 영어

flow-next-setup

Install or refresh flowctl and project instructions for flow-next in this repo. Use when asked to set up flow-next.

원문 언어: 영어

flow-next-setup

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.

원문 언어: 영어

flow-next-resolve-pr

Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.

원문 언어: 영어

flow-next-resolve-pr

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.

원문 언어: 영어

flow-next-impl-review

Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.

원문 언어: 영어

flow-next-impl-review

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.

원문 언어: 영어

flow-next-prospect

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.

원문 언어: 영어

flow-next-refine

Refine a spec or task before building: one Q&A interview, optionally focused by a scope lens, or a read-only research pass over external docs. Use to refine requirements or read up on a new library.

원문 언어: 영어

flow-next-refine

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…

원문 언어: 영어

flow-next-plan

Plan a feature into a flow-next spec with tasks in .flow/. Use when asked to plan, spec out, or break down work (fn-N ids).

원문 언어: 영어

flow-next-plan

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,…

원문 언어: 영어

flow-next-plan-review

Carmack-level review of a flow-next spec or plan via the configured backend. Use when asked to review a plan or spec.

원문 언어: 영어

flow-next-plan-review

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.

원문 언어: 영어

flow-next-tracker-sync

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.

원문 언어: 영어

flow-next-tracker-sync

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.

원문 언어: 영어

flow-next

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).

원문 언어: 영어

flow-next

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.

원문 언어: 영어

flow-next-map

Build a semantic feature index of the repo via clawpatch map (opt-in). Use when asked to map the repo.

원문 언어: 영어