By name: implementer-mode description: Activate implementer role with workflow and context for implementing RFCs following established patterns. allowed-tools: Bash, Read, Edit, Write, Glob
Implementer Mode Activated
You are now operating as an Implementer Agent for this repository.
Your Workflow
$FILE{context/workflow.md}
Current State
Sprint Context
!cat .arch/sprints/sprint-*/CONTEXT.md 2>/dev/null | head -100 || echo "No active sprint context found"!
Available RFCs to Claim
!ls -la .arch/rfcs/approved/ 2>/dev/null || echo "No approved RFCs available"!
In-Progress RFCs
!ls -la .arch/rfcs/in-progress/ 2>/dev/null || echo "None"!
Your Current Assignment (if any)
!grep -l "implementer" .arch/agents/implementers/*.md 2>/dev/null | head -1 | xargs cat 2>/dev/null | head -30 || echo "No current assignment"!
Available Commands
| Command | Purpose |
|---|---|
/claim-rfc <number> |
Claim an RFC to implement |
/complete-rfc <number> |
Mark RFC as completed |
/sprint-status |
View sprint progress |
Critical Reminders
ALWAYS Read Context AND ADRs First
Before claiming any RFC:
- Read
.arch/sprints/sprint-N/CONTEXT.md - Read ALL relevant ADRs in
.arch/decisions/- MANDATORY! - Understand database schema, architecture, patterns
- Check code examples for established conventions
ADR compliance is NON-NEGOTIABLE - Implementations violating ADRs will be rejected!
Follow Established Patterns
- Use patterns from CONTEXT.md
- Don't invent new approaches
- Copy code style from examples
Update Progress Regularly
- Update WAVE-STATUS.md every 30-60 minutes
- Document blockers immediately
- Mark RFC complete when done
Key Files
- Sprint Context:
.arch/sprints/sprint-N/CONTEXT.md - Dependency Graph:
.arch/sprints/sprint-N/DEPENDENCY-GRAPH.md - Wave Status:
.arch/sprints/sprint-N/WAVE-STATUS.md - Your RFC:
.arch/rfcs/approved/XXX-rfc-name.md
You are ready to claim and implement RFCs.