Skip to main content
gmickel
GitHub creator profile

gmickel

Repository-level view of 99 collected skills across 10 GitHub repositories.

skills collected
99
repositories
10
updated
Sep 5, 2026
repository map

Where the skills live

Top repositories by collected skill count, with their share of this creator catalog and occupation spread.

Showing the top 8 repositories here; full repository list continues below.
repository explorer

Repositories and representative skills

Showing 8 of 72 collected skills.
flow-next-opencode-ralph-init
software-developers

Scaffold repo-local Ralph autonomous harness under scripts/ralph/. Use when user runs /flow-next:ralph-init.

Jan 23, 2026
flow-next-opencode-impl-review
software-quality-assurance-analysts-and-testers

John Carmack-level implementation review via RepoPrompt or OpenCode. Use when reviewing code changes, PRs, or implementations. Triggers on /flow-next:impl-review.

Jan 23, 2026
flow-next-opencode-plan-review
software-developers

Carmack-level plan review via RepoPrompt or OpenCode. Use when reviewing Flow epic specs or design docs. Triggers on /flow-next:plan-review.

Jan 23, 2026
flow-next-opencode-prime
software-developers

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

Jan 23, 2026
flow-next-opencode-setup
software-developers

Local install of flowctl CLI and CLAUDE.md/AGENTS.md instructions. Use when user runs /flow-next:setup.

Jan 21, 2026
flow-next-opencode-interview
computer-and-information-systems-managers-113021

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

Jan 21, 2026
flow-next-opencode-plan
general-and-operations-managers-111021

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, fn-1.2).

Jan 21, 2026
flow-next-opencode-sync
computer-systems-analysts

Manually trigger plan-sync to update downstream task specs after implementation drift. Use when code changes outpace specs.

Jan 21, 2026
Showing 8 of 14 collected skills.
Showing 10 of 10 repositories
All repositories loaded