documentation-specialist

Extract architectural information and data-flow documentation into structured JSON and Markdown.

12|4|Updated Nov 6, 2025
One-click install
npx skills add https://github.com/ensingm2/AI-threat-modeling-rulesets --skill documentation-specialist-ensingm2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation-specialist
Source: https://github.com/ensingm2/AI-threat-modeling-rulesets/tree/main/.ai-instructions/skills/documentation-specialist
Command: npx skills add https://github.com/ensingm2/AI-threat-modeling-rulesets --skill documentation-specialist-ensingm2

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill extracts factual architectural information and creates structured data-flow documentation, ensuring source traceability and reducing ambiguity in Stage 1, Stage 2, and Stage 6 outputs.

Core Features & Use Cases

  • System Understanding Extraction: Build component inventories, trust boundaries, and data assets from source docs.
  • Data Flow Documentation: Produce clear Stage 2 data flows aligned to Stage 1 components.
  • Final Report Formatting Support: Prepare self-contained outputs for Stage 6.

Quick Start

Read source documentation, extract factual architecture details, and generate the required ai-working-docs and system understanding Markdown.

Frequently Asked Questions about documentation-specialist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract architecture and data flows from documentation?

Extract architecture and data flows by reading source documentation, identifying components and trust boundaries, then generating structured JSON artifacts and Markdown that map data movement between systems with full source attribution.

What is source traceability in threat modeling documentation?

Source traceability means every architectural claim and data flow is tagged as documented, inferred, or unknown and linked to its source, eliminating ambiguity and ensuring threat models rest on factual, verifiable information.

Can I use this to prepare Stage 1, Stage 2, and Stage 6 threat modeling outputs?

Yes. This Skill extracts architectural information and data-flow documentation aligned to Stage 1 components, produces Stage 2 data flows, and formats self-contained outputs ready for Stage 6 final reports.

How do I build a component inventory and trust boundary map from source docs?

Read your source documentation, identify system components and trust boundaries, then use this Skill to generate a structured component inventory with data assets mapped to boundaries and traced to their documentation source.

What's the difference between documented, inferred, and unknown data tags?

Documented data flows are explicitly stated in source material; inferred flows are deduced from documented facts; unknown flows lack sufficient source evidence, preventing fabrication and maintaining transparency in threat models.

Do I need existing architectural documentation to use this Skill?

Yes. This Skill extracts from source documentation you provide—design docs, system diagrams, or architecture specifications—so complete or partial source material is required to generate accurate, traced outputs.