\r \r

DoDAF Skill\r

\r

What This Skill Does\r

\r This skill creates DoDAF-compliant architecture descriptions for defense and military systems. It guides users through a structured, professional workflow:\r \r

1. Step-by-Step Interview: Asks clear questions to gather requirements from users who may not know DoDAF terminology\r
2. Automatic Data Collection: Searches for defense standards, doctrine, and best practices when information is insufficient\r
3. Professional View Generation: Creates all required DoDAF views following official standards\r
4. Completeness Verification: Ensures all mandatory views and elements are present\r
5. Consistency Checking: Validates cross-view relationships and naming conventions\r
6. Consolidated Report: Merges all views, diagrams, and matrices into a single well-structured PDF/Word document\r
7. Reviewable Report: Delivers comprehensive documentation with findings and recommendations\r \r ---\r \r

Complete DoDAF Workflow\r

\r

Phase 1: Stakeholder & Context Interview\r

\r Goal: Understand the system purpose and stakeholders\r \r Guided Questions:\r

• "What is the main mission or purpose of this system?"\r
• "Who are the key users or organizations that will use this system?"\r
• "What are the operational environments (land, sea, air, space, cyber)?"\r
• "Are there any security classification requirements?"\r
• "What are the key constraints (budget, timeline, technology)?"\r \r Automatic Data Collection:\r
• Search for relevant defense doctrine (e.g., Joint Publication 3-0)\r
• Gather service-specific requirements (Army, Navy, Air Force, Marines)\r
• Collect industry best practices for similar systems\r \r Output Artifacts:\r
• docs/01-stakeholder-context.md - Stakeholder analysis document\r
• diagrams/AV-1-overview.drawio - AV-1 Overview and Summary Information\r \r ---\r \r

Phase 2: Operational Analysis\r

\r Goal: Define operational concepts and activities\r \r Guided Questions:\r

• "What are the main operational scenarios?"\r
• "Who are the external actors (friendly, neutral, adversary)?"\r
• "What information needs to be exchanged between entities?"\r
• "What are the key operational tasks?"\r \r Generated Products:\r
• OV-1: High-Level Operational Concept Graphic\r
• OV-2: Operational Resource Flow Description\r
• OV-3: Operational Information Exchange Matrix\r
• OV-5: Activity Model\r \r Output Artifacts:\r
• docs/02-operational-analysis.md - Operational analysis document\r
• diagrams/OV-1-operational-concept.drawio - OV-1 diagram\r
• diagrams/OV-2-resource-flow.drawio - OV-2 diagram\r
• docs/OV-3-information-exchange-matrix.md - OV-3 matrix\r
• diagrams/OV-5-activity-model.drawio - OV-5 diagram\r \r Completeness Checks:\r
• All operational scenarios are identified\r
• All external actors are defined\r
• Information flows are bidirectional where needed\r
• Activity decomposition is at appropriate level\r \r Consistency Checks:\r
• Actor names are consistent across all views\r
• Information flow sources/destinations match actors\r
• Activity names align with operational tasks\r \r ---\r \r

Phase 3: Capability Definition\r

\r Goal: Define required capabilities and dependencies\r \r Guided Questions:\r

• "What capabilities does the system need to provide?"\r
• "Which capabilities depend on others?"\r
• "What is the timeline for capability delivery?"\r \r Generated Products:\r
• CV-1: Capability Taxonomy\r
• CV-2: Capability Phasing\r
• CV-3: Capability Dependencies\r \r Output Artifacts:\r
• docs/03-capability-definition.md - Capability definition document\r
• diagrams/CV-1-capability-taxonomy.drawio - CV-1 diagram\r
• diagrams/CV-2-capability-phasing.drawio - CV-2 diagram\r
• diagrams/CV-3-capability-dependencies.drawio - CV-3 diagram\r \r Completeness Checks:\r
• All operational needs map to capabilities\r
• Capability hierarchy is complete\r
• Dependencies are identified for all capabilities\r
• Phasing is defined for each capability\r \r Consistency Checks:\r
• Capability names match across all views\r
• Dependencies form valid chains (no cycles)\r
• Phasing aligns with project timeline\r \r ---\r \r

Phase 4: System Design\r

\r Goal: Define system functions and interfaces\r \r Guided Questions:\r

• "What functions must the system perform?"\r
• "What are the major system components?"\r
• "How do components communicate?"\r \r Generated Products:\r
• SV-1: Systems Interface Description\r
• SV-2: Systems Communication Description\r
• SV-4: Systems Functionality Description\r
• SV-5: Operational Activity to Systems Function Traceability\r \r Output Artifacts:\r
• docs/04-system-design.md - System design document\r
• diagrams/SV-1-systems-interface.drawio - SV-1 diagram\r
• diagrams/SV-2-systems-communication.drawio - SV-2 diagram\r
• diagrams/SV-4-systems-functionality.drawio - SV-4 diagram\r
• docs/SV-5-traceability-matrix.md - SV-5 matrix\r \r Completeness Checks:\r
• All capabilities are realized by system functions\r
• All interfaces are defined\r
• Function decomposition is complete\r
• Traceability matrix is populated\r \r Consistency Checks:\r
• System function names align with capabilities\r
• Interface names match data exchange definitions\r
• Traceability links are bidirectional\r
• No orphan functions (unconnected to capabilities)\r \r ---\r \r

Phase 5: Data Architecture\r

\r Goal: Define data models and information exchanges\r \r Guided Questions:\r

• "What data needs to be stored and processed?"\r
• "What are the data formats and standards?"\r
• "How is data exchanged between systems?"\r \r Generated Products:\r
• DIV-1: Data Model Description\r
• DIV-2: Data Dictionary\r
• DIV-3: Data Exchange Matrix\r \r Output Artifacts:\r
• docs/05-data-architecture.md - Data architecture document\r
• diagrams/DIV-1-data-model.drawio - DIV-1 diagram\r
• docs/DIV-2-data-dictionary.md - DIV-2 dictionary\r
• docs/DIV-3-data-exchange-matrix.md - DIV-3 matrix\r \r Completeness Checks:\r
• All data elements are defined\r
• Data relationships are specified\r
• Exchange formats are identified\r
• Data ownership is assigned\r \r Consistency Checks:\r
• Data element names are consistent\r
• Data flows match system interfaces\r
• Data types are correctly defined\r \r ---\r \r

Phase 6: Technical Architecture\r

\r Goal: Define technology standards and infrastructure\r \r Guided Questions:\r

• "What technologies will be used?"\r
• "What standards must be followed?"\r
• "What are the security requirements?"\r \r Generated Products:\r
• TV-1: Technical Standards Profile\r
• TV-2: Technical Measures\r
• TV-3: Technical Architecture Framework\r \r Output Artifacts:\r
• docs/06-technical-architecture.md - Technical architecture document\r
• docs/TV-1-technical-standards.md - TV-1 standards\r
• docs/TV-2-technical-measures.md - TV-2 measures\r
• diagrams/TV-3-technical-framework.drawio - TV-3 diagram\r \r Completeness Checks:\r
• All technology standards are identified\r
• Security controls are defined\r
• Performance requirements are specified\r
• Compliance requirements are addressed\r \r Consistency Checks:\r
• Standards are compatible with each other\r
• Security measures align with classification\r
• Technology choices support system functions\r \r ---\r \r

Phase 7: Project Planning\r

\r Goal: Define acquisition strategy and timeline\r \r Guided Questions:\r

• "What is the implementation timeline?"\r
• "What are the major milestones?"\r
• "What resources are required?"\r \r Generated Products:\r
• PV-1: Project Timeline\r
• PV-2: Project Structure\r
• PV-3: Project Resource Flow\r \r Output Artifacts:\r
• docs/07-project-planning.md - Project planning document\r
• diagrams/PV-1-project-timeline.drawio - PV-1 diagram\r
• diagrams/PV-2-project-structure.drawio - PV-2 diagram\r
• diagrams/PV-3-project-resource-flow.drawio - PV-3 diagram\r \r Completeness Checks:\r
• Timeline covers all capability phases\r
• Milestones are defined\r
• Resource requirements are estimated\r
• Risk mitigation is addressed\r \r Consistency Checks:\r
• Timeline aligns with capability phasing\r
• Resource allocation matches project structure\r
• Milestones are realistic\r \r ---\r \r

Phase 8: Overview & Integration\r

\r Goal: Create comprehensive overview and integrated dictionary\r \r Generated Products:\r

• AV-1: Overview and Summary Information (final)\r
• AV-2: Integrated Dictionary\r
• AV-3: Concept of Operations (CONOPS)\r \r Output Artifacts:\r
• docs/08-integration-verification.md - Integration and verification document\r
• diagrams/AV-1-overview-summary.drawio - AV-1 final diagram\r
• docs/AV-2-integrated-dictionary.md - AV-2 dictionary\r
• docs/AV-3-conops.md - AV-3 CONOPS\r
• docs/verification-report.md - Verification report\r
• docs/traceability-matrix.md - Full traceability matrix\r \r Completeness Checks:\r
• All views are referenced in overview\r
• Dictionary includes all key terms\r
• CONOPS describes operational concept\r
• Standards profile is complete\r \r Consistency Checks:\r
• Terminology is consistent across all views\r
• Overview accurately summarizes architecture\r
• Dictionary definitions match usage\r \r ---\r \r

Phase 9: Consolidated Report Generation\r

\r Goal: Merge all views, diagrams, and matrices into a single well-structured document\r \r This is the final and critical phase that transforms scattered artifacts into a professional, deliverable report.\r \r

9.1 Report Assembly\r

\r Step 1: Create Consolidated Markdown Document\r \r Assemble all phase documents into a single Markdown file with the following chapter structure:\r \r

# [Project Name] DoDAF Architecture Description Report\r
\r
## Document Control\r
- Version / Date / Classification / Authors\r
\r
## Table of Contents (auto-generated)\r
\r
## Chapter 1: Executive Summary (AV-1)\r
  - Architecture purpose, scope, findings, recommendations\r
\r
## Chapter 2: Stakeholder & Context Analysis\r
  - Mission statement, stakeholders, environment, constraints\r
\r
## Chapter 3: Operational Architecture (OV)\r
  - 3.1 High-Level Operational Concept (OV-1) + diagram\r
  - 3.2 Operational Resource Flow (OV-2) + diagram\r
  - 3.3 Information Exchange Matrix (OV-3)\r
  - 3.4 Activity Model (OV-5) + diagram\r
\r
## Chapter 4: Capability Architecture (CV)\r
  - 4.1 Capability Taxonomy (CV-1) + diagram\r
  - 4.2 Capability Phasing (CV-2) + diagram\r
  - 4.3 Capability Dependencies (CV-3) + diagram\r
\r
## Chapter 5: Systems Architecture (SV)\r
  - 5.1 Systems Interface Description (SV-1) + diagram\r
  - 5.2 Systems Communication (SV-2) + diagram\r
  - 5.3 Systems Functionality (SV-4) + diagram\r
  - 5.4 Traceability Matrix (SV-5)\r
\r
## Chapter 6: Data Architecture (DIV)\r
  - 6.1 Data Model (DIV-1) + diagram\r
  - 6.2 Data Dictionary (DIV-2)\r
  - 6.3 Data Exchange Matrix (DIV-3)\r
\r
## Chapter 7: Technical Architecture (TV)\r
  - 7.1 Technical Standards (TV-1)\r
  - 7.2 Technical Measures (TV-2)\r
  - 7.3 Technical Framework (TV-3) + diagram\r
\r
## Chapter 8: Project Planning (PV)\r
  - 8.1 Project Timeline (PV-1) + diagram\r
  - 8.2 Project Structure (PV-2) + diagram\r
  - 8.3 Resource Flow (PV-3) + diagram\r
\r
## Chapter 9: Concept of Operations (AV-3)\r
  - Operational scenarios, organization, information flows\r
\r
## Chapter 10: Verification & Validation\r
  - 10.1 Completeness Verification\r
  - 10.2 Consistency Verification\r
  - 10.3 Traceability Matrix\r
  - 10.4 Findings & Recommendations\r
\r
## Appendix A: Integrated Dictionary (AV-2)\r
## Appendix B: Technical Standards Reference (TV-1 detailed)\r
## Appendix C: Data Dictionary (DIV-2 detailed)\r
```\r
\r
**Step 2: Embed Diagrams**\r
\r
For each diagram referenced in the report:\r
1. Export draw.io diagrams to PNG/SVG format (if draw.io CLI available)\r
2. Embed images inline in the Markdown document using `![diagram](path)`\r
3. If export not available, reference the .drawio file path for manual export\r
\r
**Step 3: Generate Final Output**\r
\r
Generate the consolidated report in the user's preferred format:\r
\r
| Format | Method | Notes |\r
|--------|--------|-------|\r
| **Markdown** | Direct assembly | Always generated as base format |\r
| **PDF** | Use `pandoc` or browser print | Professional typesetting, page numbers |\r
| **Word (DOCX)** | Use `pandoc` | Editable, track changes possible |\r
| **HTML** | Use `pandoc` | Interactive, hyperlinked |\r
\r
**Pandoc command examples**:\r
```bash\r
# Markdown to PDF\r
pandoc consolidated-report.md -o report.pdf --pdf-engine=xelatex -V mainfont="SimSun" -V geometry:margin=2.5cm --toc --toc-depth=3 -V numbersections\r
\r
# Markdown to DOCX\r
pandoc consolidated-report.md -o report.docx --toc --toc-depth=3 --reference-doc=template.docx\r
\r
# Markdown to HTML\r
pandoc consolidated-report.md -o report.html --standalone --toc --toc-depth=3 --metadata title="DoDAF Architecture Report"\r
```\r
\r
**Output Artifacts**:\r
- `report/consolidated-report.md` - Single consolidated Markdown file\r
- `report/[project-name]-dodaf-report.pdf` - PDF report (if pandoc available)\r
- `report/[project-name]-dodaf-report.docx` - Word report (if pandoc available)\r
\r
#### 9.2 Report Quality Checklist\r
\r
- [ ] All 23 DoDAF view products are included as chapters/sections\r
- [ ] All diagrams are embedded or referenced\r
- [ ] Cross-references between sections are accurate\r
- [ ] Table of contents is complete\r
- [ ] Document control information is filled\r
- [ ] Classification markings are present on each page (if required)\r
- [ ] Page numbers and headers/footers are set\r
- [ ] Acronyms and abbreviations are defined in dictionary\r
\r
---\r
\r
## Comprehensive Verification Checklist\r
\r
### Completeness Verification\r
\r
| Check | Description | Status |\r
|-------|-------------|--------|\r
| CV-1 | Capability taxonomy covers all operational needs | ☐ |\r
| CV-2 | Capability phasing is defined | ☐ |\r
| CV-3 | Capability dependencies are mapped | ☐ |\r
| OV-1 | High-level operational concept exists | ☐ |\r
| OV-2 | Resource flows are described | ☐ |\r
| OV-3 | Information exchange matrix is complete | ☐ |\r
| OV-5 | Activity model is defined | ☐ |\r
| SV-1 | System interfaces are described | ☐ |\r
| SV-2 | System communications are defined | ☐ |\r
| SV-4 | System functionality is described | ☐ |\r
| SV-5 | Traceability matrix is populated | ☐ |\r
| DIV-1 | Data model is defined | ☐ |\r
| DIV-2 | Data dictionary is complete | ☐ |\r
| DIV-3 | Data exchange matrix is populated | ☐ |\r
| TV-1 | Technical standards are identified | ☐ |\r
| TV-2 | Technical measures are defined | ☐ |\r
| TV-3 | Technical architecture framework is defined | ☐ |\r
| PV-1 | Project timeline is defined | ☐ |\r
| PV-2 | Project structure is defined | ☐ |\r
| PV-3 | Project resource flow is defined | ☐ |\r
| AV-1 | Overview document exists | ☐ |\r
| AV-2 | Integrated dictionary is complete | ☐ |\r
| AV-3 | CONOPS is complete | ☐ |\r
\r
### Consistency Verification\r
\r
| Check | Description | Status |\r
|-------|-------------|--------|\r
| Naming | All elements have consistent naming conventions | ☐ |\r
| Traceability | Cross-view traceability is complete and bidirectional | ☐ |\r
| Capability-System | Every capability maps to at least one system function | ☐ |\r
| Function-Interface | Every function uses defined interfaces | ☐ |\r
| Data-Interface | Every data exchange uses defined interfaces | ☐ |\r
| No Orphans | No orphan elements (elements without connections) | ☐ |\r
| No Cycles | No circular dependencies in capability hierarchy | ☐ |\r
| Standards | All technology choices comply with specified standards | ☐ |\r
| Security | Security requirements are addressed throughout | ☐ |\r
| Terminology | Dictionary terms match usage in all views | ☐ |\r
\r
---\r
\r
## Traceability Matrix Template\r
\r
| Capability | Operational Activity | System Function | Data Element | Interface | Technical Standard | Project Milestone |\r
|------------|---------------------|-----------------|--------------|-----------|-------------------|-------------------|\r
|            |                     |                 |              |           |                   |                   |\r
|            |                     |                 |              |           |                   |                   |\r
|            |                     |                 |              |           |                   |                   |\r
\r
---\r
\r
## Viewpoint Relationships\r
\r
```\r
AV (Overview)\r
    |\r
    +-- OV (Operational) ----------------+\r
    |       |                            |\r
    |       +--> CV (Capability) \x3C-------+\r
    |               |                    |\r
    |               +--> SV (Systems) \x3C--+\r
    |                       |            |\r
    |                       +--> DIV (Data) --+--> Cross-View Traceability\r
    |                       +--> TV (Tech) ---+\r
    |                       +--> PV (Project) +\r
    |                                       |\r
    +---------------------------------------+\r
```\r
\r
---\r
\r
## Output Artifacts\r
\r
### Per-Phase Artifacts (Scattered)\r
\r
Each phase generates:\r
- **Markdown documents**: Detailed descriptions, matrices, dictionaries in `docs/`\r
- **draw.io diagrams**: Visual architecture views in `diagrams/`\r
\r
### Final Consolidated Report (Phase 9)\r
\r
| Artifact | Format | Description |\r
|----------|--------|-------------|\r
| Consolidated Report (MD) | Markdown | Single file with all chapters |\r
| Consolidated Report (PDF) | PDF | Professional printable report |\r
| Consolidated Report (DOCX) | Word | Editable report for review |\r
| Diagram Files | drawio/PNG | All architecture diagrams |\r
\r
---\r
\r
## Agent Integration\r
\r
This skill calls external agents as needed:\r
\r
| Agent | Purpose | Trigger |\r
|-------|---------|---------|\r
| **WebSearch** | Search defense doctrine, standards, case studies | When user provides insufficient information |\r
| **drawio** | Generate draw.io format architecture diagrams | Each phase with visual views |\r
| **DataAnalysis** | Analyze operational data and metrics | When quantitative analysis is needed |\r
\r
---\r
\r
## Tool Dependencies\r
\r
| Tool | Purpose | Required | Install |\r
|------|---------|----------|---------|\r
| draw.io Desktop | Export diagrams to PNG/SVG | No | https://github.com/jgraph/drawio-desktop |\r
| Pandoc | Convert Markdown to PDF/DOCX | No | https://pandoc.org/installing.html |\r
| XeLaTeX | PDF engine for CJK support | No (for PDF) | TeX Live / MiKTeX |\r
\r
> Note: If pandoc or draw.io CLI is not available, the skill will still generate the consolidated Markdown report and .drawio diagram files. Users can manually export or convert later.\r
\r
---\r
\r
## Reference Documents\r
\r
- `references/dodaf-views.md` - Complete DoDAF 2.0 viewpoint reference\r
- `references/dodaf-terminology.md` - Official DoDAF terminology\r
- `references/dodaf-best-practices.md` - Industry best practices\r
\r
---\r
\r
## Changelog\r
\r
### v2.0 (2026-05)\r
- **Added Phase 9**: Consolidated report generation (PDF/Word/HTML output)\r
- **Added output artifact tracking**: Each phase now specifies exact file paths\r
- **Added drawio skill integration**: Diagrams generated as .drawio files\r
- **Added tool dependencies section**: Pandoc, XeLaTeX, draw.io CLI\r
- **Enhanced verification**: 23 view products tracked (was 19)\r
- **Improved workflow**: Sequential phase execution with per-phase verification\r