Skip to main content

Critical Path Management

Critical Path Management Skill

Comprehensive critical path management for CODITECT deployment milestones. Registers tasks, tracks dependencies, inventories progress, and coordinates execution.

When to Use

  • Planning launches: When identifying which tasks must complete before deployment
  • Tracking blockers: When understanding what's blocking a milestone
  • Coordinating work: When multiple tracks (A/B/C/D/E/F) have interdependencies
  • Progress reporting: When generating status updates for stakeholders

Usage

# Show current critical path status
/critical-path status

# Register a new critical path
/critical-path register "Cloud Workstation Launch"

# Add tasks to critical path
/critical-path add A.10.1.1 A.10.1.2 C.5.1 --path "Cloud Workstation Launch"

# Show dependency chain
/critical-path deps A.10.2.1

# Execute next task in path
/critical-path next

# Mark task complete
/critical-path done A.10.1.1

# Generate report
/critical-path report --format markdown

Actions

ActionDescription
statusShow all critical paths and progress
registerCreate a new named critical path
addAdd tasks to a critical path
removeRemove tasks from a critical path
depsShow dependency chain for a task
nextGet next actionable task
doneMark task complete
blockMark task blocked with reason
unblockRemove blocker from task
reportGenerate progress report
inventoryFull inventory of all critical path items

Current Critical Paths

Cloud Workstation Launch (Active)

Goal: Enable paying customers to access Cloud Workstations with valid licenses

Dependency Chain:

Registration → Payment → License → Container Session → Workstation Access
↓ ↓ ↓ ↓ ↓
B.2 A.3/B.3 A.4 A.10/C.5 A.7/C.7

Phase 1: Core Infrastructure (COMPLETE)

TaskDescriptionStatus
A.3.*Commerce API✅ 100%
B.3.*Commerce UI✅ 90%
D.1-D.3Security✅ 100%
C.1-C.4GKE deployment✅ 100%

Phase 2: Auth & Registration (85%)

TaskDescriptionStatusBlocked By
B.2.1Signup page-
B.2.2Email verification-
B.2.3Login with JWT~60%-
B.2.5Auth context~60%-
A.4.10JWT tenant_id claims-

Phase 3: Container Sessions (0% - CRITICAL)

TaskDescriptionStatusBlocked By
A.10.1.1Create sessions app-
A.10.1.2ContainerSession modelA.10.1.1
A.10.1.3ContainerUserSession modelA.10.1.1
A.10.2.1POST /sessions/validateA.10.1.2
A.10.2.2Docker validation flowA.10.2.1
A.10.2.3Workstation JWT validationA.10.2.1
A.10.3.1POST /sessions/heartbeatA.10.2.1
A.10.4.1POST /sessions/releaseA.10.2.1
A.10.4.3License expiration webhookA.10.4.1

Phase 4: Docker Registry (0% - CRITICAL)

TaskDescriptionStatusBlocked By
C.5.1GCP Artifact Registry-
C.5.2Pull token generation APIC.5.1, A.10.2.1
C.5.3Dashboard token UIC.5.2
C.5.4Token revocationC.5.2

Phase 5: Workstation Provisioning (0%)

TaskDescriptionStatusBlocked By
A.7.1Workstations Django appA.10.2.1
A.7.2GCP Workstations APIA.7.1
A.7.3WorkstationInstance modelA.7.1
A.7.4Stripe webhook triggerA.7.2
C.7.1-6Workstation entrypointsA.10.2.1

Phase 6: Frontend UX (70%)

TaskDescriptionStatusBlocked By
B.3.4.2-4Entitlement displayA.10.2.1
B.4.4Device session UIA.10.2.1
B.4.5Container session UIA.10.2.1
B.4.6Billing portal link-

Execution Order

Recommended sequence (critical path):

A.10.1.1 → A.10.1.2 → A.10.1.3 → A.10.2.1 → C.5.1 → C.5.2 → A.7.1 → A.7.4
| | | | | | |
Sessions Session User Validate Registry Tokens Workstations
App Model Session API

Total Critical Path Tasks: 27 Estimated Completion: 18-24 hours parallel execution

Agent Assignments

PhasePrimary AgentSupporting
Phase 2frontend-react-typescript-expertsenior-architect
Phase 3senior-architectdatabase-architect
Phase 4devops-engineersenior-architect
Phase 5senior-architectdevops-engineer
Phase 6frontend-react-typescript-expert-

Storage

Critical path data stored in:

  • context-storage/critical-paths.json - Path definitions
  • PILOT-PARALLEL-EXECUTION-PLAN.md - Task details (SSOT)

Integration

Works with:

  • /orient - Session orientation includes critical path status
  • /which - Agent recommendations for critical path tasks
  • TodoWrite - Task tracking syncs to critical path

Success Output

✅ SKILL COMPLETE: /critical-path status

Cloud Workstation Launch
========================
Progress: 58% (16/27 tasks)
Phase: 3 - Container Sessions
Next Task: A.10.1.1 (Create sessions Django app)
Blockers: None
Est. Completion: 18 hours

Agent: senior-architect
Invocation: Task(subagent_type="senior-architect",
prompt="A.10.1.1: Create sessions Django app in coditect-cloud-infra/backend/")

Completion Checklist

  • Critical path registered
  • All tasks inventoried
  • Dependencies mapped
  • Agent assignments complete
  • Progress tracking active

Failure Indicators

  • ❌ Circular dependency detected
  • ❌ Task not in PILOT plan
  • ❌ Invalid task ID format
  • ❌ Missing dependency

When NOT to Use

Do NOT use when:

  • Single task with no dependencies (just execute it)
  • Non-blocking exploratory work (use regular task tracking)
  • Research or documentation tasks (not deployment-critical)
  • Tasks that can run in any order (no path needed)

Anti-Patterns (Avoid)

Anti-PatternProblemSolution
Everything is criticalDilutes focusLimit to launch-blocking tasks
Skipping dependency mappingHidden blockersAlways map deps before execution
Not updating statusStale dataMark done immediately
Parallel execution of dependent tasksRace conditionsFollow execution order
Ignoring agent assignmentsSuboptimal executionUse recommended agents

Principles

This skill embodies:

  • #3 Complete Execution - Track to completion
  • #4 Separation of Concerns - Clear phase boundaries
  • #9 Based on Facts - Data from PILOT plan (SSOT)

Version: 1.0.0 Created: 2026-01-05 Author: CODITECT Team