Getting Started
Usage
Day-to-day patterns for working with Gem Team.
Start a Task
Just describe what you need. The Orchestrator handles the rest: context gathering, complexity classification, planning, delegation, and verification.
"Add a rate limiter to the API gateway"
"Find out why the login flow fails on iOS Safari"
"Review the auth module for security issues"
Complexity at a Glance
| Complexity | When | What You See |
|---|---|---|
| TRIVIAL | Typo fix, rename, one-shot command | Instant result, no visible plan |
| LOW | 1-2 files, known pattern | Quick execution, minimal feedback |
| MEDIUM | Multiple files, new pattern, moderate uncertainty | Plan artifact created, wave progress shown |
| HIGH | Architecture change, API/schema/auth, broad risk | Full plan with validation gates per wave |
Plans Are Resumable
MEDIUM/HIGH tasks produce durable plan artifacts:
docs/plan/{plan_id}/
plan.yaml # Task breakdown with dependencies
context_envelope.json # Progressive context cache
tasks/ # Individual results per task
You can pause mid-work and resume later by referencing the plan ID:
continue plan 20260714-api-rate-limiter
After Each Task
Gem Team persists what it learns:
- Product decisions →
docs/PRD.yaml - Technical conventions →
AGENTS.md - Patterns & gotchas → Memory (repo/session/global)
- Repeatable workflows →
docs/skills/(asSKILL.mdplaybooks)
Practical Tips
- Be specific: clearer input → better plans. Include error messages, file paths, and expected behavior.
- Check plan artifacts for MEDIUM/HIGH tasks: they show the full breakdown before execution starts.
- Use plan IDs to reference ongoing work, even across sessions.
- Keep
apm_modules/in.gitignore: it's an install cache, not project code.
Next
Workflow → · Features → · Configuration →