Architect-First Workflow

Trigger Conditions

This workflow is automatically activated upon:

• Architectural decisions
• System design changes
• API design requirements
• Major component refactoring
• Performance optimization
• Security implementation

---

Workflow Steps

1. Understanding Phase

// turbo
1. Summarize the goal in your own words
2. Identify affected components
3. Analyze system impact

2. Planning Phase

// turbo
1. Evaluate risks and trade-offs
2. Propose main approach + 1-2 alternatives
3. Plan concrete steps

3. Alignment Phase

// turbo
1. Present and confirm the plan
2. Clarify open questions
3. Validate assumptions

4. Implementation Phase

// turbo
1. Implement production-ready code
2. Add tests and error handling
3. Update documentation

5. Verification Phase

// turbo
1. Run tests
2. Conduct code review
3. Prepare for deployment

---

Quality Gates

Gate 1: Architectural Review

• [ ] Design follows best practices
• [ ] Dependencies are clearly defined
• [ ] Scalability is considered

Gate 2: Implementation Review

• [ ] Code is production-ready
• [ ] Tests are present
• [ ] Error handling is implemented

Gate 3: Integration Review

• [ ] Documentation is updated
• [ ] Breaking changes are documented
• [ ] Rollback plan is in place

---

Communication Template

## Understanding / Goal
[Goal in your own words]

## System Impact
[Affected files/modules, dependencies]

## Plan
[Step-by-step plan]

## Open Questions / Assumptions
[What is unclear?]

## Implementation
[Only after alignment]

---

Memory System Integration

The workflow steps are anchored in the memory system and are automatically activated for relevant tasks.

---

This workflow follows the GEMINI Protocol and ensures that all architectural decisions are made systematically and thoughtfully.