Audit `.flow/memory/` entries against the current codebase and decide Keep / Update / Consolidate / Replace / Delete per entry.
Synthesize the current conversation context into a flow-next epic spec at `.flow/specs/.md` via `flowctl epic create + epic set-plan` — agent-native, source-tagged, with…
Show epic dependency graph and execution order. Use when asking 'what's blocking what', 'execution order', 'dependency graph', 'what order should epics run', 'critical path',…
Epic completion review - verifies all epic tasks implement spec requirements. Triggers on /flow-next:epic-review.
Export RepoPrompt context for external LLM review (ChatGPT, Claude web, etc.). Use when you want to review code or plans with an external model.
John Carmack-level implementation review via RepoPrompt or Codex. Use when reviewing code changes, PRs, or implementations. Triggers on /flow-next:impl-review.
Interview user in-depth about an epic, task, or spec file to extract complete implementation details.
Migrate pre-fn-30 legacy flat memory files (`.flow/memory/pitfalls.md`, `conventions.md`, `decisions.md`) into the categorized YAML schema.
Create structured build plans from feature requests or Flow IDs. Use when planning features or designing implementation.
Carmack-level plan review via RepoPrompt or Codex. Use when reviewing Flow epic specs or design docs. Triggers on /flow-next:plan-review.
Comprehensive codebase assessment for agent and production readiness. Scans 8 pillars (48 criteria), verifies commands work, checks GitHub settings.
Scaffold repo-local Ralph autonomous harness under scripts/ralph/. Use when user runs /flow-next:ralph-init.
Token-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…
Optional local install of flowctl CLI and CLAUDE.md/AGENTS.md instructions. Use when user runs /flow-next:setup.
Spec completion review - verifies all spec tasks implement the spec requirements. Triggers on /flow-next:spec-completion-review.
Manually trigger plan-sync to update downstream task specs after implementation drift. Use when code changes outpace specs.
Project a flow-next spec to a tracker issue (Linear first, GitHub next) and reconcile body/status/comments two-way — projection, not coordination.
Execute 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.
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.
Flow Orchestration admin: stage configuration, step assignment, background steps, interactive steps, evaluation flows, work items, pause/resume.
Flow Orchestration design patterns — multi-stage, multi-step flows where each step is itself an autolaunched flow or a screen flow assigned to a user / queue, with Work Items…
Tune Flow runtime performance: pick Before-Save over After-Save, consolidate Get Records, eliminate loop-DML, cache lookups, split with Scheduled Paths, and measure actual…
Create structured build plans from feature requests, bug reports, or Beads issue IDs. Use when planning features, designing implementation, preparing work breakdown, or when given…
Plan phases, tasks, and iterations. Use when structuring new work, adding features, or organizing development plans.
Build reactive Flow screens where one component updates another without navigation using reactive formulas and component outputs. NOT for Aura-based screens.
Handle code review feedback with technical rigor. Don't blindly agree - verify before implementing.
Diagnose and prevent UNABLE_TO_LOCK_ROW + parent-record contention in record-triggered, scheduled, and screen flows by mapping the implicit lock chain and applying decouple…
Reason about how record-triggered flows interleave with the Salesforce Save Order (validation, before-save flows, before triggers, duplicate rules, after-save flows, workflow,…
Orchestrate living requirements refinement, change control, impact analysis, and traceability maintenance throughout SDLC
Flow resource types and when to use each: Variables, Collection Variables, Constants, Formulas, Text Templates, Choices, Stages, Picklist Choice Sets, Record Choice Sets.
Resume interrupted flow:work session from last checkpoint. Reads flow-progress.txt to restore context and continue work.
Orchestrate systematic retrospective cycle with structured feedback collection, improvement tracking, and action item management
Orchestrate continuous risk identification, assessment, tracking, and retirement across SDLC phases
Chat / code generation via flow_router using OpenAI /v1/chat/completions or Anthropic /v1/messages or Gemini /v1beta/models/...:generateContent with streaming + auto-fallback…
Image generation via flow_router OpenAI-shape /v1/images endpoint. Routes to active media providers (OpenAI, Stability, BFL, Gemini, etc.).
Text-to-speech via flow_router. OpenAI /v1/audio/speech shape, routes to active TTS providers (OpenAI, ElevenLabs, Gemini TTS, Edge TTS, etc.).
Design input validation inside Screen Flow screens using component-level (formula + errorMessage), isRequired, cross-field rules on the second field, reactive…
Presents 2+ candidate flows from flow-detector and asks the user to pick one. Issues exactly one AskUserQuestion.
When the user wants to solve Flow Shop Scheduling Problems (FSP), optimize production on assembly lines, or minimize makespan with linear routing.
Menyelesaikan issue GitHub atau task Jira end-to-end dari branching sampai PR dan status update. Gunakan saat user meminta eksekusi task implementasi lengkap berbasis tiket.
Enforces TDD Iron Law in flow-dev. NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST.
Orchestrate Team Onboarding flow with pre-boarding, training, buddy assignment, and 30/60/90 day check-ins
Time-based execution in Salesforce Flow — Scheduled Paths in record-triggered flows (delays measured against a record date or trigger fire time), the Wait element in autolaunched…
Use when a Flow needs to do work that must survive the triggering transaction — post-commit notifications, callouts, audit rows, or compensating actions.
Reason about when a Flow is inside the caller's transaction vs starts its own. Pick Before-Save vs After-Save vs Async Path vs Pause + Resume when transaction boundaries matter.
Complete migration validation checklist for Flow to Output SDK. Use after migration to verify completeness and correctness.
Verify plan consistency, generate summaries, maintain plan health. Use for review, verification, summaries, or plan maintenance. Mostly read-only with maintenance operations.
יצירת תמונה או סרטון מלווה לתוכן דרך Google Flow — מצב תמונה (2 שלבים) או מצב סרטון (4 שלבים)
Execute a plan file or Beads epic systematically with git setup, task tracking, quality checks, and commit workflow.
Team-management dashboard skill in the FlowAI aesthetic — three tabs (Team Members, Team Details, Activity Log), KPI stat row, member table, role distribution bar chart, online…
Provides reference documentation and examples for all of the available Flowbite TailwindCSS HTML UI Components plus the related Typography and Forms plugins.
Create HTML flowcharts and process diagrams with decision trees, color-coded stages, arrows, and swimlanes.
Create and manage data pipelines using the FlowerPower framework with Hamilton DAGs and uv. Use when users request creating flowerpower projects, pipelines, Hamilton dataflows, or…
Automation discovery audit skill. Walks through a 5-question workflow intake, then audits Gmail/Calendar/Slack/task trackers to identify automation opportunities.
Parse FCS (Flow Cytometry Standard) files v2.0-3.1. Extract events as NumPy arrays, read metadata/channels, convert to CSV/DataFrame, for flow cytometry data preprocessin — from…
Parse FCS (Flow Cytometry Standard) files v2.0-3.1. Extract events as NumPy arrays, read metadata/channels, convert to CSV/DataFrame, for flow cytometry data preprocessin — from…
Parse/write FCS (Flow Cytometry) files v2.0-3.1. Events as NumPy, channel metadata, multi-dataset files, CSV/FCS export. Use FlowKit for gating/compensation.
Parse FCS (Flow Cytometry Standard) files v2.0-3.1. Extract events as NumPy arrays, read metadata/channels, convert to CSV/DataFrame, for flow cytometry data preprocessin — from…
FlowiseAI integration. Manage data, records, and automate workflows. Use when the user wants to interact with FlowiseAI data.
Automate Flowiseai tasks via Rube MCP (Composio). Always search tools first for current schemas. — from general/automation