home / skills / shaul1991 / shaul-agents-plugin / docs-internal

docs-internal skill

/skills/docs-internal

This skill creates and maintains internal docs including architecture diagrams, onboarding guides, operating manuals, and architecture decision records.

npx playbooks add skill shaul1991/shaul-agents-plugin --skill docs-internal

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
466 B
---
name: docs-internal
description: Docs Internal Agent. 아키텍처 문서, 온보딩 가이드 작성을 담당합니다.
allowed-tools: Read, Write, Edit, Grep, Glob
---

# Docs Internal Agent

## 역할
내부 기술 문서 작성을 담당합니다.

## 담당 업무
- 아키텍처 문서
- 온보딩 가이드
- 운영 매뉴얼
- ADR (Architecture Decision Records)

## 산출물 위치
- 아키텍처: `docs/architecture/`
- 온보딩: `docs/onboarding/`

Overview

This skill is the Docs Internal Agent responsible for producing internal technical documentation like architecture docs, onboarding guides, operation manuals, and ADRs. It organizes and delivers clear, maintainable documents placed under the project's docs folders for easy discovery and updates. The skill focuses on accuracy, consistency, and practical guidance for internal teams.

How this skill works

The agent gathers context from code, design notes, and stakeholder inputs to draft structured documents. It generates architecture diagrams and narratives, step-by-step onboarding content, runbooks for operations, and formal ADR entries. Final artifacts are stored under docs/architecture/ and docs/onboarding/ for team consumption and versioning.

When to use it

  • When starting a new system or module and an architecture overview is needed
  • When hiring or rotating team members and you need onboarding materials
  • When documenting operational procedures or incident runbooks
  • When capturing a design decision as an ADR for future reference
  • When preparing handover materials between teams

Best practices

  • Provide high-level goals and intended audience before drafting a document
  • Attach relevant diagrams, code references, and example commands to increase usefulness
  • Keep documents concise: include a short summary, context, steps, and follow-up links
  • Version-control all documents and reference ADR IDs in related code or issues
  • Review drafts with engineers and operators to ensure accuracy and completeness

Example use cases

  • Create a system architecture overview for a new microservice, including components, data flow, and deployment notes
  • Produce a 30-minute developer onboarding guide with environment setup, local run instructions, and common troubleshooting tips
  • Write an operations runbook for service recovery, monitoring checks, and escalation paths
  • Record an Architecture Decision Record explaining choice between two database technologies and implications for migration

FAQ

Where are generated documents stored?

Architecture documents go to docs/architecture/ and onboarding guides go to docs/onboarding/.

What types of ADRs are produced?

Formal Architecture Decision Records capturing context, alternatives considered, decisions made, and consequences for traceability.