/decision - Log Decision

Record a technical or product decision in the decision log.

Usage

/decision "Decision title"

Or interactive mode:

/decision

Examples

/decision "Use PostgreSQL for primary database"
/decision "Implement JWT for API authentication"
/decision "Adopt React Query for server state management"

What It Does

1. Prompts for decision details (if not provided):

   • Decision title
   • Context (why this decision was needed)
   • Options considered
   • Decision made and rationale
   • Consequences/trade-offs

2. Creates entries in:

   • Confluence Decision Log
   • Related Jira tickets (if applicable)

3. Links to relevant context:

   • ADRs
   • Related stories
   • Technical documentation

Output Format

## Decision Recorded

**ID:** DEC-042
**Title:** Use PostgreSQL for primary database
**Date:** 2024-01-15
**Status:** Accepted

### Context
Need to select primary database for new service.
Expected data: 10M+ records, complex queries, ACID required.

### Options Considered
1. **PostgreSQL** - Mature, strong consistency, excellent query planner
2. **MySQL** - Familiar, good performance, wide hosting options
3. **MongoDB** - Flexible schema, horizontal scaling

### Decision
PostgreSQL selected.

### Rationale
- Complex query requirements favor PostgreSQL's query planner
- ACID compliance critical for financial data
- Team has PostgreSQL expertise
- PostGIS support needed for future geo features

### Consequences
- Need PostgreSQL hosting (managed preferred)
- Team training on PostgreSQL-specific features
- Migration path from prototype MySQL database needed

**Confluence:** [Decision Log Entry](link)
**Related:** PROJ-123, PROJ-124

Skill Used

confluence-decision-log

When to Use Agent Instead

Use the Software Architect agent when:

• Decision requires technical analysis first
• ADR (Architecture Decision Record) needed
• Trade-off analysis required
• Multiple stakeholders need input