ginee


An AI software engineering team that behaves like a real one. Drops into your project, self-onboards, and gets to work.
You’re running AI coding agents across projects. Each tool has its own quirks, prompts,
agent files, slash commands. The team works differently in every repo. Phases get
skipped. Roles overlap. Long tasks crash with nothing to resume from. You re-explain
the same governance every single time.
ginee makes the team portable, the process deterministic, and your project the source of truth.
Drop the framework into a repo, prompt “Run initial discovery”, and you have a 7-role
engineering team that works the same way on Claude Code, Copilot CLI, Cursor, Codex,
Windsurf, and anything that reads AGENTS.md.
Why ginee?
📐 Process is the framework
The phased lifecycle, dispatch rules, and iteration protocol are the spine. Agents, the knowledge index, self-onboarding, the adapters — all optimisations on top. Strip them away and the process still holds; you could run it by hand.
👥 Works like a real team
Roles dispatch each other, hand off, and review each other's work. Strict-domain rule keeps each specialist in its lane; cross-domain bugs go through a propose → implement → verify cycle, not single-agent guessing.
🎯 Deterministic process
Same phased lifecycle (Phases 1–8), same dispatch rules, same gates — from one project to the next. No re-teaching what "Phase 3" means.
🤖 Client-agnostic
Claude Code (tier-1) · Copilot CLI (tier-1) · AGENTS.md (tier-2) · generic (tier-3). One set of role definitions; per-client renderings are pointer files only.
🔎 Self-learning
Zero stack/domain opinions baked in. team-lead learns your project on first run — tech stack, architecture, SDLC artefacts, TODO conventions, doc layout.
📊 Compliance at a glance
A single-line statusline on the Claude adapter surfaces compliance state in real time: current issue, trailer status, and cap-bytes headroom on the tightest hot-spec file. Class G — visible state, never blocking. Opt out per-tactic.
📥 Three task sources
Freeform requests, TODO files (root + nested per-component), and GitHub issues (file / pick up / triage / promote). TODOs flip ☐ → ☒ only on user approval; PRs auto-close issues via Closes #N.
📚 Reference, not copy
Project docs (architecture, mockups, diagrams) stay where they are. Doc changes propagate instantly — the framework never duplicates content.
🛡️ Compliance hooks
Cross-platform PreToolUse hooks on the Claude adapter block 5 charter-violating edit patterns at the tool-call layer (frontmatter omission, cap-bytes overrun, D-token reintroduction, RFC 2119 voluntarism, always-loaded bloat). Per-tactic opt-out via local/framework.config.yaml § compliance.disabled.
⏱️ Iteration protocol
Work > 15 min runs in 3–5 min stoppable batches with visible intermediate results. Interrupt anytime; resume next day with zero rework.
🚧 Shell-command guardrails
The Bash PreToolUse hook on Claude blocks 4 destructive shell patterns at the tool-call layer: --no-verify commits, force-pushes to trunk, hard resets, and PRs without a body. Per-tactic opt-out via local/framework.config.yaml § compliance.disabled.
🧱 Extensible
5 pre-built specialists (security · ml · mobile · sre · data). Plus author your own under local/roles/.
🔄 Update-safe
core/, adapters/, extras/ replaced on update. local/ (your bindings, custom roles) survives every upgrade.
🛡️ Compliance by construction
Per-cardinal tools: whitelists on the Claude adapter convert charter rules into hard gates — solution-architect cannot edit code; ai-engineer cannot run shells. Opt out per tactic via local/framework.config.yaml § compliance.disabled.
Quick start
1. Install into your project
cd /path/to/your-project
curl -fsSL https://raw.githubusercontent.com/kostiantyn-matsebora/ginee/main/install.sh | bash -s -- --adapter claude
cd C:\path\to\your-project
$env:GINEE_ADAPTER='claude'; iwr -useb https://raw.githubusercontent.com/kostiantyn-matsebora/ginee/main/install.ps1 | iex
Adapters: claude (Claude Code) · copilot-cli (GitHub Copilot CLI) · agents-md (Cursor / Codex / Windsurf / Gemini) · generic (fallback).
Default --ref is latest — downloads + SHA256-verifies the published release tarball; no git required. Pin with --ref v0.1.0, or track a branch / commit with --ref main / --ref <sha> (falls back to git clone).
2. Run discovery
Open your client in the project, then prompt:
/ginee-discovery # tier-1 slash command
Run initial discovery # natural-language equivalent
team-lead writes local/project-profile.md, local/bindings.md, local/framework.config.yaml, extracts a knowledge index under local/index/, scans external catalogs for specialist candidates, and reports recommended roles for your approval.
3. Give it work
Talk to ginee — the team self-dispatches per local/bindings.md. Two invocation paths:
- Freeform (any tier):
Use ginee to ....
- Skill (tier-1, Claude Code + Copilot CLI):
/ginee-<skill> [args]. Natural-language phrasings also match.
Three task sources:
# Freeform — any source, any tier
Use ginee to add a dark-mode toggle to the header
# TODO files — /ginee-pick-up on tier-1
Use ginee to pick up the next TODO # freeform
/ginee-pick-up # skill, next unchecked TODO
# GitHub issues — /ginee-* slash commands on tier-1
Use ginee to pick up issue #42 # freeform
/ginee-pick-up #42
/ginee-file-bug Safari 17 dashboard blank
/ginee-triage # ranked by D23 score = value / complexity
/ginee-address-review #42 # ingest review comments on an open PR (D24)
/ginee-iterate # relay review-cycle reply to warm cardinal — main thread = relay only
/ginee-update # refresh framework — preserves local/
Full 13-skill cheat sheet in adapters/claude/install.md. For long tasks, the iteration protocol kicks in automatically: 3–5 min batches with visible intermediate results and a stop-anywhere contract.
Full Getting Started guide →
The 7 cardinals
team-lead
solution-architect
ai-engineer
frontend-engineer
backend-engineer
devops-engineer
qa-engineer
| Role |
Owns |
Generic alias |
team-lead |
Dispatch routing, lifecycle gates, discovery, post-acceptance hook |
orchestrator, project-manager |
solution-architect |
Architecture doc semantics, SAD freeze + CR/ADR governance |
architect |
ai-engineer |
AI-asset + doc context economy, file-splitting, load topology |
context-engineer |
frontend-engineer |
Client / UI engineering |
client-engineer |
backend-engineer |
Server / API engineering |
service-engineer |
devops-engineer |
Infra, CI/CD, containers, cloud, secrets |
platform-engineer |
qa-engineer |
Functional / e2e / visual / scenario testing + thin runners |
quality-engineer |
Plus 5 opt-in specialists in extras/roles/ (security · ml · mobile · sre · data) and unlimited custom roles in local/roles/.
More on the 7-cardinal model →
Where to next
- Getting Started — install, discovery, first dispatch.
- Concepts — 7-cardinal model, lifecycle, dispatch rules, iteration protocol, index protocol, delivery modes.
- Reference — process spec, role kernels, index protocol — the canonical specs.
- Cheatsheet — one-page quick reference for daily use.
- Contributing — issue templates, PR conventions, how to add a role.
- Source repo —
core/, adapters/, extras/, install scripts.