All authors
Claude Skills by gmickel
github.com/gmickel70 skills235 installs2,509 views
- Flow Next Make PrOpen 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.Votes: 0GitHub stars: 706
- Flow Next Worktree KitManage git worktrees (create/list/switch/cleanup) and copy .env files. Use for parallel feature work, isolated review, clean workspace, or when user mentions worktrees.Votes: 0GitHub stars: 706
- Flow Next FlowConductor for an idea, spec or task id, tracker issue, branch, bug report, or question; --auto runs a ready spec unattended and emits PILOT_VERDICT. Use when no skill is named or to pilot a spec.Votes: 0GitHub stars: 706
- Specs> user (turn — 3-part decomposition): "so this would be a 3 parter perhaps, 1. wrap clawpatch map including the install etc. in a new flow-next:map skill 2. scouts can use the map as additional help for context gathering? agents.md/claude.md perhaps too a short mention of the map 3. prime could suggest using it if a similar map doesn't exist?"Votes: 0GitHub stars: 705
- Flow Next AuditAudit .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.Votes: 0GitHub stars: 705
- Flow Next CaptureSave the current conversation as a source-tagged flow-next spec, then offer review or editing. Use when asked to capture this as a spec.Votes: 0GitHub stars: 705
- Flow Next MapBuild a semantic feature index of the repo via clawpatch map (opt-in). Use when asked to map the repo.Votes: 0GitHub stars: 705
- Flow Next Memory MigrateMigrate legacy flat .flow/memory files to the categorized YAML schema. One-time ceremony. Use when asked to migrate flow memory.Votes: 0GitHub stars: 705
- Flow Next ProspectGenerate ranked candidate ideas grounded in the repo. Use when asked what to build next.Votes: 0GitHub stars: 705
- Flow Next Resolve PrResolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.Votes: 0GitHub stars: 705
- Flow Next Spec Completion ReviewVerify that a spec's completed tasks fully implement the spec requirements. Use at spec completion before close.Votes: 0GitHub stars: 705
- Flow Next StrategyCreate or update repo-root STRATEGY.md (problem, approach, users, metrics, tracks). Use for strategy or roadmap doc requests.Votes: 0GitHub stars: 705
- Specsflow-next has two visual registers and nothing between them. At one extreme: raw spec/task markdown - after `/flow-next:plan` a reviewer faces the spec plus N task files (500+ lines for a 7-task spec) and must reconstruct the structure in their head by serial reading. At the other: the opt-in HTML render lenses (`artifacts.html.enabled`) - full instrument-panel documents with mastheads, dials, and DAG hover wires, heavyweight to generate and consume. The middle register is missing: a fast, compaVotes: 0GitHub stars: 705
- Flow Next ChartDecision-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.Votes: 0GitHub stars: 705
- Flow Next DepsShow 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'.Votes: 0GitHub stars: 705
- Flow Next DriveDrive 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 pag...Votes: 0GitHub stars: 705
- Flow Next FeaturesSeed or maintain the committed user-POV drive map at .flow/features/ so QA and drive reuse how a user reaches each feature.Votes: 0GitHub stars: 705
- Flow Next Impl ReviewCarmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.Votes: 0GitHub stars: 705
- Flow Next InterviewDeprecated alias for flow-next-refine, removed next release. Invoke /flow-next:refine.Votes: 0GitHub stars: 705
- Flow Next LandResolve 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.Votes: 0GitHub stars: 705
- Flow Next Plan ReviewCarmack-level review of a flow-next spec or plan via the configured backend. Use when asked to review a plan or spec.Votes: 0GitHub stars: 705
- Flow Next PlanPlan 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).Votes: 0GitHub stars: 705
- Flow Next PrimeAssess codebase agent and production readiness. Classifies the project, verifies commands run, leads with a verdict and ranked next actions.Votes: 0GitHub stars: 705
- Flow Next ProseUse 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.Votes: 0GitHub stars: 705
- Flow Next QaLive-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.Votes: 0GitHub stars: 705
- Flow Next SetupInstall or refresh flowctl and project instructions for flow-next in this repo. Use when asked to set up flow-next.Votes: 0GitHub stars: 705
- Flow Next SyncManually trigger plan-sync to update downstream task specs after implementation drift. Use when code changes outpace specs.Votes: 0GitHub stars: 705
- Flow Next Tracker SyncProject 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.Votes: 0GitHub stars: 705
- Flow Next VisualRestate 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.Votes: 0GitHub stars: 705
- Flow Next WorkExecute a flow-next spec or task end-to-end with worker subagents, gates, and commits. Use when asked to work on, implement, or execute fn-N.Votes: 0GitHub stars: 705
- Flow Next Worktree KitManage git worktrees (create/list/switch/cleanup) and copy .env files. Use for parallel feature work, isolated review, clean workspace, or when user mentions worktrees.Votes: 0GitHub stars: 705
- Flow NextManage .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).Votes: 0GitHub stars: 705
- Flow Next AuditAudit `.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 (...Votes: 0GitHub stars: 705
- Flow Next CaptureSynthesize 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 existi...Votes: 0GitHub stars: 705
- Flow Next ChartDecision-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.Votes: 0GitHub stars: 705
- Flow Next DriveDrive 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 pag...Votes: 0GitHub stars: 705
- Flow Next FeaturesSeed 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.Votes: 0GitHub stars: 705
- Flow Next LandResolve 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.Votes: 0GitHub stars: 705
- Flow Next Make PrRender 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.Votes: 0GitHub stars: 705
- Flow Next MapWrap `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.Votes: 0GitHub stars: 705
- Flow Next Memory MigrateMigrate 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 fi...Votes: 0GitHub stars: 705
- Flow Next PrimeComprehensive 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.Votes: 0GitHub stars: 705
- Flow Next ProseUse 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].Votes: 0GitHub stars: 705
- Flow Next ProspectGenerate 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).Votes: 0GitHub stars: 705
- Flow Next QaLive-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 m...Votes: 0GitHub stars: 705
- Flow Next Ralph InitScaffold repo-local Ralph autonomous harness under scripts/ralph/. Use when user runs /flow-next:ralph-init.Votes: 0GitHub stars: 705
- Flow Next Resolve PrResolve PR review feedback — fetch unresolved threads, triage, dispatch per-thread resolver agents, validate, commit, reply + resolve via GraphQL. Triggers on /flow-next:resolve-pr.Votes: 0GitHub stars: 705
- Flow Next SetupOptional 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.Votes: 0GitHub stars: 705
- Flow Next Spec Completion ReviewSpec completion review - verifies all spec tasks implement the spec requirements. Triggers on /flow-next:spec-completion-review.Votes: 0GitHub stars: 705
- Flow Next StrategyCreate 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.Votes: 0GitHub stars: 705