Coding Corgi Flow plugin
Coding Corgi Flow is an OpenSpec extension: issue tracking, per-group checks, review, QA and a change archive for AI agents.
- 102 ★ on the repository
- Last commit
Extended access
Why this level
- Hooks, commits and Issues automatically change the repository and the external tracker.
Install
- Works in
Manual install
npm install -g corgispecOpenSpec is required first (`npm install -g @fission-ai/openspec@^1.6.0`). Then `corgispec bootstrap`.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Hooks, commits and Issues automatically change the repository and the external tracker.
This is third-party code. Review the repository files before installing.
What it does
Coding Corgi Flow adds schemas, skills and the `corgispec` CLI on top of OpenSpec so an agent's work moves along a pipeline from proposal to archive. Each RFC slice gets a GitLab or GitHub Issue with a synced task dashboard, and execution proceeds in groups, with checks and a commit after each group. Then come automated verify gates (lint, build, tests, spec coverage), human review and QA against real user paths. Between sessions a shared memory promotes verified knowledge, and RFCs and deliveries run in isolated Git worktrees. The commands `/corgi:propose`, `/corgi:apply`, `/corgi:verify`, `/corgi:review` and `/corgi:archive` are available for OpenCode, Claude Code and Codex, with a plugin for Claude Code and Codex and lifecycle hooks.
Who it is for. Teams that develop with agents from specifications and want every task visible in a tracker with checks and review.
Good fit when
- A change should be split into task groups with a commit after each.
- The agent must not finish until lint, build and tests pass.
- A link between an RFC slice and a GitLab or GitHub Issue is needed.
- Knowledge from one session should land in shared project memory.
Not a fit when
- A lightweight flow for a single edit is wanted.
- The project does not use OpenSpec and will not adopt it.
- Automatically creating Issues and commits is not allowed.
Example request
Prepare a proposal for the task with `/corgi:propose`, open an Issue for each slice and show the group plan before execution starts.Limitations
Node.js 20.19 or newer, OpenSpec CLI 1.6.0 to below 2.0 (versions 1.3 to 1.5 are unsupported) and one agent are required; the tracker needs `gh` or `glab`. The repository states no license. Version 4 is still a release candidate (`corgispec@4.0.0-rc2`), so pin the version for reproducibility. `bootstrap` updates managed files and keeps backups if you edited them by hand, but hooks and commits change the repository, so review the plan before running.
How to disable. Delete the command and skill files that `corgispec bootstrap` created and remove the hooks from the agent settings. Remove the global package with `npm uninstall -g corgispec`.
FAQ
How do I install it?
Run `npm install -g corgispec` after installing OpenSpec with `npm install -g @fission-ai/openspec@^1.6.0`.
How do I prepare a project?
With `corgispec bootstrap --target /path/to/your-project --schema github-tracked`; the `--platform` and `--scope` flags are available.
Which agents are supported?
Claude Code, Codex and OpenCode in commands and hooks; Cursor and AmpCode are mentioned as possible agents.
Are GitLab or GitHub required?
Only when issue tracking is enabled: then `gh` or `glab` is needed.
What do the verify gates check?
Lint, build, tests and spec coverage; review is blocked on failure.
Discussion
No questions or reviews yet.
Related
PluginsSpec-driven development for coding agents: proposal, requirements, design and tasks come before any code
A CLI for spec-driven development: the agent carries a task through files in the repository from plan to verification and archive
A plugin that takes coding tasks from agreed scope to verified results and saves workflow state for later resumption.
A CLI that keeps the spec, tasks and proof of done in git so Claude, Codex, Grok and Cursor can hand work to each other
A workflow layer for a coding agent: from a task to a pull request with evidence, reviewed by a different model at every handover
A code-review CLI and plugin for agents: reads a git diff and writes line-level comments with context
Comparison with similar tools
Cards that share the main search query, and how they differ.
README in short
A community extension of OpenSpec: schemas, skills, a CLI and commands for three agents. The cycle ends with verification, human review and an archive.