# [Project Name]

*Initialized: [date]*

## What This Is

[2-3 sentence description. What does this project do and who is it for?]

Example: *A CLI tool that automates database schema migrations for PostgreSQL. Designed for backend teams who need repeatable, version-controlled database changes without manual SQL execution.*

## Core Value

[The ONE thing that matters most. If everything else fails, this must work.]

Example: *Migrations apply in correct order without data loss.*

## Success Criteria

Project succeeds when:
- [ ] [Observable outcome 1 - something you can verify by testing/running]
- [ ] [Observable outcome 2 - a measurable quality or capability]
- [ ] [Observable outcome 3 - user feedback or real-world validation]

*These are high-level goals that connect daily WORK.md logs to overall project intent. Keep it simple - 3-5 items is ideal.*

## Context

[Background that informs implementation:]

**Technical environment:**
- [What platform/runtime/constraints shape this project?]

**Prior work:**
- [Is this replacing something? Building on existing tools?]

**User needs:**
- [What problem does this solve? Who asked for it?]

*Provide just enough context so implementation decisions make sense. Avoid speculation.*

## Constraints

- **[Type]:** [What] - [Why this limitation exists]
- **[Type]:** [What] - [Why this limitation exists]

*Examples:*
- *Memory: 8GB RAM limit - Running on budget VPS plan*
- *Latency: Asia-Europe connection - Server hosted in Helsinki, client in Vietnam*
- *Dependencies: Standard library only - Must run in sandboxed environments*

---
*Update when project scope changes (new requirements, pivot, major feature addition)*
