skills.rest
addxai
addxaiOFFICIAL
Explore all skills by this author →
GitHub

architect

Generate standardized architecture documentation from user stories with ADRs and domain models.

42|7|Updated Apr 17, 2026
Search Tags:#adr#ddd#architecture design#user stories#technical documentation#test planning#system decomposition
One-click install
npx skills add https://github.com/addxai/enterprise-harness-engineering --skill architect-addxai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/addxai/enterprise-harness-engineering/tree/main/skills/architect
Command: npx skills add https://github.com/addxai/enterprise-harness-engineering --skill architect-addxai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates ad-hoc, intuition-driven system design and scattered, inconsistent technical documentation that leads to misalignment, rework, and unclear architecture decisions in software development projects. It ensures design is intentional, fully documented, and aligned with business requirements before any code is written, reducing costly rework and onboarding friction.

Core Features & Use Cases

  • Socratic questioning-driven design: Identifies implicit architectural concerns from user stories, converges on decisions with documented tradeoffs, and avoids premature solutioning that leads to flawed architectures.
  • Standardized documentation system: Generates a complete, navigable set of technical docs (architecture overviews, domain models, ADRs, module specs) aligned with DDD ubiquitous language to ensure consistent terminology across teams.
  • End-to-end workflow integration: Covers the full project lifecycle from user story definition to CI/CD documentation, with built-in guardrails like 400-line file limits, cross-document sync rules, and ADR reasoning chain requirements.
  • Use case: For a team building a new multi-tenant SaaS feature, use this Skill to systematically decompose user requirements, evaluate architecture options with full tradeoff analysis, and produce a maintainable documentation suite that stays in sync with implementation.

Quick Start

Use the architect skill to design the system for a new user notification feature, starting with the user stories for real-time push alerts and multi-tenant delivery rules.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I create standardized technical documentation from user stories?▼

Standardized technical documentation is generated by using Socratic questioning to identify implicit architectural concerns from user stories, converging on decisions with documented tradeoffs to produce architecture overviews, domain models, and ADRs.

What is the best way to document architecture decisions and avoid rework?▼

Documenting architecture decisions through a repeatable, guardrailed design process eliminates ad-hoc system design, ensuring intentional design with documented tradeoffs and ADR reasoning chains to prevent costly rework and onboarding friction.

How do I decompose a system using domain-driven design?▼

System decomposition using domain-driven design applies ubiquitous language to ensure consistent terminology across teams, generating navigable domain models and module specs aligned with user requirements before code implementation.

Can I generate test plans and CI/CD guides alongside architecture overviews?▼

Generating test plans and CI/CD guides alongside architecture overviews is supported by end-to-end workflow integration, covering the full project lifecycle from user story definition to continuous integration documentation.

What are the limitations of intuition-driven system design for enterprise software?▼

Intuition-driven system design causes misalignment, rework, and unclear architecture decisions in enterprise software workflows, requiring structured architecture decision-making and cross-document sync rules to maintain navigable, consistent documentation.

Does the architecture design process enforce file size limits and cross-document sync?▼

The architecture design process enforces built-in guardrails including 400-line file limits and cross-document sync rules to ensure the standardized technical documentation suite remains maintainable and aligned with implementation.

Related Skills

Explore More Software Engineering Skills→
arrowInkneeeeearrowInkneeeee
1

priority-assessor

Prioritize user stories with MoSCoW analysis and generate an implementation sequence.

Community
Intermediate
yangqiongyangqiong

CI/CD Pipeline Skill

Generate automated CI/CD pipeline configurations in YAML for GitHub Actions and GitLab CI/CD.

Community
Advanced
gugug168gugug168

e2e-testing

Automate Playwright end-to-end testing workflows with Page Object Model and CI/CD integration.

Community
Intermediate
hdtinh57hdtinh57
1

planning

Coordinate backlog planning and architecture decisions across product and technical domains.

Community
Advanced