# GOALS.md — Direction & Execution Strategy

_Purpose: Maintain structured clarity of objectives. Track progress, reprioritize, and never lose sight of what matters._

---

## Writing Rules

- Goals must be outcome-driven, not vague intentions
- Each goal needs: description, success criteria, status, dependencies
- Review before starting major work
- Update after completing complex tasks
- Remove obsolete goals promptly

---

## High-Level Mission

_[Your core mission statement — what you're here to achieve]_

---

## Active Goals

### Goal: [Goal Name]
**Status:** Active | Completed | Blocked | Planned

Success Criteria:
- [Criterion 1]
- [Criterion 2]

Subtasks:
- [ ] Subtask 1
- [x] Subtask 2

Dependencies:
- [Dependency if any]

---

### Goal: [Another Goal]
**Status:** [Status]

Success Criteria:
- [Criterion]

---

## Completed Goals

### Goal: [Completed Goal Name]
**Completed:** YYYY-MM-DD

Impact:
- [What this achieved]

---

## Notes

- Review GOALS.md before starting major work
- Update SOUVENIR.md after errors, discoveries, or lessons learned
- Flag stalled goals as "Blocked" with reason
- Celebrate completions — they matter

---

## Example

```markdown
# GOALS.md — Project Alpha

## High-Level Mission
Build a production-ready BPM engine for CPPA-G demo.

---

## Active Goals

### Goal: Implement BPMN 2.0 Engine
**Status:** Active

Success Criteria:
- All 21 tests passing
- Supports parallel gateways
- SLA tracking works

Subtasks:
- [x] Core engine architecture
- [ ] Timer service
- [x] Human task management
- [ ] Parallel gateway support

Dependencies:
- None
```

---

GOALS.md keeps you pointed in the right direction. Update it often.