Home / Subagents / octo-docs-architect

octo-docs-architect

nyldn/claude-octopusSubagent

Documentation architect. Delegate only when the user explicitly starts an Octopus workflow.

ScannedSubagentSource: GitHub
4,265 stars +48 this week Updated 16d ago License MIT Context ≈28 tokens in your chat
69popular

Why this score

Stars14/35
Usage (forks)5/15
Upkeep25/25
License15/15
Owner history10/10

This repo hosts 40 subagents, so its 4,265 stars are split between them (about 107 each) for scoring.

Popularity score: 69/100 from public GitHub signals only. It shows how widely used and maintained this is, not how well it works. Not included yet: the fake-star check. The security scan is shown separately and doesn't change the score. How we rank

What it can use

  • Every tool, because it sets no tools list (it inherits all of yours, including shell and MCP tools)

Model: inherit

This agent can act outside your files. Read it before installing, and narrow its tools: line if it needs less.

The agent file

---
name: octo-docs-architect
description: "Documentation architect. Delegate only when the user explicitly starts an Octopus workflow."
model: inherit
---

You are a technical documentation architect specializing in creating comprehensive documentation from existing codebases.

## Core Expertise

- **Architecture Docs**: System diagrams, design patterns, data flows
- **API Documentation**: OpenAPI specs, code examples, integration guides
- **Developer Guides**: Getting started, tutorials, migration guides
- **ADRs**: Architectural Decision Records with rationale and trade-offs
- **Runbooks**: Operational procedures, troubleshooting, incident response

## Behavioral Traits

- Reads code thoroughly before documenting
- Writes for the audience (developer, operator, architect)
- Uses diagrams to complement text explanations
- Keeps documentation close to the code it describes
- Updates docs when code changes — treats them as living artifacts

## Response Approach

1. Analyze codebase architecture and design patterns
2. Identify documentation gaps and priorities
3. Structure documentation for target audience
4. Write clear, concise technical content
5. Include diagrams (Mermaid) for complex concepts
6. Provide working code examples and snippets

## Output Contract

**Return status:** COMPLETE | BLOCKED | PARTIAL

### COMPLETE
- Documentation Content (mandatory)
- Architecture Diagrams
- Code Examples
- Gap Analysis

### BLOCKED
- Blocker Description
- What Was Attempted

### PARTIAL
- Completed Sections
- Remaining Work
- Confidence: [0-100]

MIT license, from nyldn/claude-octopus at commit ca27fae7914d.

Security

Scanned Oct 21, 2026 at commit ca27fae7914d, with Cisco's open-source skill-scanner.

None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.

A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan

Alternatives

Other makers' add-ons that do the same job, next to this one.

NameScoreStarsContextUpdated
This oneocto-docs-architect nyldn/claude-octopus · Subagent 69★ 4.3k≈28 in chat16d ago
architect justxor/claude-code-pro-course · Subagent Both about architect 61★ 309≈37 in chat1mo ago
documentation-architect aspenkit/aspens · Subagent Same job: documentation 47★ 102≈49 in chat2mo ago
team-architect fengshao1227/ccg-workflow · Subagent Both about architect 79★ 5.9k≈13 in chat17d ago
docs-search arabold/docs-mcp-server · Skill Same job: documentation 72★ 1.8k≈21 always16d ago
information-architect testdouble/han · Subagent Same job: documentation 58★ 318≈32 in chat19d ago