architect

Generates ADRs and phased implementation roadmaps for complex software systems.

3|1|Updated Apr 18, 2021
One-click install
npx skills add https://github.com/nashgao/mqtt-client --skill architect-nashgao
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/nashgao/mqtt-client/tree/main/.claude/skills/architect
Command: npx skills add https://github.com/nashgao/mqtt-client --skill architect-nashgao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures robust system design by mandating thorough architectural analysis before implementation, preventing costly rework and technical debt.

Core Features & Use Cases

  • Architecture Decision Records (ADRs): Generates formal documentation for key design choices.
  • Implementation Roadmaps: Creates phased plans for development and deployment.
  • Risk Assessment: Identifies and mitigates potential architectural risks.
  • Use Case: Before building a new microservice, use this Skill to analyze requirements, evaluate design patterns, document decisions in ADRs, and generate a clear implementation roadmap, ensuring alignment and foresight.

Quick Start

Use the architect skill to design the architecture for a new user authentication service.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I generate Architecture Decision Records for a new microservice?▼

Architecture Decision Records are generated by enforcing structured analysis of system requirements, dependencies, and design patterns. This process formally documents key architectural choices to prevent rushed implementation and technical debt.

What is included in a system design implementation roadmap?▼

A system design implementation roadmap includes phased plans for development and deployment based on architectural analysis. It provides a structured breakdown of implementation stages to ensure alignment and foresight before coding begins.

When do I need a structured risk assessment for system architecture?▼

A structured risk assessment for system architecture is needed when designing complex software systems to identify and mitigate potential architectural risks. This prevents costly rework by mandating thorough analysis before the implementation phase.

Can I use this to design an architecture without any prior codebase?▼

Yes, you can design system architecture without a prior codebase by using this approach to analyze requirements and evaluate design patterns. It mandates a thorough architectural analysis phase before any actual implementation occurs.

What's the best way to document system design decisions for complex software?▼

The best way to document system design decisions is by generating formal Architecture Decision Records and implementation roadmaps. This ensures robust system design by mandating thorough architectural analysis of requirements, patterns, and risks.