plan-master¶

Cross-session project management using PMBOK methodology

Plan-Master is the project management brain of F3L1X. While Pipeline-Go governs HOW you write code (per-session methodology), Plan-Master governs WHAT you work on across sessions using industry-standard PMBOK practices.

What It Does¶

Plan-Master provides:

WBS Decomposition - Break projects into hierarchical work packages
EVM Tracking - Earned Value Management metrics (CPI, SPI, EAC)
Critical Path Analysis - Identify blocking task sequences
Risk Register - Track and mitigate project risks
Task Discovery - Automatically find the next ready work package
Realm Governance - Generate state.json and ASSIGNMENTS.md per realm

Think of Plan-Master as your project manager that never forgets context between sessions.

Key Capabilities¶

Work Breakdown Structure (WBS)¶

Plan-Master decomposes projects into hierarchical task trees:

Project: Website Builder
  1.0 Core Framework
    1.0.1 Registry App [completed]
    1.0.2 Classifier App [completed]
    1.0.3 Pipeline App [completed]
  2.0 Content System
    2.0.1 Editorial Workflow [in_progress]
    2.0.2 Staging Pipeline [not_started]

Each leaf node is a work package - a concrete, assignable unit of work with an estimated effort in sessions.

Earned Value Management (EVM)¶

Track project health with industry-standard metrics:

Metric	Meaning
CPI	Cost Performance Index - are you on budget?
SPI	Schedule Performance Index - are you on schedule?
EAC	Estimate at Completion - projected total effort
CV	Cost Variance - budget surplus/deficit

A CPI > 1.0 means you are ahead of estimates. The Dashboard shows EVM health as green/yellow/red.

Task Discovery¶

The plan_check command finds the next ready work package automatically:

Reads all work packages in the project
Checks dependency chains
Returns the first task where all dependencies are met
Claims it for the current session

This means agents can autonomously discover what to work on next.

How It Works¶

For End Users¶

Plan-Master runs as a CLI tool - no server needed for basic operations. When you start a session in a realm, the Master Prompt reads .realm-master/state.json to find ready tasks and begins executing.

For Developers¶

Plan-Master integrates with every realm through the governance file system:

your-realm/
  .realm-master/
    state.json          <- Current project state, next tasks, EVM
    ASSIGNMENTS.md      <- Human-readable task assignments
    WBS.md             <- Full WBS tree
    RISKS.md           <- Active risk register
    ROADMAP.md         <- Project timeline

These files are auto-generated by realm_master command and kept in sync.

Key Commands¶

Command	Purpose
`plan_check --realm <name>`	Find next ready task
`wbs --project <slug>`	View WBS tree
`update_progress --project <slug> --wbs <code>`	Record task completion
`evm --project <slug>`	View EVM health metrics
`decompose --project <slug> --json '[...]'`	Create WBS structure
`project_create --name "..." --realm <name>`	Register new project
`realm_master --project <slug> --file state`	Refresh governance files

All commands work against SQLite via manage.py - no server required.

Common Use Cases¶

Use Case 1: Starting a New Project¶

Register with Plan-Master, decompose into work packages, generate governance files. The realm is now trackable across sessions.

Use Case 2: Autonomous Task Execution¶

Agent runs /master, reads state.json, picks up next ready task, executes via Pipeline-Go TDD cycle, records progress, picks up next task. Fully autonomous.

Use Case 3: Multi-Session Tracking¶

Project spans 10 sessions. Each session reads the WBS, works on the next task, records delta. EVM shows whether you are ahead or behind estimates.

Important Notes¶

Pipeline-Go vs Plan-Master¶

These are SEPARATE systems with DIFFERENT purposes:

System	Purpose	Scope
Pipeline-Go	HOW to write code (patterns, TDD, git)	Per-session
Plan-Master	WHAT to work on (WBS, EVM, critical path)	Cross-session

WBS is the Approval¶

If a work package exists in the WBS with status not_started and its dependencies are met, it is approved for execution. No additional gate is needed.

Pipeline-Go - Provides the methodology for executing tasks
Worker-Bee - Captures session activity for progress tracking
All active realms - Receive governance files from Plan-Master