3dbbc069f7
- New folder: docs/tasks-active/ with individual task files - Each task = separate markdown file with frontmatter metadata - Migrated 6 key tasks (26, 87, 93, 94, 98, 99) as examples - Added comprehensive README with workflow documentation Task Files Created: - task-026-modpack-version-checker.md (P1, IN_PROGRESS) - task-087-arbiter-lifecycle-handlers.md (P0, COMPLETE, BLOCKER) - task-093-trinity-codex.md (P1, PLANNED) - task-094-global-restart-scheduler.md (P1, PLANNED) - task-098-discord-channel-automation.md (P2, PLANNED) - task-099-claude-projects-architecture.md (P1, READY) Benefits: - Decap CMS shows individual tasks instead of two giant files - Sortable by priority (blockers first) - Filterable by status, blocker flag, priority - Mobile-friendly individual entries - Links to full specs in /docs/tasks/ - Easy to add/edit/complete tasks via UI For Future Chroniclers: - README documents full workflow - Template structure established - Integration with existing /docs/tasks/ specs
184 lines
4.4 KiB
Markdown
184 lines
4.4 KiB
Markdown
# 📋 Active Tasks — Individual Task Files
|
|
|
|
**Created:** April 7, 2026
|
|
**Created By:** Chronicler #67
|
|
**Purpose:** Individual task files for Decap CMS display
|
|
|
|
---
|
|
|
|
## What This Folder Is
|
|
|
|
This folder contains **individual markdown files for each active task** to make them easy to view and edit in Decap CMS.
|
|
|
|
**Each file = one task** with:
|
|
- Frontmatter metadata (priority, status, blocker flag)
|
|
- Summary of the task
|
|
- Current status
|
|
- Next steps
|
|
- Link to full spec in `/docs/tasks/`
|
|
|
|
---
|
|
|
|
## File Naming Convention
|
|
|
|
```
|
|
task-[NUMBER]-[slug].md
|
|
```
|
|
|
|
Examples:
|
|
- `task-026-modpack-version-checker.md`
|
|
- `task-094-global-restart-scheduler.md`
|
|
- `task-099-claude-projects-architecture.md`
|
|
|
|
---
|
|
|
|
## Frontmatter Fields
|
|
|
|
Every task file MUST include:
|
|
|
|
```yaml
|
|
---
|
|
task_number: 26
|
|
title: Modpack Version Checker
|
|
priority: 1 # 0=blocker, 1=high, 2=medium, 3=low, 4=personal
|
|
status: IN_PROGRESS # PLANNED, READY, IN_PROGRESS, BLOCKED, COMPLETE
|
|
is_blocker: false # true for soft launch blockers
|
|
tags: [commercial, pterodactyl]
|
|
estimated_hours: 40
|
|
---
|
|
```
|
|
|
|
Optional fields:
|
|
- `completed_date: 2026-04-06` (for completed tasks)
|
|
- `blocked_by: "Blueprint reinstallation"` (for blocked tasks)
|
|
|
|
---
|
|
|
|
## Priority Levels
|
|
|
|
| Priority | Label | Meaning |
|
|
|----------|-------|---------|
|
|
| 0 | BLOCKER | Soft launch critical (must complete first) |
|
|
| 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
|
|
|
|
| Status | Meaning |
|
|
|--------|---------|
|
|
| PLANNED | Spec exists, not started |
|
|
| READY | Ready to implement (no blockers) |
|
|
| IN_PROGRESS | Currently being worked on |
|
|
| BLOCKED | Cannot proceed (dependency or blocker) |
|
|
| COMPLETE | Done, documented, deployed |
|
|
|
|
---
|
|
|
|
## How to Add a New Task
|
|
|
|
### 1. Create the file
|
|
|
|
```bash
|
|
cd /home/claude/firefrost-operations-manual/docs/tasks-active
|
|
touch task-[NUMBER]-[slug].md
|
|
```
|
|
|
|
### 2. Add frontmatter + content
|
|
|
|
Copy template from any existing task file.
|
|
|
|
### 3. Commit to Git
|
|
|
|
```bash
|
|
git add docs/tasks-active/task-[NUMBER]-[slug].md
|
|
git commit -m "Add Task #[NUMBER]: [Title]"
|
|
git push origin master
|
|
```
|
|
|
|
### 4. View in Decap CMS
|
|
|
|
Visit https://firefrostgaming.com/admin
|
|
Click "🔥 TASKS"
|
|
Your task appears in the list!
|
|
|
|
---
|
|
|
|
## How to Update a Task
|
|
|
|
### Option 1: Decap CMS (Easiest)
|
|
|
|
1. Go to https://firefrostgaming.com/admin
|
|
2. Click "🔥 TASKS"
|
|
3. Click the task you want to edit
|
|
4. Make changes
|
|
5. Click "Save" (creates draft) or "Publish" (goes live)
|
|
|
|
### Option 2: Direct Git Edit
|
|
|
|
1. Edit the task file in `/docs/tasks-active/`
|
|
2. Commit and push
|
|
3. Changes appear in Decap CMS automatically
|
|
|
|
---
|
|
|
|
## Relationship to Other Task Files
|
|
|
|
### `/BACKLOG.md` (Repo Root)
|
|
- **Legacy system** — simple table of all tasks
|
|
- **Still maintained** for quick reference
|
|
- **Will eventually be retired** when all tasks migrated to this folder
|
|
|
|
### `/docs/tasks/` (Full Specs)
|
|
- **Deep documentation** — full implementation guides
|
|
- **Never deleted** — permanent reference
|
|
- **Linked from** task-active files via "Full Spec Location" section
|
|
|
|
### Task-Active Files (This Folder)
|
|
- **Decap CMS display layer** — what you see in admin UI
|
|
- **High-level summaries** — current status, next steps
|
|
- **Links to full specs** — points to /docs/tasks/ for details
|
|
|
|
---
|
|
|
|
## For Future Chroniclers
|
|
|
|
### When Creating a New Task
|
|
|
|
1. ✅ Create full spec in `/docs/tasks/task-[NUMBER]-[name]/`
|
|
2. ✅ Create summary file in `/docs/tasks-active/task-[NUMBER]-[slug].md`
|
|
3. ✅ Update `/BACKLOG.md` table (for now, until deprecated)
|
|
4. ✅ Commit all three
|
|
|
|
### When Completing a Task
|
|
|
|
1. ✅ Update status to `COMPLETE` in task-active file
|
|
2. ✅ Add `completed_date` frontmatter field
|
|
3. ✅ Move from active section to "Recently Completed" in `/BACKLOG.md`
|
|
4. ✅ Leave full spec in `/docs/tasks/` (never delete)
|
|
|
|
### When a Task is Blocked
|
|
|
|
1. ✅ Update status to `BLOCKED`
|
|
2. ✅ Add `blocked_by: "reason"` frontmatter
|
|
3. ✅ Note blocker in task body
|
|
4. ✅ Move to "BLOCKED" section in `/BACKLOG.md`
|
|
|
|
---
|
|
|
|
## Mobile-Friendly Note
|
|
|
|
**Decap CMS works on mobile**, but firefrostgaming.com/admin is not yet mobile-optimized.
|
|
|
|
**Future enhancement:** Make Decap CMS responsive for phone/tablet editing.
|
|
|
|
---
|
|
|
|
**Fire + Frost + Foundation = Where Love Builds Legacy** 🔥❄️
|
|
|
|
**Created by:** Chronicler #67
|
|
**For:** Michael, Meg, Holly, and all future Chroniclers
|