Risk Register

Risk Register — project risk managementversus Full pipeline

project risk identification→assessment→response→monitoring→reporting An agent team collaborates to generate all deliverables at once.

execution mode

agent team — 5 agents communicate directly via SendMessage and cross-verify each other's work.

agent composition

workflow

Phase 1: preparation (Orchestrator directly perform)

1. Extract from user input:

• project overview: people, goal, scale, duration
• project type: IT/case/R&D//service etc.
• stakeholder: core stakeholder and expectedmatters
• constraint condition (optional): budget, schedule, technical,
• existing material (optional): existing risk list,

2. _workspace/ Create the directory at the project root
3. Organize input and save to _workspace/00_input.md
4. existing material _workspace/ companyand applicable Phase
5. Determine the execution mode based on the scope of the request

Phase 2: team composition and execution

teamKRW between flow:

• identifier complete → analystto risk list·RBS, strategistto ·dependencynature deliver
• analyst complete → strategistto priority·EMV, plannerto score standard deliver
• strategist complete → plannerto ·natureindicator, writerto response summary deliver
• planner complete → writerto monitoring schedule·KRI deliver
• writer all deliverable cross-verification, dayvalue findings when applicable agent revision request (versus 2)

Phase 3: integration and final deliverable

1. _workspace/ Verify all files in the directory
2. writer consistency verify result reflected
3. Report the final summary to the user

task scaleby mode

data deliver protocol

File naming convention: {}_{agent}_{deliverable}.{extensionspecialist}

error handling

test scenario

flow

Prompt: "6months companywithin ERP whensystem project risk managementversus create it. budget 1000M, teamKRW 15people." expected result:

• identification: RBS 6items category, risk 20~30case, annual risk
• assessment: 5×5 matrix, EMV , Critical 3~5case
• response: Critical avoidance/mitigation, cost- and analysis, residual risk
• monitoring: KRI 10items+, weekbetween/monthbetween review, condition
• report: management 1degree, , Top 5 risk

existing material utilization flow

Prompt: " risk list regarding response strategy establishand report create it" + risk list file expected result:

• existing list _workspace/01_risk_identification.md company
• assessment mode: analyst + strategist + writer deploy
• identifier case

error flow

Prompt: "risk managementversus create it, project basis stage" expected result:

• identifier "[basis stage]" specify after general project risk + basis stage risk derive
• data insufficient → analyst nature assessment duringas task
• report "basis stage — detailed timing re-assessment needed"

agentby extension skill