Packs

3 packs

Create Architecture Documentation

Create comprehensive architectural documentation with diagrams and ADRs for a codebase.

7 skills · pack

Adrian Luna Díaz personal skill library — product management, engineering, design, and operations skills.

57 skills · pack

Create Architectural Decision Record

Document architectural decisions with context, consequences, and alternatives in a standardized ADR format.

10 skills · pack

Results for “adr”

7 skills

grill-with-docs

Stress-tests a plan against the project's domain model and documented decisions, sharpening terminology and updating DOMAIN.md and ADRs inline as decisions crystallize.

grill-with-docs

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.

Designing, optimizing, and auditing repository structure: directory design, docs/ layout (PRD, specs, ADR), test/script organization, anti-pattern detection. Use for repo layout or migration planning.

More results

Provides technical leadership frameworks for architecture decisions, engineering team scaling, technology strategy, and technical debt assessment.

20.4k · bundle

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

superpowers-sage-architecture-discovery

Architecture discovery for Sage/Acorn projects — map existing codebase, discover post types, routes, ACF field groups, Livewire components, Service Providers, identify architectural gaps, architecture decision records, ADR, component boundary map, data flow diagram, risk register, implementation sequencing, discovery session, understanding unknown codebases, use before architecting or building new features, output contract, discover-abilities

project-documentation

Creates and maintains project documentation for features, systems, and components. Use when documenting how a feature, system, or component works — including writing, updating, or organizing docs. Does not scan or detect the project's technology stack — use project-discovery for repository analysis and config detection. Does not create architectural decision records — use architectural-decision-record for ADRs. Does not create or update coding standards — use coding-standard instead. Does not generate PR descriptions — use update-pr-description for that. Does not produce runbooks for operational scenarios — use runbook for that. Does not rewrite existing prose for readability — use edit-for-readability for that. Does not produce an ephemeral, understand-now overview of code or a PR — use code-overview for that.