skills.rest
jpoley
jpoleyCOMMUNITY
Explore all skills by this author →
Website𝕏@jbpoleyGitHub

architect

Generate and format Architecture Decision Records with standard templates.

50|9|Updated Oct 15, 2025
Search Tags:#architecture#documentation#governance#infrastructure#ADR#system-design#architecture-decision
One-click install
npx skills add https://github.com/jpoley/flowspec --skill architect-jpoley
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/jpoley/flowspec/tree/main/.claude/skills/architect
Command: npx skills add https://github.com/jpoley/flowspec --skill architect-jpoley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Software teams often struggle to converge on clear architecture decisions and maintain a living record of why certain choices were made. This Skill guides the creation of Architecture Decisions Records (ADRs) and enforces consistent architectural documentation.

Core Features & Use Cases

  • ADR Creation & Formatting: Generate ADRs with standard templates and traceable context.
  • Architecture Principles: Define and enforce principles to guide design decisions.
  • Technology Evaluation: Systematically compare tech options and capture rationale.
  • Plan & Communicate: Outline implementation plans and governance for changes.
  • Use Case: When choosing between databases or deployment strategies, produce ADRs and a decision log.

Quick Start

Draft an ADR for selecting a database technology for a new service, including context, alternatives, decision, and consequences.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I document architectural decisions for my software project?▼

Architecture Decision Records (ADRs) document the reasoning behind design choices. ADRs capture context, alternatives considered, the decision made, and its consequences, creating a traceable record of why your system evolved the way it did.

What should I include in an ADR when evaluating database or infrastructure options?▼

A complete ADR includes the problem context, alternative technologies evaluated, your chosen solution, rationale for the selection, and anticipated consequences. This systematic approach ensures technology decisions are explicit and justified.

How can I enforce consistent architecture documentation across my team?▼

Establish architecture principles and ADR formatting standards that guide design decisions uniformly. Enforcing consistent templates and governance ensures all team members document decisions the same way, maintaining a coherent decision log.

When should I create an ADR instead of just deciding internally?▼

Create ADRs when making significant system design choices—database selection, deployment strategies, or technology evaluation—that affect multiple teams or have long-term consequences. ADRs transform ephemeral discussions into durable institutional knowledge.

Can I use ADRs to communicate infrastructure planning and changes to stakeholders?▼

Yes. ADRs serve as living documentation that communicates implementation plans, governance decisions, and architectural rationale to both technical and non-technical stakeholders, enabling informed decision-making across the organization.

Related Skills

Explore More Software Engineering Skills→
t-i-0414t-i-0414

project-context

Summarize project goals, constraints, and dependencies into a context document.

Community
Intermediate
s3nex-coms3nex-com

architecture-decision-records

Create and manage Architecture Decision Records with a templated format.

Community
Advanced
sethdfordsethdford
2

Architecture Decision Records

Create and maintain Michael Nygard ADR templates in Confluence.

Community
Advanced
outfitter-devoutfitter-dev
4

clark-decision

Log Trails framework decisions with rationale to .trails/clark/decisions.md.

Official
Advanced