Initial commit

skills/dev-guided/references/template-decisions.md

@@ -0,0 +1,65 @@
+# Decisions
+
+This document captures explicit human choices on unclear aspects of the implementation. Each decision includes the context, options considered, and the chosen approach with rationale.
+
+## Decision Template
+
+Use this format for each decision:
+
+```markdown
+## [Decision Topic]
+
+**Context:** [Why does this decision need to be made?]
+
+**Options Considered:**
+1. [Option A] - [Brief description]
+2. [Option B] - [Brief description]
+
+**Decision:** [Chosen option]
+
+**Rationale:** [Why this choice was made]
+
+**Date:** YYYY-MM-DD
+```
+
+---
+
+## Example Decisions
+
+### Language Choice
+
+**Context:** Need to choose implementation language for the new service.
+
+**Options Considered:**
+1. Python - Good for rapid development, rich ecosystem
+2. Go - Better performance, strong concurrency support
+3. Rust - Maximum performance and safety
+
+**Decision:** Python
+
+**Rationale:** Team is most familiar with Python, and performance requirements don't justify the learning curve of Go or Rust. We can optimize later if needed.
+
+**Date:** 2025-11-24
+
+---
+
+### Database Storage
+
+**Context:** Need to store user session data.
+
+**Options Considered:**
+1. PostgreSQL - Relational, ACID guarantees
+2. Redis - In-memory, fast but volatile
+3. DynamoDB - Managed NoSQL, scalable
+
+**Decision:** Redis with PostgreSQL backup
+
+**Rationale:** Redis for fast session access, PostgreSQL for persistence. Hybrid approach gives us speed and durability.
+
+**Date:** 2025-11-24
+
+---
+
+## Current Decisions
+
+[Add decisions here as they are made during the development session]