architecture-consult

Map architecture boundaries and ADR constraints for feature changes.

Updated Jan 5, 2025

Search Tags:#architecture #codebase #adr #architecture-docs #design-decisions #module-discovery

Ready to run

npx skills add https://github.com/pkuppens/pkuppens --skill architecture-consult

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-consult
Source: https://github.com/pkuppens/pkuppens/tree/main/skills/architecture/architecture-consult
Command: npx skills add https://github.com/pkuppens/pkuppens --skill architecture-consult

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture teams need to surface relevant constraints and decisions when planning changes. This guidance reads existing architecture docs, ADRs, and the codebase to map boundaries, ownership, and dependencies.

Core Features & Use Cases

Locate architecture documentation under docs/architecture for arc42 sections and ADR decisions under docs/architecture/adr
Identify modules, components, and services affected by a change
Surface constraints and existing decisions to guide scoping and placement

Quick Start

Survey the target feature area in docs/architecture and adr, then map the relevant modules, files, and constraints to guide implementation.

Frequently Asked Questions about architecture-consult

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

FAQPage Schema

How do I identify architecture boundaries and constraints before scoping a feature change?▼

To identify architecture boundaries, survey existing documentation under docs/architecture and adr directories to map modules, layers, and surface constraints that guide implementation placement and scoping decisions.

How do I find which modules are impacted by a codebase change using ADRs?▼

Find impacted modules by reading ADR decisions and architecture docs to map code boundaries, ownership, and dependencies, clarifying which components and services are affected by your planned feature change.

What is the best way to locate architecture decisions and ADRs in a repository?▼

The best way to locate architecture decisions is to survey the docs/architecture directory for arc42 sections and the docs/architecture/adr subdirectory for individual ADR records that define existing design decisions.

Can I use architecture docs to determine module ownership and dependencies for a new feature?▼

Yes, architecture docs can be used to determine module ownership and dependencies by reading existing decisions and mapping boundaries across the codebase to align new features with established constraints.

Do I need existing architecture documentation to surface constraints for my implementation?▼

You need existing architecture documentation under docs/architecture and adr directories because the process reads those targets to map boundaries, identify impacted modules, and surface constraints that guide implementation.

Why does my feature change conflict with existing architecture boundaries and design decisions?▼

Feature changes conflict with architecture boundaries when existing ADRs and design decisions constrain module placement, layer interactions, and dependency direction, which must be surfaced and mapped before implementation proceeds.