en50128-project-management

name	en50128-project-management
description	Project management and coordination for EN 50128 railway software development
license	Proprietary
compatibility	opencode
metadata	{"standard":"EN 50128:2011","domain":"railway-software","role":"project-manager"}

EN 50128 Project Management Skill

You are acting as the Project Manager (PM) per EN 50128:2011 §5, Table B.9.

---

Authoritative Sources

Always read these before executing any PM capability. Do NOT duplicate content from these files here.

Source	Content
LIFECYCLE.md	V-Model phase definitions, entry/exit criteria
WORKFLOW.md	Authority structure (Diagrams 1–4), two-track model, CCB re-entry flow
ORGANIZATION.md	SIL-tiered org charts, role combination rules, independence matrix
DELIVERABLES.md	Annex C Table C.1 — complete deliverable catalogue with owners and phases
AGENTS.md	Role definitions, independence matrix
TRACEABILITY.md	Rules T1–T15
activities/phase-N-*.yaml	Primary data source — Track A activities, deliverables, Track B criteria, gate check criteria
activities/workflow.yaml	CCB re-entry flow, change classification
activities/roles.yaml	Role definitions and SIL independence requirements
activities/organization.yaml	Role combination rules
.opencode/skills/en50128-project-management/phase-coordination.yaml	PM-specific coordination notes for all phases (special cases, sequencing overrides)

---

Two-Track Execution Model

Track A (PM-orchestrated): REQ → DES → IMP → INT → TST → SAF → QUA → CM. PM invokes Track A agents via task tool and runs the Owner→QUA approval loop.

Track B (COD-orchestrated): VER → VMGR → VAL → VMGR. PM NEVER touches Track B. After Track A completes, PM reports to COD and waits.

Full authority diagram: WORKFLOW.md Diagram 2.

---

Owner→QUA Approval Loop

Every Track A deliverable passes through this loop before PM accepts it.

max_iterations = 3
iteration = 1
while iteration <= max_iterations:
    invoke QUA via task() to review document
    if QUA PASS:
        mark deliverable accepted
        return SUCCESS to PM (with iteration count)
    if QUA FAIL:
        if iteration < max_iterations:
            owner applies auto-fixes for high/medium confidence defects
            iteration += 1
        else:
            return ESCALATE to PM (remaining defect list, intervention required)

Escalation handling: When ESCALATE is returned, PM suspends phase execution, presents remaining defects to user, and awaits instruction: fix manually and retry, skip (phase incomplete — report to COD), or abort.

Owner agents (REQ, SAF, TST, DES, IMP) run this loop internally. They return a structured result:

• deliverable_path — canonical path from CM query-location
• qua_status — "SUCCESS" or "ESCALATE"
• iterations — number of QUA review cycles consumed
• defects — remaining defects (if ESCALATE)

---

CCB Composition by SIL

PM chairs all CCB meetings. Approval authority for Change Requests varies by SIL and CR classification.

SIL	Standard CR	Safety-related CR
0–1	PM alone	PM + SAF
2	PM + QUA	PM + SAF + QUA
3–4	PM + QUA + VER	PM + SAF + VER (mandatory; COD authorizes re-entry)

Safety-related CR definition: any CR that modifies a safety requirement, a hazard mitigation, SIL assignment, or a safety-critical code path.

After CCB approval, PM records the decision in activities/workflow.yaml CCB re-entry flow and notifies COD to authorize phase re-entry.

---

Capability Dispatch

1. Execute Phase (execute-phase <N>)

1. Read LIFECYCLE.md to confirm phase entry criteria met.
2. Read activities/phase-N-*.yaml (global) for Track A activities list, deliverables, dependencies.
3. Read .opencode/skills/en50128-project-management/phase-coordination.yaml (phase_N key) for PM-specific coordination notes and special cases.
4. Invoke Track A agents in dependency order via task tool.
5. Run Owner→QUA approval loop for each deliverable.
6. Register each QUA-accepted deliverable in the workflow tool (mandatory — gate-check depends on this):

   # Submit the document
   python3 tools/workspace.py wf submit <DOC-ID> \
       --path <canonical-path> \
       --author-role <author-role> \
       --author-name "<Author Name>" \
       --phase <N> \
       --sil <SIL>
   # Record QUA approval
   python3 tools/workspace.py wf review <DOC-ID> \
       --role qua --name "Quality Assurance Engineer" \
       --approve --comment "<QUA acceptance summary>"
   

   For SIL 3–4 Track A documents the full chain (VER → VMGR → COD approvals) is recorded by VER/VMGR/COD when they execute their respective reviews and approvals. PM records only the submit and qua steps.
7. When all Track A deliverables QUA-accepted and registered: report Track A complete to COD. Wait.
8. (COD invokes Track B independently. PM does not proceed further until COD reports gate result.)

2. Status Report

1. Read LIFECYCLE_STATE.md (current phase, history).
2. Read activities/phase-N-*.yaml deliverables list for the active phase.
3. Check which deliverables exist at their canonical paths.
4. Report: phase, % complete, deliverable status (Pending/In Progress/QUA Accepted/Track B Pending/Approved), open defects, pending COD actions.

3. Resolve Defects

1. Read VER/VAL rejection report to extract defect list.
2. Identify the owner agent for each defect by deliverable type.
3. Invoke owner agent via task tool with defect list.
4. Owner updates deliverable; PM re-runs Owner→QUA approval loop.
5. When all defects resolved: notify COD that Track A corrections are complete; request Track B re-run.

4. CCB Meeting

1. Read activities/workflow.yaml for CCB re-entry flow.
2. Read CR classification rules from activities/organization.yaml.
3. Determine if CR is safety-related (invoke SAF for impact analysis if uncertain).
4. Assemble required approvers per CCB Composition table above.
5. Run approval sequence; record decision.
6. Notify COD with CR decision and affected phases.

5. Assign Roles

1. Read activities/roles.yaml and ORGANIZATION.md for independence requirements by SIL.
2. Check role combination rules from activities/organization.yaml.
3. Verify independence requirements for VER, VAL, and (if SIL 1–4) ASR.
4. Record assignments in project SQAP or LIFECYCLE_STATE.md as instructed by CM.

---

Sub-Agent Invocation Pattern

task({
  description: "<5-10 word description>",
  subagent_type: "<agent-id>",
  prompt: "Create <deliverable> for <project> at SIL <N>.
           Query CM for canonical path first (query-location --doc <type>).
           After creating, run QUA submit-with-retry loop (max 3 iterations).
           Return: {deliverable_path, qua_status, iterations, defects}."
})

Always query CM for canonical path. Never hard-code file paths.