pm-orchestration

name	pm-orchestration
description	Orchestrate PM-Agent workflows for case management, task delegation, and artifact pipeline coordination within sea-domain-forge. Use when managing multi-step projects, delegating tasks to sub-agents, tracking work through CMMN stages, or reporting progress across cases. Integrates with case-management, cognitive-artifacts, and internal-comms skills.

PM-Agent Orchestration

Coordinate project work through PM-Agent — the orchestration layer for case management, task delegation, and artifact pipelines.

No-Technical-Debt Rule

This skill forbids placeholders of any kind:

• No TODO/FIXME/XXX/HACK/STUB markers
• No stubs, mocks-as-implementations, or empty handlers
• No raise NotImplementedError / throw new Error("not implemented")
• No pass or placeholder logic

If an issue blocks progress, present the user with explicit options and a recommendation.

When to Use This Skill

1. Managing Complex Projects: Work spanning multiple phases, teams, or dependencies
2. Delegating to Sub-Agents: Breaking work into tasks for specialized agents
3. Tracking Artifact Pipelines: Moving artifacts through CMMN stages
4. Coordinating Handoffs: Ensuring smooth transitions between stages
5. Reporting Progress: Generating status updates across cases

PM-Agent Architecture

┌─────────────────────────────────────────────────────────────┐
│                        PM-Agent                              │
│  ┌─────────────┐  ┌──────────────┐  ┌────────────────────┐  │
│  │ Case Manager │  │ Task Router  │  │ Artifact Pipeline  │  │
│  └─────────────┘  └──────────────┘  └────────────────────┘  │
│          │                │                    │             │
│          ▼                ▼                    ▼             │
│  ┌─────────────┐  ┌──────────────┐  ┌────────────────────┐  │
│  │   NATS Bus   │◄─┤ Sub-Agents   │  │ Knowledge Graph    │  │
│  └─────────────┘  └──────────────┘  └────────────────────┘  │
└─────────────────────────────────────────────────────────────┘

Core Workflows

1. Case Creation

command: pm.case.create
payload:
  title: "<Project Name>"
  description: "<Brief summary>"
  desiredOutcome: "<Specific, measurable outcome>"
  timeline:
    startDate: "<ISO 8601>"
    targetDate: "<ISO 8601>"
  semanticRefs:
    - conceptId: "sea:KnowledgeWork"

2. Task Breakdown

Decompose a case into delegatable tasks:

command: pm.task.plan
payload:
  caseId: "<case-id>"
  breakdown:
    strategy: "vertical-slice"   # or "horizontal", "milestone"
    maxParallelism: 3

Quality guidelines for tasks:

• Each task must have a single, unambiguous name
• Tasks must be atomic (one verifiable unit of work)
• Success criteria must be measurable:

  successCriteria:
    - metric: "tests_passing"
      threshold: 100
      unit: "percent"
    - metric: "lint_errors"
      threshold: 0
      unit: "count"
  

3. Task Delegation

Route tasks to the most capable available agent:

Agent	Specialization
code-agent	Code generation, refactoring
review-agent	Code review, PR analysis
test-agent	Test generation, verification
doc-agent	Documentation, handbooks
research-agent	Codebase exploration, analysis
human	Architecture decisions, sovereign approval

command: pm.task.delegate
payload:
  taskId: "<task-id>"
  agent: "<agent-type>"
  context:
    files:
      - "<specific file path>"    # Minimum required context only — no wildcards
    instructions: "<Precise instruction>"
    successCriteria:
      - "<Measurable criterion>"

4. Progress Tracking

command: pm.case.status
payload:
  caseId: "<case-id>"

Present as:

• Completed / In Progress / Pending / Total
• % complete
• On-track vs. at-risk flag
• Active blockers list

Pair with a CADSL Kanban artifact for visual status by invoking cognitive-artifacts.

5. Artifact Pipeline Advancement

command: pm.artifact.advance
payload:
  artifactId: "<artifact-id>"
  fromStage: "<current stage>"
  toStage: "<target stage>"
  reviewer: "human"     # or "agent", "automated"

Artifact stages:

draft → review → approved → published → archived
                     ↓
              rejected → draft (revision)

No Teleportation Policy: Artifacts cannot skip stages. If the user asks to skip a stage, present the required intermediate stages and ask which to use.

Execution Patterns

Sequential

execution:
  strategy: "sequential"
  tasks: ["task-001", "task-002", "task-003"]

Parallel

execution:
  strategy: "parallel"
  maxConcurrency: 3
  tasks: ["task-001", "task-002", "task-003"]

DAG (Dependency Graph)

execution:
  strategy: "dag"
  tasks:
    - id: "task-001"
      dependencies: []
    - id: "task-002"
      dependencies: []
    - id: "task-003"
      dependencies: ["task-001", "task-002"]

NATS Event Integration

PM-Agent publishes events for observability:

# Case created
subject: "sea.pm.case.created"
payload:
  caseId: "<case-id>"
  timestamp: "<ISO 8601>"

# Task completed
subject: "sea.pm.task.completed"
payload:
  taskId: "<task-id>"
  caseId: "<case-id>"
  duration: "PT2H30M"
  result: "success"

# Stage transition
subject: "sea.pm.artifact.stage.changed"
payload:
  artifactId: "<artifact-id>"
  from: "draft"
  to: "review"

Integration with Other Plugin Skills

Skill	When
case-management	Source of case definitions and sentry conditions
cognitive-artifacts	Generate Kanban for visual progress; Checklist for completion tracking
internal-comms	After major milestones: offer 3P update or announcement

Reporting

After significant milestones, offer to generate internal communications:

• Stage completed → 3P update
• Case closed → project closure announcement
• Blocker detected → incident report
• On-track check → status report

Invoke internal-comms skill to produce the communication.