Add task management system documentation to Project Instructions
- Documented tasks-active system (individual task files) - Explained Decap CMS primary interface - Defined priority levels (0-4) and status values - Added workflow for creating/updating/completing tasks - Linked to full system docs in tasks-active/README.md For Future Chroniclers: - Clear guidance on task creation workflow - Decap CMS vs Git edit options explained - Link to deep dive in tasks-active/README.md - Ensures system continuity across sessions
This commit is contained in:
@@ -44,6 +44,68 @@ git config user.name "Claude"
|
|||||||
|
|
||||||
**Then ask Michael what needs to be done.**
|
**Then ask Michael what needs to be done.**
|
||||||
|
|
||||||
|
### Task Management System
|
||||||
|
|
||||||
|
**As of April 7, 2026:** Tasks are managed in **two places**:
|
||||||
|
|
||||||
|
#### 1. Decap CMS (Primary Interface)
|
||||||
|
- **URL:** https://firefrostgaming.com/admin
|
||||||
|
- **Collection:** 🔥 TASKS
|
||||||
|
- **Location:** `docs/tasks-active/` folder
|
||||||
|
- **Format:** Individual markdown files (one per task)
|
||||||
|
|
||||||
|
**Each task file includes:**
|
||||||
|
- Frontmatter: task_number, title, priority, status, is_blocker, tags, estimated_hours
|
||||||
|
- Summary: Overview, current state, next steps
|
||||||
|
- Link to full spec in `/docs/tasks/`
|
||||||
|
|
||||||
|
**Priority Levels:**
|
||||||
|
- `0` = BLOCKER (soft launch critical)
|
||||||
|
- `1` = HIGH (revenue impact or force multiplier)
|
||||||
|
- `2` = MEDIUM (important but not urgent)
|
||||||
|
- `3` = LOW (backlog, do when time allows)
|
||||||
|
- `4` = PERSONAL (Michael/Meg/Holly personal projects)
|
||||||
|
|
||||||
|
**Status Values:** PLANNED, READY, IN_PROGRESS, BLOCKED, COMPLETE
|
||||||
|
|
||||||
|
#### 2. Full Task Specs (Deep Storage)
|
||||||
|
- **Location:** `docs/tasks/task-[NUMBER]-[name]/`
|
||||||
|
- **Contains:** Complete implementation guides, architecture docs, code examples
|
||||||
|
- **Referenced from:** task-active files via "Full Spec Location" section
|
||||||
|
|
||||||
|
#### Creating a New Task
|
||||||
|
|
||||||
|
**Process:**
|
||||||
|
1. Create full spec in `/docs/tasks/task-[NUMBER]-[name]/README.md`
|
||||||
|
2. Create summary in `/docs/tasks-active/task-[NUMBER]-[slug].md`
|
||||||
|
3. Update `/BACKLOG.md` table (for now, until fully migrated)
|
||||||
|
4. Commit all three
|
||||||
|
|
||||||
|
**Template:** Copy frontmatter from any existing task-active file
|
||||||
|
|
||||||
|
#### Updating a Task
|
||||||
|
|
||||||
|
**Via Decap CMS (Easiest):**
|
||||||
|
1. Visit https://firefrostgaming.com/admin
|
||||||
|
2. Click 🔥 TASKS
|
||||||
|
3. Click the task
|
||||||
|
4. Edit fields or markdown
|
||||||
|
5. Save (draft) or Publish (live)
|
||||||
|
|
||||||
|
**Via Git:**
|
||||||
|
1. Edit `/docs/tasks-active/task-[NUMBER]-[slug].md`
|
||||||
|
2. Commit and push
|
||||||
|
3. Changes appear in Decap CMS automatically
|
||||||
|
|
||||||
|
#### Completing a Task
|
||||||
|
|
||||||
|
1. Set status to `COMPLETE` in task-active file
|
||||||
|
2. Add `completed_date: YYYY-MM-DD` frontmatter
|
||||||
|
3. Note completion in task body
|
||||||
|
4. Leave full spec in `/docs/tasks/` (never delete)
|
||||||
|
|
||||||
|
**Read the full system docs:** `/docs/tasks-active/README.md`
|
||||||
|
|
||||||
### Current Architecture (April 2026)
|
### Current Architecture (April 2026)
|
||||||
|
|
||||||
| Component | Technology | Location |
|
| Component | Technology | Location |
|
||||||
|
|||||||
Reference in New Issue
Block a user