-
Notifications
You must be signed in to change notification settings - Fork 36
Open
Labels
Description
Drafter Agent Mission
Your role: Analyze upstream changes with extreme thoroughness. Quality >> Speed >> Cost.
Upstream range: HEAD~50..upstream/main
Commits to analyze: 4594
Required Reading
Before starting, read these documents completely:
AGENTS.md— Project identity and golden rulesdocs-terminai/FORK_ZONES.md— Zone classification (CANON/LEVERAGE/SKIP)docs-terminai/UPSTREAM_SCRUB_RULES.md— Deep scrub rule set
Drafter Process
Phase 1: Fetch & Analyze
git remote add upstream https://github.com/google-gemini/gemini-cli.git 2>/dev/null || true
git fetch upstream
git log HEAD~50..upstream/main --name-only --onelinePhase 2: Classify Every Commit
Apply UPSTREAM_SCRUB_RULES.md to each commit:
- 🟢 LEVERAGE: Clean, no overlaps, cherry-pick directly
- 🔴 CANON: Overlaps our systems, reimplement intent
- 🟡 QUARANTINE: Uncertain, needs human decision
- ⚪ SKIP: Irrelevant (telemetry, version bumps)
Grounding requirements:
- Before mentioning a file → Run
lsto verify it exists - Before claiming overlap → Run
grepto confirm - Every classification → Must reference real commit hash
Phase 3: Architecture for CANON
For each 🔴 CANON commit, write full architecture spec:
- Upstream intent analysis
- Our system context (with diagram)
- Technical specification
- Data models
- Security considerations
- Testing strategy
Phase 4: Atomic Task List
For each architecture, write complete task list:
- Each task 5-30 minutes
- Include code snippets
- Include verification commands
- Include potential issues
Output
Create file: docs-terminai/upstream-merges/WeekOfFeb12_drafter.md
Use template from: docs-terminai/templates/upstream-merge-plan.md
Complete Sections 1-3 (Classification, Architecture, Tasks).
Leave Sections 4-5 (Red-Team, Local) empty for next agents.
Quality Standards
- Take as long as needed for perfection
- Length is acceptable if accurate and complete
- Every claim must be verifiable
- When in doubt, provide more detail
- Mark uncertainty as QUARANTINE, don't guess
When Complete
- Commit the merge plan file
- Open a PR titled:
[Upstream Sync] Week of Feb12 - Assign label:
upstream-sync - The Red-Team agent will be triggered automatically
Reactions are currently unavailable