Master Plan Manager

Intelligent management of MASTER_PLAN.md files with comprehensive safety measures.

When to Use

Use this skill when:

• Updating task status (TASK-XXX, BUG-XXX)

• Adding items to roadmap or ideas sections

• Modifying project tracking documentation

• Ensuring safe updates to critical planning files

Safety Protocol

MANDATORY before any MASTER_PLAN.md modification:

• Read First - Always read the entire file before editing

• Backup - Create timestamped backup before changes

• Validate - Check if update is actually needed (avoid duplicates)

• Preserve - Maintain existing structure and formatting

• Verify - Confirm integrity after changes

Core Operations

1. Status Updates

Update task/bug status in the Dependency Index table:

Status transitions:

• 📋 TODO → 🔄 IN PROGRESS → 👀 REVIEW → ✅ DONE

2. Adding New Items

New Task:

TASK-XXX: Task Title (📋 TODO)

Priority: P2-MEDIUM

Files to Modify:

• src/file.ts

Steps:

• Step 1
• Step 2

New Bug:

BUG-XXX: Bug Description (🔄 IN PROGRESS)

Severity: HIGH

Symptoms: What's wrong

Root Cause: (To be determined)

Roadmap Item:

| ROAD-XXX | Feature description | P2 | TODO | Notes |

3. Completing Items

When marking complete:

• Add strikethrough to ID: TASK-XXX

• Update status: (✅ DONE)

• Move to "Recently Completed" section

• Update Dependency Index table

4. ID Format

Prefix Usage

TASK-XXX

Features and tasks

BUG-XXX

Bug fixes

ROAD-XXX

Roadmap items

IDEA-XXX

Ideas to consider

ISSUE-XXX

Known issues

Safe Update Workflow

1. READ current MASTER_PLAN.md ↓
2. ANALYZE what needs to change ↓
3. CHECK if content already exists (avoid duplicates) ↓
4. BACKUP before modifications ↓
5. APPLY changes incrementally ↓
6. VALIDATE markdown structure ↓
7. CONFIRM with user if significant changes

Examples

Example 1: Mark Task Complete

Before:

TASK-033: Create Plugin (🔄 IN PROGRESS)

After:

TASK-033: Create Plugin (✅ DONE)

Also update Dependency Index:

| TASK-033 | ✅ DONE | plugin/* | - | - |

Example 2: Add New Bug

BUG-XXX: Button not responding (🔄 IN PROGRESS)

Severity: MEDIUM

Symptoms: Click handler not firing on mobile

Root Cause: Touch event not handled

Fix: Add touchstart listener

Example 3: Update Progress

Steps:

• Research ✅
• Implementation ✅
• Testing
• Documentation

Integration Commands

When chief-architect or other skills delegate:

master-plan-manager: update-status TASK-033 done master-plan-manager: add-task "New feature" P2 master-plan-manager: add-bug "Issue description" HIGH master-plan-manager: move-to-completed TASK-033

Validation Checklist

Before completing any update:

• Read entire file first

• Backup created

• No duplicate IDs

• Proper markdown formatting

• Strikethrough on completed IDs

• Status emoji matches state

• Dependency Index updated

Error Recovery

If something goes wrong:

Restore from backup

cp docs/MASTER_PLAN.md.backup docs/MASTER_PLAN.md

Or use git

git checkout HEAD -- docs/MASTER_PLAN.md

Best Practices

• Never blindly append - Always check if section exists

• Preserve formatting - Match existing style (emojis, spacing)

• Atomic updates - One logical change at a time

• User verification - Ask user to confirm significant changes

• Keep history - Document why changes were made