documentation-rfc
Documentation RFC
Overview
Use this skill to produce decision-ready RFCs that let stakeholders review options with clear tradeoffs and risks.
Scope Boundaries
- Use this skill when the task matches the trigger condition described in
description. - Do not use this skill when the primary task falls outside this skill's domain.
Shared References
- Decision quality checks:
references/rfc-decision-quality-checks.md
Templates And Assets
- RFC template:
assets/rfc-template.md
- Tradeoff matrix template:
assets/rfc-tradeoff-matrix-template.csv
Inputs To Gather
- Problem statement and business/technical motivation.
- Constraints and non-goals.
- Candidate options and evaluation criteria.
- Risks, rollout implications, and decision timeline.
Deliverables
- RFC with context, options, recommendation, and rationale.
- Tradeoff table and risk assessment.
- Open questions and decision dependencies.
- Review checklist and approval path.
Quick RFC Skeleton
- Problem and goals/non-goals.
- Constraints and assumptions.
- Options considered (including rejected options).
- Recommendation and rationale.
- Risks, rollout, and rollback considerations.
- Open questions and required approvals.
Quality Standard
- Problem framing is concrete and scope-bounded.
- Options are comparable with explicit criteria.
- Recommendation includes why alternatives were rejected.
- Risks and unknowns are clearly separated.
Workflow
- Define problem scope and success criteria.
- Collect options and evaluation evidence.
- Compare options with explicit tradeoff criteria in
assets/rfc-tradeoff-matrix-template.csv. - Draft recommendation and risk treatment plan using
assets/rfc-template.md. - Publish for review with clear decision deadlines.
Failure Conditions
- Stop when recommendation lacks option comparison evidence.
- Stop when major risks/unknowns are hidden or untracked.
- Escalate when required approvers are missing for high-impact decisions.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9