The Seven Skills
Seven skills. One pipeline. Your project gets sharper with each one.
Plus: maintain (ongoing), snap (audit)
gigo
You go from an empty project to an expert team in one conversation. Describe what you’re building, pick your working language, and GIGO researches the best practitioners in that field. Real people, real philosophies, blended into team members who have opinions and push back. Then it scaffolds everything: lean rules, deep references, session-end audits.
What you get: A project that starts with expertise instead of trial and error. Your team is active from the first message. Need vanilla Claude? /team off. Want the team back? /team on.
Example: “Building a CLI tool for database migrations. Go, targets Postgres and MySQL.” → GIGO proposes The Migration Architect (Andrew Kane + Sandi Metz), The CLI Designer (Steve Francia + Rob Pike), The Test Strategist (Mitchell Hashimoto).
gigo:blueprint
Your expert team plans the work before anyone builds anything. A quick fix gets a short brief. A complete overhaul gets a full design with independent adversarial review and an ordered implementation plan. Blueprint scales to the task.
The fact-checker validates your design against the real project before you commit. The Challenger reviews your spec blind, looking for what will break. No execution without an approved plan.
What you get: Hand it something ambitious and it breaks it down so you can execute with confidence.
gigo:execute
Workers build from the spec your team wrote. They get the requirements, not the rules. Three execution tiers depending on your needs: full parallelization, sequential with some parallelization, or simple inline.
The quality comes from the spec, not from loading workers with extra context. Testing validated this: workers with good specs consistently produce first-pass quality that sticks.
What you get: Output that matches the spec without hand-holding.
gigo:verify
An independent reviewer catches what the worker missed. Two focused passes: “Did you build the right thing?” checks output against the spec. “Is the work good?” checks correctness, consistency, and completeness. Two passes find more than one pass trying to do both.
Issues get triaged: auto-fix (worker handles it), ask-operator (needs your input), or accept (noted for later).
What you get: Reviews that catch real problems, not rubber stamps.
gigo:snap
Your project gets sharper instead of bloated. At the end of every session, The Snap runs a 10-point audit: removes stale rules, merges overlaps, enforces line budgets, checks that your team still covers what your project needs. Then it captures what you learned and routes it to the right file.
A lean project with missing knowledge outperforms a bloated one with everything.
What you get: A project that improves every session instead of rotting.
gigo:retro
Your sessions teach your project to be better. Retro reads what happened, finds where things got stuck, and proposes specific fixes so the next session is smoother. Not a report you have to interpret. Concrete proposals backed by session data.
First real run found the exact pain points, proposed 4 fixes, all approved and shipped.
What you get: Your next session is less painful than your last one.
gigo:maintain
Your team grows with your project. Need a new area of expertise? Maintain adds it. Project drifted? It restructures. Setup outdated? It upgrades. Auto-detects what kind of maintenance your project needs.
Also kicks in automatically during planning when the team spots an expertise gap.
What you get: An expert team that stays relevant as your project evolves.