Getting Started
Five minutes from now, your project has an expert team.
What you need
Claude Code CLI installed. That’s it.
Install
From the marketplace
claude marketplace add croftspan/gigo
claude plugin install gigo
Manual install
git clone https://github.com/croftspan/gigo.git
cp -r gigo/skills/ ~/.claude/skills/
Your first expert team
Open any project and say “gigo.”
- Describe what you’re building. Be as vague or specific as you want. “A Rails API for library reservations” or “I’m thinking about writing kids’ mystery books.”
- GIGO finds the right experts. Real practitioners in your domain. Their specific philosophies, blended into team members who have opinions and push back.
- You shape the team. “Drop that one.” “Add a testing expert.” “Who would they disagree with?” The skill adjusts until it feels right.
- Your project is ready. Expert team assembled. Rules lean. Deep knowledge loaded on demand. Start building.
What you get
| File | What it gives you | When it loads |
|---|---|---|
CLAUDE.md |
Your expert team. Blended authorities, quality bars, and the autonomy model that keeps them effective | Every conversation |
.claude/rules/ |
The essentials. Standards and workflow that apply to all work. Lean by design (~60 lines per file) | Every conversation |
.claude/references/ |
Deep expertise. Authority profiles, technique catalogs, domain knowledge. Only loads when the task needs it | On demand only |
The result: your always-on context stays lean while deep expertise is available when the task calls for it. No bloat, no wasted attention. See how the architecture works →
What to do next
gigo:blueprint |
Your expert team plans the work. They catch the gaps you’d miss and produce a spec workers can follow. |
gigo:execute |
Workers build from the spec. First-pass quality that sticks. |
gigo:verify |
Two focused reviewers catch what one pass misses. Spec compliance, then output quality. |
gigo:snap |
Your project stays lean. Session-end audit that prevents the bloat that makes output worse. |
gigo:retro |
After a few sessions, see what’s working and what to fix. Your project learns from every session. |
See all seven skills for full documentation.