Architecture Design (project-level)

Generate project-level architecture documentation with ADRs and domain specialist collaboration.

Updated May 10, 2026
One-click install
npx skills add https://github.com/AshleyHollis/agentic-identity-lab --skill architecture-design-project-level
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Architecture Design (project-level)
Source: https://github.com/AshleyHollis/agentic-identity-lab/tree/main/.copilot/skills/architecture-design
Command: npx skills add https://github.com/AshleyHollis/agentic-identity-lab --skill architecture-design-project-level

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the production of detailed project-level architecture documentation, reducing the complexity of fan-out processes across various domain concerns.

Core Features & Use Cases

  • Project-Level Documentation: Generates documentation that outlines system overview, principles, and key decisions.
  • Domain Specialist Collaboration: Orchestrates collaboration between domain specialists for specific architecture concerns.
  • ADRs and Decisions: Manages architectural decisions with ADRs, ensuring traceable rationale and compliance.

Quick Start

Run the architecture design skill to start the documentation process for your project.

Frequently Asked Questions about Architecture Design (project-level)

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

FAQPage Schema
How do I create comprehensive project architecture documentation efficiently?

Project architecture documentation is generated by coordinating domain specialists and managing architectural decisions through ADRs. This structured approach outlines system overviews, principles, and key project decisions, ensuring traceable rationale and reducing the complexity of fan-out processes.

How do ADRs help manage architectural decisions in project-level documentation?

ADRs help manage architectural decisions by capturing traceable rationale and compliance within your project documentation. They ensure every key architectural choice is documented, reducing complexity and maintaining clear records when coordinating across various domain specialists.

What is the best way to coordinate domain specialists for architecture design?

The best way to coordinate domain specialists for architecture design is to orchestrate their collaboration through a structured documentation process. This ensures specific architecture concerns are addressed comprehensively while managing project-level decisions and system principles via ADRs.

Can I use this approach to document system overviews and key principles for a new project?

Yes, you can document system overviews and key principles for a new project using this approach. It generates comprehensive project-level architecture documentation that outlines these elements while managing architectural decisions through ADRs for easy reference and maintenance.

How do I maintain traceable rationale for project architectural decisions?

You maintain traceable rationale for project architectural decisions by using Architecture Decision Records (ADRs). ADRs document the compliance and reasoning behind each choice, providing a structured output that coordinates domain collaboration and ensures easy future reference.