Agent Skills
› NeverSight/learn-skills.dev
› document-writer
document-writer
GitHub专注于创建结构化技术文档的专家技能，涵盖ADR、RFC、系统设计文档及知识库文章。适用于需要规范化记录架构决策、技术方案评审、系统运行指南及事故复盘的场景，确保文档的一致性与可维护性。
Trigger Scenarios
编写架构决策记录(ADR)
创建RFC文档
撰写系统设计文档
编写技术规格说明书
制作运维手册或应急预案
构建内部知识库
撰写事故后复盘报告
Install
npx skills add NeverSight/learn-skills.dev --skill document-writer -g -y
SKILL.md
Frontmatter
{
"name": "document-writer",
"description": "Expert in creating technical documentation, architectural decision records (ADRs), and RFCs. Specializes in structured knowledge management and system documentation. Use when writing technical docs, ADRs, RFCs, or system design documents."
}
Document Writer
Purpose
Provides expertise in creating structured technical documentation for software systems. Specializes in architectural decision records, RFCs, design documents, and knowledge base articles.
When to Use
- Writing architectural decision records (ADRs)
- Creating RFC (Request for Comments) documents
- Documenting system designs
- Writing technical specifications
- Creating runbooks and playbooks
- Building internal knowledge bases
- Documenting incidents (post-mortems)
Quick Start
Invoke this skill when:
- Writing architectural decision records (ADRs)
- Creating RFC documents
- Documenting system designs
- Writing technical specifications
- Creating runbooks and playbooks
Do NOT invoke when:
- Writing API documentation (use api-documenter)
- Writing user-facing docs (use technical-writer)
- Creating Word documents (use docx-skill)
- Writing marketing content (use content-marketer)
Decision Framework
Document Type Selection:
├── Decision needed → ADR
├── Proposal for review → RFC
├── System explanation → Design doc
├── How to operate → Runbook
├── Incident occurred → Post-mortem
├── Process definition → SOP
└── Knowledge capture → Wiki article
Core Workflows
1. ADR Creation
- Identify decision to be made
- List context and constraints
- Enumerate options considered
- Analyze pros and cons
- State decision and rationale
- Document consequences
- Get stakeholder review
2. RFC Process
- Write problem statement
- Propose solution approach
- Detail implementation plan
- Address risks and mitigations
- Define success metrics
- Open for comments
- Iterate based on feedback
- Move to accepted/rejected
3. Design Document
- State purpose and scope
- Describe current state
- Present proposed design
- Include diagrams (C4, sequence)
- Address non-functional requirements
- List alternatives considered
- Define rollout plan
Best Practices
- Use templates for consistency
- Include diagrams for complex systems
- Write for the reader, not yourself
- Keep documents updated
- Link related documents
- Version control all documentation
Anti-Patterns
| Anti-Pattern | Problem | Correct Approach |
|---|---|---|
| No template | Inconsistent docs | Use standard templates |
| Write-only docs | Never updated | Schedule reviews |
| Missing context | Readers confused | Include background |
| Too verbose | Nobody reads | Be concise, link details |
| Undiscoverable | Docs go unused | Organize and index |
Version History
- e0220ca Current 2026-07-05 21:13
