nexus2-arch

Generate structured architecture documentation with decision records and diagrams.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/tcfialho/Herald.Ai.Skills --skill nexus2-arch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nexus2-arch
Source: https://github.com/tcfialho/Herald.Ai.Skills/tree/main/skills/nexus2/nexus_arch
Command: npx skills add https://github.com/tcfialho/Herald.Ai.Skills --skill nexus2-arch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating and updating a comprehensive technical architecture document, ensuring consistency and clarity in architectural decisions.

Core Features & Use Cases

  • Architecture Specification: Produce nexus/architecture.md following a standardized template.
  • Decision Recording: Document architectural choices, including tools, stack, and non-functional requirements.
  • Use Case: A development team wants a clear, visual, and traceable architecture documentation for new project onboarding.

Quick Start

Call the nexus2-arch skill when starting a new project to generate the initial architecture document according to company standards.

Frequently Asked Questions about nexus2-arch

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

FAQPage Schema
How do I document software architecture decisions for a new project?

Documenting software architecture decisions involves recording technical choices, tools, and non-functional requirements in a standardized template. This skill generates a structured architecture document ensuring design consistency and traceability across multiple system layers.

What is the best way to create traceable technical decision records for software design?

Traceable technical decision records are created by logging architectural choices, technology stacks, and non-functional attributes within a centralized document. This skill facilitates structured planning to ensure all decisions are clearly documented and compliant with company standards.

How do I generate UML diagrams and system modeling documentation for project onboarding?

Generating UML diagrams and system modeling documentation requires mapping visual representations to architectural decisions. This skill produces a comprehensive architecture file covering diagrams, styles, and stacks to streamline new project onboarding for development teams.

Does this architecture documentation approach support non-functional requirements and multi-layer system modeling?

Yes, this architecture documentation approach supports non-functional requirements by explicitly capturing them alongside technical decisions. It covers multi-layer system modeling, ensuring visual diagrams and structural choices are consistently documented across all layers of the software project.

When do I need to use a standardized template for software architecture documentation?

A standardized template for software architecture documentation is needed when starting a new project to ensure consistency and clarity. It is essential for architecture teams and leads responsible for maintaining design consistency and compliance across the development lifecycle.

What are the limitations of using automated architecture documentation for software projects?

Automated architecture documentation focuses on generating the initial structure and standardized template for decisions and diagrams. It requires architecture teams to input accurate project specifics, as it does not replace the human reasoning needed for complex non-functional design trade-offs.