architect-patterns

Architect Patterns and Templates

This file contains detailed templates, examples, and patterns for creating architectural proposals. Load this file when you need to create proposals or epics.

Parent file: architect.md contains core instructions and workflow.

Contents

• Issue Template
• Issue Creation Command
• Autonomous Mode Assumptions Template
• Requirements Gathering Examples
• Epic Proposals
• Tracking Dependencies with Task Lists
• Goal Discovery Script
• Backlog Balance Check Script
• Milestone Alignment Examples

Issue Template

Use this template when creating architectural proposals:

## Problem Statement

Describe the architectural issue or opportunity. Why does this matter?

## Milestone Alignment

**Current Milestone**: [e.g., "M0 - Bootstrap" or "unknown if no roadmap found"]
**Alignment Tier**: [Tier 1 - Goal-Advancing | Tier 2 - Goal-Supporting | Tier 3 - General Improvement]
**Related Deliverable**: [If Tier 1/2, which specific deliverable does this advance?]
**Justification**: [Why this proposal matters for the current milestone]

## Current State

How does the system work today? What are the pain points?

## Requirements Gathered

Summarize the key constraints, priorities, and context from user responses:
- **Constraint**: [e.g., "500MB storage budget"]
- **Priority**: [e.g., "Simplicity over performance"]
- **Context**: [e.g., "Weekly re-analysis pattern"]
- **Existing**: [e.g., "Already using Redis for session storage"]

## Recommended Solution

**Approach**: [Single recommended approach name and brief description]

**Why This Approach**:
- Fits constraint: [How it addresses their specific constraint]
- Aligns with priority: [How it matches their stated priority]
- Matches context: [How it fits their usage pattern]
- Integrates well: [How it works with existing systems]

**Implementation**:
- [Key implementation steps or components]
- [Technical details relevant to this approach]

**Complexity**: Estimate (Low/Medium/High with brief justification)

**Dependencies**: Related issues or prerequisites (if any)

## Alternatives Considered

Briefly document other options you evaluated and why they were ruled out:

**[Alternative 1]**: [Why it doesn't fit] (e.g., "Manual invalidation - doesn't match preference for automatic cleanup")

**[Alternative 2]**: [Why it doesn't fit] (e.g., "LRU eviction - poor cache hit ratio for their access patterns")

## Impact

- **Files affected**: Rough estimate
- **Breaking changes**: Yes/No
- **Migration path**: How to transition
- **Risks**: What could go wrong

## Related

- Links to related issues, PRs, docs
- References to similar patterns in other projects