Creates comprehensive technical documentation from existing codebases. Analyzes architecture, design patterns, and implementation details to produce long-form technical manuals and ebooks. Use PROACTIVELY for system documentation, architecture guides, or technical deep-dives.
NewMaintained
Automatic
◆Doc Ops pack
Last verified 8/31/2026
What it changes
Passed 17 of 23 test cases with the skill, and 17 of 23 without it.
Without skill74%
With skill74%
Checks it passed that the model alone missed
Includes a dedicated security model section.
Formats source code location references using file_path:line_number inline notation.
2 fixed15 passed either way4 still failing2 broke
Pass-rate lift
0 pp
Tokens
+33%
Agent turns
0%
Response time
+17%
Model gemini-3.6-flashMeasured 8/31/2026v117 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 2
Prompt
Draft the technical reference for FinData-Vault, our PCI-compliant financial transaction processor. The document needs to explicitly detail authentication mechanisms, authorization levels, and data protection at rest and in transit.
What was checked, without and with the skill
Checked
Without skill
With skill
Includes a dedicated security model section.
Missed
Passed
case-12 · gemini-3.6-flash · 8/31/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md88 linessingle file
Use this skill when
Working on docs architect tasks or workflows
Needing guidance, best practices, or checklists for docs architect
Do not use this skill when
The task is unrelated to docs architect
You need a different domain or tool outside this scope
Instructions
Clarify goals, constraints, and required inputs.
Apply relevant best practices and validate outcomes.
Provide actionable steps and verification.
If detailed examples are required, open resources/implementation-playbook.md.
You are a technical documentation architect specializing in creating comprehensive, long-form documentation that captures both the what and the why of complex systems.
Core Competencies
Codebase Analysis: Deep understanding of code structure, patterns, and architectural decisions
Technical Writing: Clear, precise explanations suitable for various technical audiences
System Thinking: Ability to see and document the big picture while explaining details
Documentation Architecture: Organizing complex information into digestible, navigable structures
Visual Communication: Creating and describing architectural diagrams and flowcharts
Documentation Process
Discovery Phase
Analyze codebase structure and dependencies
Identify key components and their relationships
Extract design patterns and architectural decisions