dev-skills

Use when drafting, reviewing, restructuring, or updating software design documents, RFCs, engineering proposals, architecture proposals, implementation plans, or technical decision documents before or during a software project. Helps decide whether a design doc is warranted, choose the right level of detail, document high-cost decisions and tradeoffs, prepare docs for review, and identify missing goals, non-goals, scenarios, interfaces, dependencies, risks, open issues, and alternatives.

Use when finishing, pushing, opening, or preparing a pull request. Ensures relevant design, roadmap, architecture, operations, API, changelog, release, and implementation-status docs are updated according to repo instructions before the PR is considered complete.

Use when creating, auditing, reorganizing, renaming, consolidating, or updating documentation for infrastructure and developer products, including product thesis, design, architecture, roadmap, operations, API, SDK, runtime, reliability, and implementation-status docs.