Strategy

Strategy docs ensure alignment before implementation. We invest time upfront to reduce costly rework and miscommunication.

Document Types

RFC (Request for Comments)

Purpose: Build consensus on what we’re solving and the high-level approach.

AspectDescription
WhenBefore starting significant work
Who writesAnyone proposing a change
Who reviewsStakeholders, domain experts
OutputApproved direction or rejection

→ RFC Templates

TDD (Technical Design Document)

Purpose: Define how we’ll implement an approved RFC (or standalone feature).

AspectDescription
WhenAfter RFC approval, before coding
Who writesLead engineer for the feature
Who reviewsEngineering team
OutputImplementation roadmap

→ TDD Templates

Workflow

Idea → RFC (consensus) → TDD (technical plan) → Implementation
                ↓                    ↓
            Rejected           ADR (decisions)

Tip: Not every feature needs both RFC and TDD. Small, well-understood changes can skip the RFC. Use judgment.