gmickel/flow-work
plugins/flow/skills/flow-work/SKILL.md
Execute a plan file or Beads epic systematically with git setup, task tracking, quality checks, and commit workflow. Use when implementing a plan, working through a spec, following documented steps, or executing a Beads issue ID (e.g., bd-123, gno-45, app-12).
$ install --global
skillsauthnpx skillsauth add gmickel/gmickel-claude-marketplace flow-workInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 5, 2026, 1:25 PM4.4s2 files scanned
SKILL.md
- name:
- flow-work
- description:
- Execute a plan file or Beads epic systematically with git setup, task tracking, quality checks, and commit workflow. Use when implementing a plan, working through a spec, following documented steps, or executing a Beads issue ID (e.g., bd-123, gno-45, app-12).
Flow work
Execute a plan systematically. Focus on finishing.
Role: execution lead, plan fidelity first. Goal: complete every plan step in order with tests.
Input
Full request: #$ARGUMENTS
Accepts:
- Plan file:
plans/<slug>.md - Beads ID(s) or title(s) directly
- Chained instructions like "then review with /flow:impl-review"
Examples:
/flow:work plans/oauth.md/flow:work gno-40i/flow:work gno-40i then review via /flow:impl-review and fix issues
If no plan/ID provided, ask for it.
FIRST: Setup Questions (REQUIRED)
Before doing anything else, output these questions as text (do NOT use AskUserQuestion tool):
Check if rp-cli available: which rp-cli >/dev/null 2>&1
If rp-cli available, ask both:
Quick setup before starting:
1. **Branch** — Where to work?
a) Current branch
b) New branch
c) Isolated worktree
2. **Review** — Run Carmack-level review after?
a) Yes, RepoPrompt chat
b) Yes, export for external LLM (ChatGPT, Claude web)
c) No
(Reply: "1a 2a", "current branch, export review", or just tell me naturally)
If rp-cli NOT available, ask only branch:
Quick setup: Where to work?
a) Current branch b) New branch c) Isolated worktree
(Reply: "a", "current", or just tell me)
Wait for response. Parse naturally — user may reply terse or ramble via voice. Do NOT read files or write code until user responds.
Workflow
After setup questions answered, read phases.md and execute each phase in order. If user chose review:
- Option 2a: run
/flow:impl-reviewafter Phase 6, fix issues until it passes - Option 2b: run
/flow:impl-reviewwith export mode after Phase 6
Guardrails
- Don't start without asking branch question
- Don't start without plan
- Don't skip tests
- Don't leave tasks half-done
Related Skills
gmickel/flow-next-drive
development
VerifiedTrustedCommunity
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 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".
621SKILL.mdUpdated Jun 4, 2026
gmickel/flow-next-drive
development
VerifiedTrustedCommunity
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 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".
621SKILL.mdUpdated Jun 4, 2026
gmickel/flow-next-make-pr
data-ai
VerifiedTrustedCommunity
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.
621SKILL.mdUpdated May 8, 2026
gmickel/flow-next-make-pr
data-ai
VerifiedTrustedCommunity
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.
621SKILL.mdUpdated May 8, 2026