skills.rest
djwmobley
djwmobleyCOMMUNITY
Explore all skills by this author →
GitHub

architecture

Synthesize architectural decisions and persist constraints to docs/architecture.md.

Updated Mar 18, 2026
Search Tags:#architecture#decision-making#cross-domain#recon#domain-specialists#docs/architecture.md
One-click install
npx skills add https://github.com/djwmobley/pipeline --skill architecture-djwmobley
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/djwmobley/pipeline/tree/main/skills/architecture
Command: npx skills add https://github.com/djwmobley/pipeline --skill architecture-djwmobley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecting complex software projects requires formal decisions to constrain downstream planning and implementation, preventing drift and misalignment.

Core Features & Use Cases

  • Silent mode coordinates recon and constraint embedding to steer the plan for MEDIUM changes.
  • Full mode orchestrates recon + domain specialists + lead architect for LARGE changes, producing persisted decisions and artifacts.
  • Artifacts and constraints are persisted to docs/architecture.md and the knowledge tier for reuse across projects.

Quick Start

Run the architecture skill on the current project to generate decisions and persist docs/architecture.md.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I synthesize architectural decisions to constrain downstream planning?▼

To synthesize architectural decisions for downstream planning, run the architecture Skill to coordinate recon, domain specialists, and a lead architect, producing final decision records and cross-domain constraints for DATA, STATE, UI, API, INFRA, and TEST.

What is the best way to prevent drift and misalignment in complex software projects?▼

Preventing drift and misalignment in complex software projects requires formal architectural decisions that constrain downstream implementation, coordinating cross-domain recon and domain specialists to produce persisted decision records.

How do I generate and persist an architecture artifact for my project?▼

You generate and persist an architecture artifact by running the architecture Skill on your current project, which synthesizes architectural decisions and saves the final output directly to docs/architecture.md for reuse across projects.

Does the architecture coordination mode change based on project size?▼

Yes, architecture coordination scales with project size: silent mode coordinates recon and constraint embedding for MEDIUM changes, while full orchestration coordinates recon, domain specialists, and a lead architect for LARGE changes.

When do I need formal architectural decision records for software changes?▼

You need formal architectural decision records when executing MEDIUM or LARGE changes that require cross-domain constraints across DATA, STATE, UI, API, INFRA, and TEST to prevent downstream implementation drift and misalignment.

Related Skills

Explore More Software Engineering Skills→
mschuerigmschuerig

bmad-generate-project-context

Generate a project-context.md documenting tech stack, patterns, and workflows.

Community
Advanced
kssuminkssumin

multi-module-reference

Organize Kotlin multi-module projects with module boundaries and dependency mapping.

Community
Advanced
gabriellpequenogabriellpequeno
8

intelligent-routing

Determine escalation paths for ambiguous multi-domain requests.

Community
Intermediate
onbluerosesonblueroses
3

domain-modeling

Create domain model terms and document architectural decisions as ADRs.

Community
Advanced