Technical Writer

Technical Writer — technical document writing pipeline

structuredesign→→diagram→review→versionmanagement 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:

• document week: regarding documentperson
• document type (optional): API//guide//operations
• target reader (optional): role, technical level
• reference material (optional): code, existing document,
• existing file (optional): existing document plan, structureplan

2. _workspace/ Create the directory at the project root
3. Organize input and save to _workspace/00_input.md
4. If existing files are provided, copy them to _workspace/and skip the corresponding Phase
5. Determine the execution mode based on the scope of the request

Phase 2: team composition and execution

task 2a(body text) and 2b(diagram) ** execution**. task 1(structure) only dependency when whenworkto do number .

teamKRW between flow:

• architect complete → writerto table of contents·content strategy, diagramto diagram requirement, versionto data deliver
• writer ↔ diagram: position, caption
• reviewer body text+diagram cross-verification. 🔴 required revision findings when Request revision from the relevant agent -> rework -> re-verify (up to 2 rounds)
• version review result reflectedto final data

Phase 3: integration and final deliverable

1. _workspace/ Verify all files in the directory
2. review reportConfirm that all critical revisions from the review report have been addressed
3. Report the final summary to the user:

• document structure — 01_doc_structure.md
• document body text — 02_doc_draft.md
• diagram — 03_diagrams.md
• review report — 04_review_report.md
• version — 05_version_meta.md

task scaleby mode

existing file utilization: existing document, code, provide applicable stage case existing material basedas task.

data deliver protocol

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

error handling

test scenario

flow

Prompt: " team API documentplease do. target external developmentspecialist, REST API 5items endpoint ." expected result:

• structure: API reference type, external developmentspecialist target reader analysis, endpointby section design
• body text: authentication, endpoint 5items detailed, error code, example code
• diagram: authentication when, process flowchart
• review: technical accuracy·completeness verify
• version: v1.0.0, Published status

existing file utilization flow

Prompt: " document structure existing, body text writingplease do" + structure file department expected result:

• mode: writer + diagram + reviewer deploy
• architect case, existing structure based task

error flow

Prompt: "technical document , week versus whensystem before" expected result:

• scope versus → architect document minute proposal ( overview, API, operations guide etc.)
• reader people → withindepartment developmentspecialist/external developmentspecialist/operationsteam afterreport present
• priority documentdepartment task

agentby extension skill

each agent specialistnature person skill: