cmd-architecture-team-design

Design comprehensive architecture documentation covering multiple system perspectives.

2|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/jlaws/dotfiles --skill cmd-architecture-team-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cmd-architecture-team-design
Source: https://github.com/jlaws/dotfiles/tree/main/.agents/skills/cmd-architecture-team-design
Command: npx skills add https://github.com/jlaws/dotfiles --skill cmd-architecture-team-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Produce comprehensive, multi-perspective architecture documents for new systems or to document existing architectures, replacing ad-hoc and scattered design efforts.

Core Features & Use Cases

  • Structured discovery to map existing patterns, APIs, data models, and constraints.
  • Multi-perspective analysis across component architecture, API design, data architecture, and security/operations.
  • Synthesis and implementation planning that yield a cohesive design with decisions, risks, and an actionable plan.

Quick Start

Provide the target directory path and a concise system description to generate the full architecture document and an implementation plan.

Frequently Asked Questions about cmd-architecture-team-design

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

FAQPage Schema
How do I create a comprehensive architecture document for a new system?

To create a comprehensive architecture document, you need a structured process covering discovery, multi-perspective analysis, and synthesis. This approach maps existing patterns, APIs, and data models to produce cohesive design docs with actionable implementation plans.

What is the best way to document an existing system architecture?

Documenting existing architecture requires a phased discovery process to map current patterns, APIs, and constraints. A multi-perspective analysis across component, data, and security domains yields a formal architecture document with identified risks and decisions.

Can I use this system design process for both new and existing architectures?

Yes, this system design process applies to both new systems and documented existing architectures. It enforces a phased workflow that guides discovery, multi-perspective analysis, and implementation planning to produce formal design documentation.

What perspectives should a design review cover for scalable architecture?

A design review for scalable architecture should cover component architecture, API design, data architecture, and security or operations. Multi-perspective analysis ensures a cohesive synthesis that identifies risks and yields an actionable implementation plan.

How do I turn a system design into an actionable implementation plan?

Turning a system design into an actionable implementation plan requires synthesizing multi-perspective analysis into a cohesive strategy. This process produces a formal architecture document with recorded decisions, identified risks, and a structured implementation plan.

What do I need to start generating architecture documentation?

To start generating architecture documentation, you need to provide a target directory path and a concise system description. This input triggers the structured discovery and multi-perspective analysis phases to output a formal design doc and implementation plan.