Knowledge Base Builder — Organizational Knowledge Management Pipeline
An agent team collaborates to execute: knowledge collection, taxonomy design, markdown wiki generation, search indexing, and maintenance guidelines.
Execution Mode
Agent Team — Five agents communicate directly via SendMessage and perform cross-validation.
Agent Composition
| Agent |
File |
Role |
Type |
| knowledge-collector |
.claude/agents/knowledge-collector.md |
Knowledge collection, inventory building |
general-purpose |
| taxonomy-designer |
.claude/agents/taxonomy-designer.md |
Classification system, tags, navigation design |
general-purpose |
| wiki-builder |
.claude/agents/wiki-builder.md |
Markdown wiki page generation |
general-purpose |
| search-optimizer |
.claude/agents/search-optimizer.md |
Search index, metadata optimization |
general-purpose |
| maintenance-planner |
.claude/agents/maintenance-planner.md |
Governance, update cycles, quality management |
general-purpose |
Workflow
Phase 1: Preparation (Performed Directly by Orchestrator)
- Extract from user input:
- Target Organization/Project: What knowledge to manage
- Target Audience: Who will use it
- Existing Documents (optional): Currently available documents, codebase
- Platform Preference (optional): MkDocs, Docusaurus, Notion, GitHub Wiki, etc.
- Create the
_workspace/ directory in the project root
- Organize inputs and save to
_workspace/00_input.md
- If existing documents are available, designate them for analysis
- Determine the execution mode based on the scope of the request
Phase 2: Team Assembly and Execution
| Order |
Task |
Owner |
Dependencies |
Deliverable |
| 1 |
Knowledge Collection |
knowledge-collector |
None |
_workspace/01_knowledge_inventory.md |
| 2 |
Taxonomy Design |
taxonomy-designer |
Task 1 |
_workspace/02_taxonomy.md |
| 3a |
Wiki Page Generation |
wiki-builder |
Tasks 1, 2 |
_workspace/03_wiki/ |
| 3b |
Search Index |
search-optimizer |
Tasks 1, 2 |
_workspace/04_search_index.md (draft) |
| 4 |
Search Index Finalization |
search-optimizer |
Task 3a |
_workspace/04_search_index.md (final) |
| 5 |
Maintenance Guide |
maintenance-planner |
Tasks 1, 2, 3a |
_workspace/05_maintenance_guide.md |
Tasks 3a (wiki generation) and 3b (search index draft) are executed in parallel.
Inter-agent Communication Flow:
- knowledge-collector completes -> Delivers inventory to taxonomy-designer; delivers original content to wiki-builder
- taxonomy-designer completes -> Delivers structure and naming conventions to wiki-builder; delivers tag scheme to search-optimizer
- wiki-builder completes -> Delivers page list to search-optimizer; delivers structure info to maintenance-planner
- maintenance-planner writes guide based on all deliverables
Phase 3: Integration and Final Deliverables
- Review all files in
_workspace/
- Verify no broken links or missing pages in the wiki
- Present the final summary to the user:
- Knowledge Inventory —
01_knowledge_inventory.md
- Taxonomy —
02_taxonomy.md
- Markdown Wiki —
03_wiki/
- Search Index —
04_search_index.md
- Maintenance Guide —
05_maintenance_guide.md
Execution Modes by Request Scope
| User Request Pattern |
Execution Mode |
Deployed Agents |
| "Build a knowledge base," "Create a wiki" |
Full Pipeline |
All 5 agents |
| "Just organize existing docs" |
Organization Mode |
knowledge-collector + taxonomy-designer |
| "Just design the taxonomy" |
Taxonomy Mode |
taxonomy-designer solo |
| "Create wiki pages with this structure" |
Generation Mode |
wiki-builder + search-optimizer |
| "Just write a maintenance guide" |
Guide Mode |
maintenance-planner solo |
Using Existing Files: If existing documents are available, knowledge-collector analyzes them and converts to an inventory.
Data Transfer Protocol
| Strategy |
Method |
Purpose |
| File-based |
_workspace/ directory |
Primary deliverable storage and sharing |
| Message-based |
SendMessage |
Real-time critical information transfer, revision requests |
| Code exploration |
Read/Grep/Glob |
Extract documentation targets from codebase |
Error Handling
| Error Type |
Strategy |
| Source inaccessible |
Infer knowledge based on user description; mark as "inference-based" |
| Excessive knowledge scope |
Propose MVP scope; take a phased approach based on priorities |
| Existing taxonomy conflict |
Respect existing structure while presenting improvement proposals in parallel |
| Agent failure |
Retry once; if still failing, proceed without that deliverable; note omission in report |
| Wiki platform unspecified |
Default to pure Markdown (GitHub/MkDocs compatible) |
Test Scenarios
Normal Flow
Prompt: "Create a wiki for our team's development processes and onboarding docs. We're a 5-developer team using React + Node.js."
Expected Results:
- Knowledge Collection: Inventory of dev processes, environment setup, coding conventions, deployment procedures, etc.
- Taxonomy: Categories such as Getting Started, Development, Deployment, Reference
- Wiki: 10+ pages with YAML front matter and cross-links
- Search Index: JSON format with synonym dictionary
- Maintenance Guide: Governance model and update cycles
Existing Materials Flow
Prompt: "Create a wiki based on these README files" + multiple README files
Expected Results:
- knowledge-collector extracts knowledge from READMEs
- Analyzes existing structure to design taxonomy
- Converts to markdown wiki, preserving original content
Error Flow
Prompt: "Build a company knowledge base"
Expected Results:
- Scope is broad, so knowledge-collector suggests domain scoping questions
- Proposes MVP based on typical corporate knowledge structure template
- Maintenance guide includes "phased expansion roadmap"
Agent Extension Skills
Extension skills that enhance each agent's domain expertise:
| Agent |
Extension Skill |
Role |
| taxonomy-designer |
information-architecture |
4 IA systems, card sorting, sitemap design, tag governance |
| maintenance-planner, wiki-builder |
content-lifecycle-manager |
5-stage lifecycle, quality scorecard, RACI governance, content auditing |
1---2name: knowledge-base-builder3description: A pipeline where an agent team builds organizational knowledge management systems. Use this skill for requests such as 'build a knowledge base,' 'wiki setup,' 'knowledge management system,' 'internal wiki,' 'organize team documentation,' 'technical documentation wiki,' 'create onboarding docs,' 'organize organizational knowledge,' or 'build documentation system.' Note: CMS server setup, database installation, and search engine deployment are outside the scope of this skill.4---56# Knowledge Base Builder — Organizational Knowledge Management Pipeline78An agent team collaborates to execute: knowledge collection, taxonomy design, markdown wiki generation, search indexing, and maintenance guidelines.910## Execution Mode1112**Agent Team** — Five agents communicate directly via SendMessage and perform cross-validation.1314## Agent Composition1516| Agent | File | Role | Type |17|-------|------|------|------|18| knowledge-collector | `.claude/agents/knowledge-collector.md` | Knowledge collection, inventory building | general-purpose |19| taxonomy-designer | `.claude/agents/taxonomy-designer.md` | Classification system, tags, navigation design | general-purpose |20| wiki-builder | `.claude/agents/wiki-builder.md` | Markdown wiki page generation | general-purpose |21| search-optimizer | `.claude/agents/search-optimizer.md` | Search index, metadata optimization | general-purpose |22| maintenance-planner | `.claude/agents/maintenance-planner.md` | Governance, update cycles, quality management | general-purpose |2324## Workflow2526### Phase 1: Preparation (Performed Directly by Orchestrator)27281. Extract from user input:29 - **Target Organization/Project**: What knowledge to manage30 - **Target Audience**: Who will use it31 - **Existing Documents** (optional): Currently available documents, codebase32 - **Platform Preference** (optional): MkDocs, Docusaurus, Notion, GitHub Wiki, etc.332. Create the `_workspace/` directory in the project root343. Organize inputs and save to `_workspace/00_input.md`354. If existing documents are available, designate them for analysis365. Determine the **execution mode** based on the scope of the request3738### Phase 2: Team Assembly and Execution3940| Order | Task | Owner | Dependencies | Deliverable |41|-------|------|-------|-------------|-------------|42| 1 | Knowledge Collection | knowledge-collector | None | `_workspace/01_knowledge_inventory.md` |43| 2 | Taxonomy Design | taxonomy-designer | Task 1 | `_workspace/02_taxonomy.md` |44| 3a | Wiki Page Generation | wiki-builder | Tasks 1, 2 | `_workspace/03_wiki/` |45| 3b | Search Index | search-optimizer | Tasks 1, 2 | `_workspace/04_search_index.md` (draft) |46| 4 | Search Index Finalization | search-optimizer | Task 3a | `_workspace/04_search_index.md` (final) |47| 5 | Maintenance Guide | maintenance-planner | Tasks 1, 2, 3a | `_workspace/05_maintenance_guide.md` |4849Tasks 3a (wiki generation) and 3b (search index draft) are executed **in parallel**.5051**Inter-agent Communication Flow:**52- knowledge-collector completes -> Delivers inventory to taxonomy-designer; delivers original content to wiki-builder53- taxonomy-designer completes -> Delivers structure and naming conventions to wiki-builder; delivers tag scheme to search-optimizer54- wiki-builder completes -> Delivers page list to search-optimizer; delivers structure info to maintenance-planner55- maintenance-planner writes guide based on all deliverables5657### Phase 3: Integration and Final Deliverables58591. Review all files in `_workspace/`602. Verify no broken links or missing pages in the wiki613. Present the final summary to the user:62 - Knowledge Inventory — `01_knowledge_inventory.md`63 - Taxonomy — `02_taxonomy.md`64 - Markdown Wiki — `03_wiki/`65 - Search Index — `04_search_index.md`66 - Maintenance Guide — `05_maintenance_guide.md`6768## Execution Modes by Request Scope6970| User Request Pattern | Execution Mode | Deployed Agents |71|---------------------|---------------|-----------------|72| "Build a knowledge base," "Create a wiki" | **Full Pipeline** | All 5 agents |73| "Just organize existing docs" | **Organization Mode** | knowledge-collector + taxonomy-designer |74| "Just design the taxonomy" | **Taxonomy Mode** | taxonomy-designer solo |75| "Create wiki pages with this structure" | **Generation Mode** | wiki-builder + search-optimizer |76| "Just write a maintenance guide" | **Guide Mode** | maintenance-planner solo |7778**Using Existing Files**: If existing documents are available, knowledge-collector analyzes them and converts to an inventory.7980## Data Transfer Protocol8182| Strategy | Method | Purpose |83|----------|--------|---------|84| File-based | `_workspace/` directory | Primary deliverable storage and sharing |85| Message-based | SendMessage | Real-time critical information transfer, revision requests |86| Code exploration | Read/Grep/Glob | Extract documentation targets from codebase |8788## Error Handling8990| Error Type | Strategy |91|-----------|----------|92| Source inaccessible | Infer knowledge based on user description; mark as "inference-based" |93| Excessive knowledge scope | Propose MVP scope; take a phased approach based on priorities |94| Existing taxonomy conflict | Respect existing structure while presenting improvement proposals in parallel |95| Agent failure | Retry once; if still failing, proceed without that deliverable; note omission in report |96| Wiki platform unspecified | Default to pure Markdown (GitHub/MkDocs compatible) |9798## Test Scenarios99100### Normal Flow101**Prompt**: "Create a wiki for our team's development processes and onboarding docs. We're a 5-developer team using React + Node.js."102**Expected Results**:103- Knowledge Collection: Inventory of dev processes, environment setup, coding conventions, deployment procedures, etc.104- Taxonomy: Categories such as Getting Started, Development, Deployment, Reference105- Wiki: 10+ pages with YAML front matter and cross-links106- Search Index: JSON format with synonym dictionary107- Maintenance Guide: Governance model and update cycles108109### Existing Materials Flow110**Prompt**: "Create a wiki based on these README files" + multiple README files111**Expected Results**:112- knowledge-collector extracts knowledge from READMEs113- Analyzes existing structure to design taxonomy114- Converts to markdown wiki, preserving original content115116### Error Flow117**Prompt**: "Build a company knowledge base"118**Expected Results**:119- Scope is broad, so knowledge-collector suggests domain scoping questions120- Proposes MVP based on typical corporate knowledge structure template121- Maintenance guide includes "phased expansion roadmap"122123## Agent Extension Skills124125Extension skills that enhance each agent's domain expertise:126127| Agent | Extension Skill | Role |128|-------|----------------|------|129| taxonomy-designer | `information-architecture` | 4 IA systems, card sorting, sitemap design, tag governance |130| maintenance-planner, wiki-builder | `content-lifecycle-manager` | 5-stage lifecycle, quality scorecard, RACI governance, content auditing |
revfactory