spex-architect

Design software architecture with bounded contexts, vertical slices, ADRs, and PRDs.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/johangm90/spex --skill spex-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spex-architect
Source: https://github.com/johangm90/spex/tree/main/skills/spex-architect
Command: npx skills add https://github.com/johangm90/spex --skill spex-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps define software architecture, create detailed slice specifications, and document critical design decisions, ensuring a clear and maintainable project structure.

Core Features & Use Cases

  • Architecture Definition: Designs bounded contexts, defines vertical slices, and writes Product Requirement Documents (PRDs).
  • Decision Recording: Authors Architecture Decision Records (ADRs) for significant technical choices.
  • Use Case: When starting a new project, use this Skill to outline the core bounded contexts, define the initial feature slices, and document the foundational architectural decisions.

Quick Start

Use the spex-architect skill to help plan a new application by defining its bounded contexts.

Frequently Asked Questions about spex-architect

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

FAQPage Schema
What is the best way to structure technical decision documentation for software design?

Architecture Decision Records (ADRs) document significant technical choices to ensure a clear and maintainable project structure. You should write an ADR when starting a new project to capture foundational architectural decisions and technical rationale.

How do I create vertical slice specifications for my software design?

Yes, you can bootstrap a new application by outlining core bounded contexts, defining initial feature slices, and generating a Product Requirement Document (PRD). This process establishes a clear architectural baseline and vertical slice specifications for the project.

What are the limitations of using bounded contexts for software architecture definition?

Yes, adhering to the MCP protocol is required for state management and artifact registration during architecture definition. This protocol ensures that bounded contexts, vertical slices, and Architecture Decision Records are consistently managed.

Are there specific prerequisites for managing state and artifact registration during architecture design?

Using bounded contexts for software architecture definition requires careful domain modeling to avoid tightly coupling slices. If domain boundaries are misaligned, vertical slice specifications may leak logic across contexts, complicating technical decision documentation and maintainability.