# Standard Operating Procedure: Task Manager Workflow **Document ID:** SOP-TASK-001 **Version:** 1.0 **Effective Date:** 2026-03-25 **Applies To:** All Agents (Mega, Athena) **System:** GNL324 Agent Workspace --- ## 1. PURPOSE This SOP establishes the standard workflow for managing tasks in the GNL324 Agent Workspace. It ensures consistent task tracking, clear handoffs between agents, and proper review processes. --- ## 2. WORKFLOW OVERVIEW The task manager uses a **5-stage workflow**: ``` ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │ Priority 1 │ │ Priority 2 │ │ In Prog │ │ In Review │ │ Approved │ │ (🔴 P1) │ → → │ (🟡 P2) │ → → │ (🟣 IP) │ → → │ (⚪ IR) │ → → │ (✅ AP) │ │ CRITICAL │ │ IMPORTANT │ │ ACTIVE │ │ PENDING │ │ DONE │ └─────────────┘ └─────────────┘ └─────────────┘ └─────────────┘ └─────────────┘ ↓ ┌─────────────┐ │ 🔄 REVISE │ │ (Back to │ │ In Prog) │ └─────────────┘ ``` ### Stage Definitions: | Stage | Icon | Description | Who Can Move | |-------|------|-------------|--------------| | **Priority 1** | 🔴 | Critical tasks - do immediately | Any agent | | **Priority 2** | 🟡 | Important tasks - do after P1 | Any agent | | **In Progress** | 🟣 | Currently being worked on | Any agent | | **In Review** | ⚪ | Completed, awaiting Mega's review | Any agent | | **Approved** | ✅ | Reviewed and approved by Mega | Mega only | --- ## 3. CREATING A NEW TASK ### 3.1 When to Create a Task Create a task when: - Assigned new work by Noel - Discovered a bug or issue - Identified an improvement opportunity - Planning new features ### 3.2 How to Create a Task 1. **Log in** to the workspace: https://team01.noelgrca.com/ 2. **Scroll to** the "Task Manager" section 3. **Enter task name** in the text field 4. **Select initial status** from dropdown: - 🔴 **Priority 1**: If critical/urgent - 🟡 **Priority 2**: If important but not urgent - 🟣 **In Progress**: If starting work immediately 5. **Click** "Add Task" ### 3.3 Task Naming Guidelines ✅ **Good examples:** - "Fix login error on mobile Safari" - "Update TOOLS.md with new API credentials" - "Create mockups for dashboard redesign" ❌ **Bad examples:** - "Fix stuff" (too vague) - "Work on project" (not specific) - "URGENT!!!!" (use Priority 1 instead) --- ## 4. WORKING ON TASKS ### 4.1 Starting Work When you begin working on a task: 1. **Find your task** in the list 2. **Click** the → (next) button until it reaches "🟣 In Progress" 3. **Begin work** on the task 4. **Keep the task** in "In Progress" while working ### 4.2 Task Movement Rules | Action | Button | When to Use | |--------|--------|-------------| | **Move Forward** | → | Task is ready for next stage | | **Move Back** | ← | Task needs to go back to previous stage | | **Submit for Review** | 👁️ | Work is complete, ready for Mega | | **Delete** | × | Task is no longer needed | ### 4.3 Priority Guidelines **🔴 Priority 1 (Critical):** - Production systems down - Security vulnerabilities - Data loss issues - Blocking other agents **🟡 Priority 2 (Important):** - Feature requests - Non-critical bugs - Improvements - Documentation updates --- ## 5. SUBMITTING FOR REVIEW ### 5.1 When to Submit for Review Submit a task for review when: - ✅ All work is complete - ✅ Code is tested - ✅ Changes are deployed (if applicable) - ✅ Documentation is updated ### 5.2 How to Submit for Review #### Step 1: Move Task in Task Manager 1. Find your completed task 2. Click the **👁️ (eye) button** or use → arrows 3. Task now shows "⚪ In Review" #### Step 2: Document in MEGA_REVIEW.md **This is REQUIRED for every review submission** 1. **Open** MEGA_REVIEW.md: https://team01.noelgrca.com/MEGA_REVIEW.md 2. **Click "Edit"** or download and edit 3. **Add your task** using this template: ```markdown ### Task #[Next Number] - [Brief Task Name] **Submitted by:** [Your Name] **Date:** [YYYY-MM-DD] **Status:** ⏳ Pending Review **Description:** [What was accomplished in 2-3 sentences] **Changes Made:** - [x] Specific change 1 - [x] Specific change 2 - [x] Specific change 3 **Files Modified:** - `path/to/file.php` (what changed) - `path/to/config.js` (what changed) **Testing:** - [x] Tested on production - [x] Verified functionality - [ ] Test pending (explain why) **How It Works:** [2-3 sentences explaining the implementation] **Action Required:** - [ ] Review specific section - [ ] Test specific functionality - [ ] Approve and merge **Notes:** [Any special notes, limitations, or questions] ``` 4. **Save** the file #### Step 3: Notify Mega - Send a message in Telegram tagging @GNL_Megabot - Or mention in heartbeat check - Include: "Task #[Number] ready for review in MEGA_REVIEW.md" --- ## 6. MEGA REVIEW PROCESS ### 6.1 For Agents (Athena) After submitting: 1. **Wait** for Mega's review 2. **Monitor** MEGA_REVIEW.md for updates 3. **If revision requested:** - Move task back to "🟣 In Progress" - Make required changes - Resubmit for review 4. **If approved:** - Task stays in "✅ Approved" - Archive or delete after 30 days ### 6.2 For Mega When reviewing: 1. **Check** MEGA_REVIEW.md regularly 2. **Review** the submitted work 3. **Update status** in MEGA_REVIEW.md: - ✅ **Approved**: Move to [Approved] section - 🔄 **Revision Required**: Move to [Revision Required] section with feedback 4. **Update task** in Task Manager to "✅ Approved" (if approving) --- ## 7. BEST PRACTICES ### 7.1 Task Hygiene - ✅ **Keep tasks specific** - One deliverable per task - ✅ **Update status frequently** - Don't leave in wrong stage - ✅ **Delete abandoned tasks** - Don't clutter the board - ✅ **Use descriptive names** - Clear to anyone reading ### 7.2 Communication - ✅ **Document thoroughly** in MEGA_REVIEW.md - ✅ **Link related files** in your submission - ✅ **Ask questions** if requirements unclear - ✅ **Report blockers** immediately ### 7.3 What NOT to Do - ❌ Don't mark complete without testing - ❌ Don't skip MEGA_REVIEW.md documentation - ❌ Don't leave tasks "In Progress" for days without updates - ❌ Don't move tasks to "Approved" yourself (Mega only) --- ## 8. EXAMPLES ### Example 1: Bug Fix **Scenario:** Fix login error on mobile 1. **Create task:** "Fix mobile login error" → Priority 1 2. **Fix the bug** 3. **Test** on mobile devices 4. **Move to** "⚪ In Review" 5. **Document in MEGA_REVIEW.md:** - What caused the bug - How it was fixed - Test results 6. **Notify Mega** ### Example 2: New Feature **Scenario:** Add dark mode toggle 1. **Create task:** "Add dark mode toggle" → Priority 2 2. **Move to** "🟣 In Progress" 3. **Implement** the feature 4. **Test** thoroughly 5. **Move to** "⚪ In Review" 6. **Document in MEGA_REVIEW.md:** - Implementation details - Files changed - How to test 7. **Notify Mega** --- ## 9. TROUBLESHOOTING | Problem | Solution | |---------|----------| | Task won't move | Refresh page and try again | | Can't find my task | Check all sections, may be in wrong status | | MEGA_REVIEW.md won't save | Check file permissions or contact Mega | | Not sure what status to use | Ask Mega in chat | --- ## 10. QUICK REFERENCE ### Workflow Cheat Sheet ``` NEW TASK → Select priority → Work on it → Complete? → Submit for review ↓ Document in MEGA_REVIEW.md ↓ Mega reviews ↓ ┌─────────┴─────────┐ ↓ ↓ ✅ Approved 🔄 Revise ↓ ↓ Done! Back to work ``` ### Button Guide | Button | Action | |--------|--------| | → | Move to next stage | | ← | Move to previous stage | | 👁️ | Quick submit for review | | × | Delete task | --- ## 11. REVISION HISTORY | Version | Date | Changes | Author | |---------|------|---------|--------| | 1.0 | 2026-03-25 | Initial SOP | Mega | --- **Questions?** Contact Mega via Telegram @GNL_Megabot **Related Documents:** - TASKS.md - Active task list - MEGA_REVIEW.md - Review submissions - AGENTS.md - Team information