By gitgitWi
Opinionated multi-step development workflow: prep → research → plan → plan-review → develop → deploy → code-review. Atomic commits, TDD-first, Multi-LLM review.
Run a multi-LLM code review on a pull request — gather the diff, dispatch reviewer CLIs in parallel via the file-write contract, synthesize a Korean summary, and post inline comments tagged by severity and model signature. Use this for any PR review whether the PR was just opened by flow:deploy or already exists on GitHub. Even when the user says "review PR
Push the task branch, open a Korean pull request, then hand off to flow:code-review for the multi-LLM review pipeline. Use this whenever development for a flow task is done and the branch is ready for review. Even when the user says "just open a PR", run the full flow — multi-LLM review is the point of this skill, not optional dressing. Run in its own session from develop; do not bundle.
Execute the implementation phase of the flow workflow — read `tasks.md`, pick the next unchecked behavior, write a failing test (when TDD applies), implement until green, commit atomically with conventional commits, and check the box. Use this for any actual code change in a flow task, whether or not a plan exists. Even when the user says "just implement this", invoke develop so the atomic-commit and TDD discipline applies. The skill resumes cleanly from interrupted sessions because `tasks.md` is the source of truth for progress.
Run the full flow workflow end-to-end — prep → optional research → plan (with optional multi-LLM brainstorming) → optional plan-review → develop → deploy — based on a single task goal from the user. Use this when the user wants to hand off a complete task and let the workflow run, rather than driving each step manually. Skips research, brainstorming, and plan-review automatically for size S tasks; runs the full pipeline for size L. Even when the user just says "build me X", consider this skill if the task warrants the full discipline.
Run a multi-LLM review on `plan.md` and `tasks.md` before implementation starts, capturing each reviewer's output as a file and synthesizing a Korean summary the user reads. Use this whenever a plan is non-trivial (size M with external dependencies, or any size L). Different models catch different gaps; the cost of an extra reviewer pass is tiny compared to discovering a missing requirement halfway through develop. Also use whenever the user asks for a "second opinion" on a plan or wants to validate an approach before committing to it.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
An opinionated multi-step development workflow for Claude Code — a small "council" of LLMs (Claude as orchestrator + Gemini + OpenCode/Kimi + OpenCode/DeepSeek) plans, reviews, and ships your changes together.
prep → (research) → plan → (plan-review) → develop → deploy
Atomic commits. TDD-first. .planning/<date>-<task>/ as the working memory. Multi-LLM review (Gemini, OpenCode/Kimi, OpenCode/DeepSeek) at plan time and review time.
| Skill | What it does |
|---|---|
flow:prep | Create worktree, branch, .planning/<date>-<task>/ folder, size estimate |
flow:research | Optional pre-plan investigation, writes research.md |
flow:plan | One-pager plan.md + GWT tasks.md |
flow:plan-review | Multi-LLM critique of the plan, Korean summary, version bump on changes |
flow:develop | TDD cycle per tasks.md checkbox, atomic conventional commits |
flow:deploy | Push, Korean PR, multi-LLM code review, inline comments with model signatures |
flow:orchestrate | Run the whole sequence end-to-end with size-based skip logic |
.planning/<yyyy-mm-dd>-<kebab-task>/ (committed by default)<type>/<task-name> where type ∈ feature|fix|chore|refactor|docsClaude Code:
/plugin marketplace add gitgitWi/council-flow
/plugin install flow@council-flow
Codex CLI:
codex plugin marketplace add gitgitWi/council-flow
GitHub shorthand resolves to this repo. Equivalent full forms also work:
# Claude Code
/plugin marketplace add https://github.com/gitgitWi/council-flow.git # HTTPS
/plugin marketplace add [email protected]:gitgitWi/council-flow.git # SSH (private/auth)
# Codex CLI
codex plugin marketplace add https://github.com/gitgitWi/council-flow.git # HTTPS
codex plugin marketplace add [email protected]:gitgitWi/council-flow.git # SSH (private/auth)
git clone https://github.com/gitgitWi/council-flow.git ~/Codes/council-flow
# Claude Code
/plugin marketplace add ~/Codes/council-flow
/plugin install flow@council-flow
# Codex CLI
codex plugin marketplace add ~/Codes/council-flow
The marketplace name council-flow comes from .claude-plugin/marketplace.json and is the same regardless of install source.
See the Claude Code docs for the full /plugin marketplace add reference: https://code.claude.com/docs/en/discover-plugins.md
See the Codex CLI help for plugin marketplace options:
codex plugin marketplace add --help
Shared reference docs live at the plugin root and are linked from each SKILL.md:
references/models.md — model registry (swap IDs here, not in skills)references/multi-llm.md — how to call other coding agentsreferences/directory-structure.md — .planning/ layoutreferences/commit-conventions.md — atomic + conventional commitsreferences/tdd-policy.md — when TDD applies, when it doesn'treferences/inline-review-posting.md — gh API mechanics for inline PR commentsscripts/prep.sh — worktree + branch + .planning/ scaffolding (idempotent)Inspired by claude-octopus — many of the design decisions here (multi-LLM orchestration, phase-based workflow, skill-per-step structure, plan/review separation) draw directly from patterns nyldn established there. council-flow is a smaller, opinionated subset focused on a single bilingual TDD-first development loop, but the foundations are theirs.
The planning and research skills also borrow from Superpowers and gstack: Superpowers' emphasis on design-before-implementation, explicit alternatives, and self-review; and gstack's stronger problem framing, premise challenge, existing-code leverage, and plan-review rigor.
MIT
npx claudepluginhub gitgitwi/council-flow --plugin flowComprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Design fluency for frontend development. 1 skill with 23 commands (/impeccable polish, /impeccable audit, /impeccable critique, etc.) and curated anti-pattern detection.
UI/UX design intelligence. 67 styles, 161 palettes, 57 font pairings, 25 charts, 15 stacks (React, Next.js, Vue, Svelte, Astro, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, Nuxt, Jetpack Compose). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.