Results for “adr”

Write and maintain Architecture Decision Records (ADRs) — when to write one, the standard format, status lifecycle, how to link related decisions, and how to surface ADRs in a codebase. Use when asked to "write an ADR", "document this decision", "architecture decision record", "why did we choose X over Y", or "we need a record of this choice". Do NOT use for: general documentation writing — ADRs are specifically for significant architecture decisions.

Records architectural decisions and documentation to capture the context, constraints, and trade-offs behind codebase choices.

Generate structured Architectural Decision Record (ADR) documents with standardized front matter, consequences, and alternatives for AI-optimized decision documentation.

Mantém a documentação técnica viva no Notion e no repositório, gerando runbooks, inventários, ADRs e procedimentos a partir da infraestrutura real.

Create, extract, or convert architectural decision records (ADRs) using a structured template, with project context discovery and evidence-based review.

Document architectural decisions in standardized ADR format. This skill should be used when making significant technical decisions, choosing between approaches, establishing patterns, or when other skills (create-plan, implement-plan, brainstorm) identify decisions that need documentation. Triggers on "document decision", "create ADR", "architectural decision", or automatically when invoked by other skills during planning and implementation.

Generates and maintains project documentation: Google-style docstrings, README, architecture docs, and ADRs, with a mandatory post-task review gate to keep docs current.

Audits documentation health by scanning for README, changelog, API docs, ADRs, runbooks, onboarding guides, and diagrams, scoring coverage against project maturity, and recommending sub-skills to fill gaps.

Runs a structured interview that stress-tests a plan against the project's domain model, sharpens terminology, and updates CONTEXT.md and ADRs inline as decisions are made.

An ADR records one decision at the moment it is made, with the information that

Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.

Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.

Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.

Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.

Generate a structured specification document before writing implementation code, validating scope, drafting specs, and registering them in the project.

Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

Extract project vision and decisions from a user through iterative Q&A, then convert them into clear repo documentation (README, ADRs, lessons). Use when user asks to document ideas in their head.

Initiates a 6‑month trial of DHEA replacement in women with primary adrenal insufficiency (PAI) who have persistent low libido, depressive symptoms, or low energy despite otherwise optimized glucocorticoid and mineralocorticoid therapy. If the patient does not report a sustained beneficial effect after 6 months, discontinue DHEA.

Maintains a project's domain vocabulary and records architecturally-significant decisions as they're made — a CONTEXT.md glossary and gated ADRs, not passive documentation read once. Use when terminology conflicts or turns fuzzy, when making a decision that's hard to reverse/surprising/a real trade-off, or when a stated domain rule doesn't match what the code actually does.

Creates and updates coding standards, conventions, rules, and guidelines for the current project. Use when creating new standards from scratch, converting existing documents into coding standards, or updating existing standards. Does not create architectural decision records — use architectural-decision-record for ADRs. Does not write feature or system documentation — use project-documentation for that. Does not research open-ended options — use research. Does not produce runbooks for operational scenarios — use runbook for that.