Generate Documentation Suite

You are orchestrating a multi-phase documentation generation workflow. Follow these phases exactly:

Phase 1: Parallel Analysis

Launch TWO agents IN PARALLEL using the Task tool:

1. doc-generator:doc-discovery - Discovers existing documentation patterns, conventions, and terminology in the codebase
2. doc-generator:architecture-analyzer - Analyzes code structure, dependencies, and module relationships

Use a SINGLE message with TWO Task tool calls to run these in parallel. Wait for both to complete before proceeding.

Prompt for doc-discovery agent:

Analyze this codebase to discover existing documentation patterns. Report on:
- Existing doc formats (README style, docstrings, comments)
- Naming conventions used
- Domain terminology
- Any existing templates or style guides

Output a structured discovery report that the technical writer can use.

Prompt for architecture-analyzer agent:

Analyze this codebase architecture. Report on:
- Module/package structure and relationships
- Key dependencies and how they connect
- Entry points and main flows
- Public API surface
- Core abstractions and patterns

Output a structured architecture analysis that the technical writer can use.

Phase 2: Technical Writing

After BOTH phase 1 agents complete, launch the doc-generator:technical-writer agent.

Pass it the outputs from BOTH phase 1 agents in the prompt:

Prompt for technical-writer agent:

Using the discovery report and architecture analysis below, generate comprehensive documentation.

## Discovery Report
[Insert doc-discovery output here]

## Architecture Analysis
[Insert architecture-analyzer output here]

Generate these documents in the ./docs/ folder:
1. api-reference.md - API/function documentation
2. architecture.md - System architecture overview
3. getting-started.md - Quick start guide

Also create Confluence wiki markup versions in ./docs/confluence/

Phase 3: Quality Gate

After the technical writer completes, launch the doc-generator:english-editor agent.

Prompt for english-editor agent:

Review the documentation in ./docs/ for quality:

1. Readability - Is the language clear and concise?
2. Style consistency - Is formatting and tone consistent?
3. Code-docs alignment - Do the docs accurately reflect the actual code?
4. Confluence compatibility - Is the wiki markup valid?
5. Completeness - Are there any missing sections?

If issues are found, fix them directly. Report what was validated and what was corrected.

Final Output

After all phases complete, summarize:

• What documentation was generated
• Key findings from discovery and architecture analysis
• Any quality issues that were corrected
• Location of output files (./docs/)

Inform the user they can now copy the ./docs/confluence/*.wiki files directly into Confluence.