Terminal tabs everywhere
Parallel agents generate momentum, but tracking what each one did and why becomes manual overhead.
Spec-driven development for AI teams
Aigon structures the full product lifecycle — research, feature delivery, and user feedback — as specs and logs committed directly to your repository. Every decision is traceable, every implementation is reviewable, and your project memory stays portable across tools.
The problem
Parallel agents generate momentum, but tracking what each one did and why becomes manual overhead.
Without spec-linked workflows, merge decisions and implementation tradeoffs disappear into chat history.
Teams rarely compare multiple implementations side-by-side before merging the best approach.
User feedback, research, and implementation often live in separate tools with no shared lifecycle.
Value proposition
Traceability
Research, feature specs, implementation logs, and evaluations stay in Markdown files your team can review and version.
docs/specs/features/03-in-progress/
docs/specs/features/logs/
Vendor independent
Run the same workflow with Claude, Gemini, Cursor, and Codex without rewriting your process around one tool.
aigon install-agent cc gg cx cu
Shared lifecycle
Aigon links discovery, implementation, review, and follow-up so each cycle improves the next one.
research -> feature -> eval -> done
Operational clarity
Pick the right execution mode for each task and make expected behavior explicit before coding starts.
aigon feedback-triage 14
Choose your mode
Hands-on + one agent
Use when you want tight control over implementation details and review checkpoints.
aigon feature-setup 07
Outcome: one guided implementation branch with a full spec and log trail.
Hands-on + multi-agent
Use when you want competing implementations you can evaluate and combine.
aigon feature-setup 07 cc gg cx
Outcome: parallel worktrees and comparable outputs for structured selection.
Hands-off + one agent
Use when the scope is clear and you want autonomous retries against validation checks.
aigon feature-implement 07 --autonomous
Outcome: automated implement-validate loop that stops when checks pass or budget ends.
Hands-off + multi-agent
Use when you want autonomous parallel exploration and then review converged outcomes.
aigon feature-setup 07 cc gg cx
# in each worktree:
aigon feature-implement 07 --autonomous --auto-submit
Outcome: concurrent autonomous runs across agents with logs ready for comparison.
Terminal examples by mode
The big picture
Explore alternatives, constraints, and market context with multiple agents.
Convert winning ideas into specs that define scope, intent, and success criteria.
Evaluate implementations, merge the strongest option, and keep rationale in logs.
Capture user signals and route them back into research and planning.
How it works
01
aigon feature-create "jwt-auth"
aigon feature-prioritise jwt-auth
02
# Drive
aigon feature-setup 07
# Fleet
aigon feature-setup 07 cc gg cx
# Swarm
aigon feature-setup 07 cc gg cx
# then in each worktree:
aigon feature-implement 07 --autonomous --auto-submit
03
aigon worktree-open 07 --all
# then in each agent:
/aigon:feature-implement 07
04
# in your agent:
/aigon:feature-eval 07
aigon feature-done 07 cx --adopt
aigon feature-cleanup 07
Documentation
git clone https://github.com/jayvee/aigon.git
cd aigon
npm install
npm link
cd /path/to/your/project
aigon init
aigon install-agent cc gg cx cu
aigon feature-now "dark-mode"
Tech & philosophy
Aigon is built for teams who want disciplined AI-assisted engineering, not opaque automation.
Community
Contribute specs, improve workflows, and share real-world patterns for running multi-agent engineering teams effectively.