skills.rest
AbsolutelySkilled
AbsolutelySkilledOFFICIAL
Explore all skills by this author →
GitHub

internal-docs

Draft and review internal engineering documents with structured frontmatter and explicit alternatives.

207|31|Updated Mar 14, 2026
Search Tags:#documentation#post-mortem#rfc#runbook#knowledge-management#internal-docs
One-click install
npx skills add https://github.com/AbsolutelySkilled/AbsolutelySkilled --skill internal-docs-absolutelyskilled
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: internal-docs
Source: https://github.com/AbsolutelySkilled/AbsolutelySkilled/tree/main/skills/internal-docs
Command: npx skills add https://github.com/AbsolutelySkilled/AbsolutelySkilled --skill internal-docs-absolutelyskilled

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Draft and review internal engineering documents to capture decisions, preserve operational knowledge, and ensure organizational learning across RFCs, design docs, post-mortems, runbooks, and knowledge base articles.

Core Features & Use Cases

  • Draft RFCs and design docs using structured templates that capture motivations, alternatives, and decisions.
  • Write and review post-mortems, runbooks, and knowledge-management articles with consistent formatting and ownership.
  • Organize and discover internal docs across teams by applying taxonomy, ownership, and versioning patterns.

Quick Start

Draft an RFC for a new authentication flow and fill in the required sections with motivation, alternatives, and rollout plan.

Frequently Asked Questions about internal-docs

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

FAQPage Schema
How do I draft an RFC that captures engineering decisions and alternatives?▼

Write post-mortems using consistent formatting that assigns explicit ownership and ties documented actions to specific outcomes. This preserves operational knowledge and ensures organizational learning across engineering teams.

What is the best way to structure internal engineering docs for knowledge management?▼

Structure internal engineering docs by applying consistent taxonomy, ownership, and versioning patterns across knowledge bases and runbooks. This enforces structured frontmatter so teams can organize and discover documents efficiently.

How do I write a post-mortem that assigns owners and documents outcomes?▼

Write post-mortems using consistent formatting that assigns explicit ownership and ties documented actions to specific outcomes. This preserves operational knowledge and ensures organizational learning across engineering teams.

Can I use structured frontmatter to organize and discover internal docs across teams?▼

Yes, you can apply structured frontmatter to internal docs to enforce taxonomy, ownership, and versioning patterns. This allows engineering teams to consistently organize and discover knowledge base articles and runbooks across the organization.

Do I need to document explicit alternatives when writing a design doc?▼

Yes, writing a design doc requires documenting explicit alternatives alongside motivations and rollout plans. Capturing these alternatives ensures that engineering decisions are clear, evaluated, and preserved for future reference.

Related Skills

Explore More Content & Communication Skills→
patricio0312revpatricio0312rev
5

rfc-generator

Generate RFC-style technical proposals with problem statements, solutions, alternatives, risks, and rollout plans.

Community
Advanced
coreymaypraycoreymaypray
1

incident-response-commander

Coordinate incident response for production outages with runbooks and severity frameworks.

Community
Advanced
AlexiosBluffMaraAlexiosBluffMara
2

llm-wiki

Ingest sources into an interlinked Markdown knowledge base with linting and search.

Community
Advanced
MaggieAppletonMaggieAppleton
160

writing-plans

Write implementation plans mapping tasks, files, tests, and documentation.

Community
Advanced