Crisis Communication

Crisis Communication — crisis Full pipeline

crisis situation situationidentify→messagestrategy→press release→Q&A→monitoring 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:

• crisis situation: day occurrence
• ** information**: people, scale,
• current status: press coverage department, withindepartment persondegree timing, initial response department
• constraint condition (optional): legal issue, matters, time constraint
• existing document (optional): existing press release, withindepartment report etc.

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

Phase 2: team composition and execution

team compositionand task to do. task between dependency total next and :

task 3a(press release) and 3b(Q&A) ** execution**. task 2(messagestrategy) only dependency when whenworkto do number .

teamKRW between flow:

• analyst complete → strategistto crisisetc.grade·stakeholder· deliver
• strategist complete → writerto coremessage·tone·No-Go Phrases deliver, preparerto stakeholderby message deliver
• writer complete → preparerto official documentplan deliver (Q&A consistency secure)
• preparer complete → monitorto expected question pattern deliver
• monitor all deliverable cross-verificationto message consistency, scenario, inspection

Phase 3: integration and final deliverable

verify result basedas final deliverable organization:

1. _workspace/ Verify all files in the directory
2. message consistency issue findings applicable agent revision request (versus 2)
3. Report the final summary to the user:

• situation analysis report — 01_situation_analysis.md
• message strategyfrom — 02_message_strategy.md
• press release/document — 03_press_release.md
• Q&A when — 04_qa_briefing.md
• monitoring plan — 05_monitoring_plan.md

task scaleby mode

user request scope according to deploy agent :

existing file utilization: user existing press release, withindepartment report etc. provide, applicable file _workspace/ qualityKorean position companyand applicable stage case.

data deliver protocol

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

error handling

test scenario

flow

Prompt: " company from client itemspersoninformation 5 only case . press coverage before withindepartmentfrom 30minute before findings. crisis response communication overall preparationplease do." expected result:

• situation analysis: data crisisetc.grade Critical , itemspersoninformationreport risk, stakeholder 6items or more
• message strategy: 3C core message, response, No-Go Phrases 5items or more
• press release: + press release + CEO fromKorean
• Q&A: categoryby expected question 20items or more, question response
• monitoring: channelby , standard, crisis judgment standard

departmentminute request flow

Prompt: "withinday basisspecialistperson Q&A only grade preparationplease do. situation ." expected result:

• Q&A mode beforeexchange (analyst + strategist + preparer)
• question (planbeforenature, report, scope, cause, re-degree)
• versusperson 1-degree + degree document

error flow

Prompt: "crisis response preparationplease do, situation SNSfrom " expected result:

• analyst "[information limitation]" specify after SNS crisis type scenario 3items present
• each scenarioby core message preparation
• i.e.when provide

agentby extension skill