gmickel
- 164 skills
- 0 followers
- 724 repo stars
- yesterday last updated
- ▌ Flow Next Audit 2 · gmickel bundleAudit `.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.
- ▌ Flow Next Capture 2 · gmickel bundleSynthesize 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 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 — never inferred).
- ▌ Flow Next Make Pr 2 · gmickel bundleRender 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.
- ▌ Flow Next QA 2 · gmickel bundleLive-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 Prospect 2 · gmickel bundleGenerate 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).
- ▌ Flow Next Map 2 · gmickel bundleBuild a semantic feature index of the repo via clawpatch map (opt-in). Use when asked to map the repo.
- ▌ Flow Next Interview 2 · gmickel bundleInterview 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.
- ▌ Flow Next Deps 2 · gmickel bundleShow 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'.
- ▌ Flow Next Land 2 · gmickel bundleAutonomous PR babysitter tick. Fixes CI, resolves feedback, merges when converged, closes the spec, releases. Emits LAND_VERDICT. Use when asked to land PRs.
- ▌ Flow Next Plan 3 · gmickel bundlePlan 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 Sync 2 · gmickel bundleManually trigger plan-sync to update downstream task specs after implementation drift. Use when code changes outpace specs.
- ▌ Flow Next Work 2 · gmickel bundleExecute 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.
- ▌ Flow Next Audit 3 · gmickel bundleAudit .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 Chart 2 · gmickel bundleDecision-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.
- ▌ Flow Next Drive 2 · gmickel bundleDrive 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".
- ▌ Flow Next Guide 2 · gmickel bundleRecommend the smallest sufficient flow-next workflow from the starting state. Stateless router. Use when unsure which command or stage applies next.
- ▌ Flow Next Pilot 2 · gmickel bundleSingle-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.
- ▌ Flow Next Prime 2 · gmickel bundleAssess codebase agent and production readiness. Classifies the project, verifies commands run, leads with a verdict and ranked next actions.
- ▌ Flow Next Prose 2 · gmickel bundleUse 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.
- ▌ Flow Next Visual 2 · gmickel bundleRestate 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.
- ▌ Flow Next Capture 3 · gmickel bundleSynthesize the current conversation into a flow-next spec with read-back gating. Use when asked to capture this as a spec.
- ▌ Flow Next Make Pr 3 · gmickel bundleOpen 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 Features 2 · gmickel bundleSeed or maintain the committed user-POV drive map at .flow/features/ so QA and drive reuse how a user reaches each feature.
- ▌ Flow Next Prospect 3 · gmickel bundleGenerate ranked candidate ideas grounded in the repo. Use when asked what to build next.
- ▌ Flow Next Strategy 2 · gmickel bundleCreate or update repo-root STRATEGY.md (problem, approach, users, metrics, tracks). Use for strategy or roadmap doc requests.
- ▌ Flow Next Interview 3 · gmickel bundleIn-depth Q&A to refine a spec, task, or spec file before building. Use when asked to flesh out, refine, or interrogate requirements.
- ▌ Flow Next Ralph Init 2 · gmickel bundleScaffold the repo-local Ralph autonomous harness and project hooks. Use when asked to set up Ralph.
- ▌ Flow Next Resolve Pr 2 · gmickel bundleResolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.
- ▌ Flow Next Impl Review 2 · gmickel bundleCarmack-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 Plan Review 2 · gmickel bundleCarmack-level review of a flow-next spec or plan via the configured backend. Use when asked to review a plan or spec.
- ▌ Flow Next Tracker Sync 2 · gmickel bundleProject 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 Worktree Kit 2 · gmickel bundleManage git worktrees (create/list/switch/cleanup) and copy .env files. Use for parallel feature work, isolated review, clean workspace, or when user mentions worktrees.
- ▌ Flow Next Export Context 2 · gmickel bundleExport 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".
- ▌ Flow Next Memory Migrate 2 · gmickel bundleMigrate legacy flat .flow/memory files to the categorized YAML schema. One-time ceremony. Use when asked to migrate flow memory.
- ▌ Flow Next Spec Completion Review 2 · gmickel bundleVerify that a spec's completed tasks fully implement the spec requirements. Use at spec completion before close.
- ▌ Managing Google Sheets · gmickelRead, write, and update Google Sheets data via CLI. Use when the user asks to read spreadsheet data, update cells, append rows, or work with Google Sheets. Triggers on mentions of spreadsheets, sheets, Google Sheets, tabular data in the cloud, or specific sheet names like "Projects" or "Tasks".
- ▌ Obsidian Skill · gmickel bundleUse Obsidian's official CLI to work with a running Obsidian app and its configured vaults. Use for live workspace state, indexed search and metadata, daily notes, tasks, links and backlinks, Bases, templates, bookmarks, plugins, themes, Sync status, and developer inspection. Prefer ordinary filesystem tools when the task only needs direct file reads, writes, listing, or text search.
- ▌ Gno · gmickel bundleSearch 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.
- ▌ Dogfood · gmickel bundleSystematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
- ▌ Browser · gmickel bundleBrowser automation via agent-browser CLI. Use when you need to navigate websites, verify deployed UI, test web apps, read online documentation, scrape data, fill forms, capture baseline screenshots before design work, or inspect current page state. Triggers on "check the page", "verify UI", "test the site", "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".
- ▌ Flow Next Opencode · gmickelManage .flow/ tasks and epics. Triggers: 'show me my tasks', 'list epics', 'what tasks are there', 'add a task', 'create task', 'what's ready', 'task status', 'show fn-1'. NOT for /flow-next:plan or /flow-next:work.
- ▌ Flow Next Opencode Plan · gmickel bundleCreate 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, fn-1.2).
- ▌ Flow Next Opencode Sync · gmickelManually trigger plan-sync to update downstream task specs after implementation drift. Use when code changes outpace specs.
- ▌ Flow Next Opencode Work · gmickel bundleExecute a Flow epic or task systematically with git setup, task tracking, quality checks, and commit workflow. Use when implementing a plan or working through a spec. Triggers on /flow-next:work with Flow IDs (fn-1, fn-1.2).
- ▌ Flow Next Opencode Prime · gmickel bundleComprehensive codebase assessment for agent and production readiness. Scans 8 pillars (48 criteria), verifies commands work, checks GitHub settings. Reports everything, fixes agent readiness only. Triggers on /flow-next:prime.
- ▌ Flow Next Opencode Setup · gmickel bundleLocal install of flowctl CLI and CLAUDE.md/AGENTS.md instructions. Use when user runs /flow-next:setup.
- ▌ Flow Next Opencode Interview · gmickel bundleInterview user in-depth about an epic, 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, fn-1.2) or file paths.
- ▌ Flow Next Opencode Ralph Init · gmickel bundleScaffold repo-local Ralph autonomous harness under scripts/ralph/. Use when user runs /flow-next:ralph-init.
- ▌ Flow Next Opencode Impl Review · gmickel bundleJohn Carmack-level implementation review via RepoPrompt or OpenCode. Use when reviewing code changes, PRs, or implementations. Triggers on /flow-next:impl-review.
- ▌ Flow Next Opencode Plan Review · gmickel bundleCarmack-level plan review via RepoPrompt or OpenCode. Use when reviewing Flow epic specs or design docs. Triggers on /flow-next:plan-review.
- ▌ Flow Next Opencode Rp Explorer · gmickel bundleToken-efficient codebase exploration using RepoPrompt CLI. Use when user says "use rp to..." or "use repoprompt to..." followed by explore, find, understand, search, or similar actions.
- ▌ Flow Next Opencode Worktree Kit · gmickel bundleManage git worktrees (create/list/switch/cleanup) and copy .env files. Use for parallel feature work, isolated review, clean workspace, or when user mentions worktrees.
- ▌ Flow Next Opencode Export Context · gmickelExport RepoPrompt context for external LLM review (ChatGPT, Claude web, etc.). Use when you want to review code or plans with an external model. Triggers on /flow-next:export-context.
- ▌ Flow Next Prose · gmickelUse 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].
- ▌ Flow Next Export Context · gmickelExport 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".
- ▌ Flow Next Guide · gmickelPrompt-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.
- ▌ Flow Next Pilot · gmickel bundleSingle-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.
- ▌ Flow Next Ralph Init · gmickel bundleScaffold repo-local Ralph autonomous harness under scripts/ralph/. Use when user runs /flow-next:ralph-init.
- ▌ Flow Next Plan · gmickel bundleCreate 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).
- ▌ Flow Next Audit · gmickel bundleAudit `.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.
- ▌ Flow Next Capture · gmickel bundleSynthesize 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).
- ▌ Flow Next Make Pr · gmickel bundleRender 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.
- ▌ Flow Next Prospect · gmickel bundleGenerate 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).
- ▌ Flow Next Interview · gmickel bundleInterview 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.