Synthesize subsystem catalogs and architecture diagrams into comprehensive, navigable architecture reports - codifies synthesis strategies and professional documentation patterns
Create and manage NAF v4 (NATO Architecture Framework) / ADMBw Requirements Viewpoints (R2-R6) in Sparx Enterprise Architect. Use when the user wants to create R2 (Requirement Catalogue), R3 (Requirement Dependencies), R4 (Requirement Conformance), R5 (Requirement Derivation), or R6 (Requirement Realization) diagrams, add requirements elements, create associations between requirements, or work with NAF requirements modeling. Also triggers on natural language like "functional requirement", "requirement category", "derived from", "conforms to standard", etc.
Use when implementing distributed transactions, coordinating multi-service workflows, handling compensating transactions, or asking about "saga pattern", "distributed transactions", "compensating actions", "workflow orchestration", "choreography vs orchestration"
Diagnose design problems and guide architecture decisions for solo developers
Creates and manages C4 architecture diagrams using PlantUML. Use when the user wants to visualize software architecture, create context/container/component/sequence diagrams, document system design with the C4 model, or mentions architecture diagrams, system design, or PlantUML. Supports iterative diagram building through conversational workflow.
Deep planning philosophy for craftsman-level architecture. Transforms planning from research-then-design to research-question-simplify-design. Use when --deep flag is set, for epics, complex features (30+ tasks), or when auto_deep_mode preference is enabled. Invokes assumption questioning, codebase soul analysis, and ruthless simplification. (project)
Transform functional requirements into comprehensive technical architecture documents. Use when: (1) User provides specs/functional requirements needing technical design, (2) User asks for system architecture, data models, API design, (3) User says 'architect this' or 'create architecture for', (4) Starting a new project that needs technical foundation, (5) Translating business requirements into engineering specs. NOT for: task planning, project management, or implementation work.
Backend engineer focused on simplicity, bug elimination, and clean code. Use when user mentions "simplify backend", "fix backend bugs", "clean up code", or "make backend perfect".
Orchestrator skill for creating and maintaining the System Context (SSOT). Sequentially executes Observe, Orient, Decide, and Act phases. Representative use cases include (1) Defining initial system boundaries and domain models for a new project, (2) Realigning documentation with codebase reality to correct drift, and (3) Establishing a grounded SSOT foundation before initiating Architectural Decision Records (ADR).
Skill for creating C4 System Context Diagrams using Mermaid. Visualizes the system's boundaries, external actors (Users, External Systems), and high-level relationships.
Expert in making multi-agent systems resilient. Specializes in detecting loops, hallucinations, and failures, and implementing self-healing workflows. Use when designing error handling for agent systems, implementing retry strategies, or building resilient AI workflows.
Algorithmic decision tree for when to follow plan exactly vs when to report STOPPED - prevents scope creep and unauthorized deviations
Refine concept designs using six transformational moves. This skill should be used when improving existing concepts, addressing design trade-offs, or deciding between split/merge, unify/specialise, tighten/loosen approaches. Handles queries like "should I split this concept", "how to make concepts more flexible", "improve this concept design", "add more automation to concepts", "make concepts more general".
Apply Elon Musk-inspired system design thinking for research, engineering, and business workflows: rigorously challenge requirements, delete steps, simplify/optimize what remains, accelerate iteration, then automate. Use when designing or revising systems, processes, or products that need lean, high-velocity execution.
Guides the planning of a microservices architecture. Use this skill when asked to design, plan, or architect a system using microservices. This skill helps with service boundary identification, communication pattern selection, data management, and defining service contracts.
Shared standards for decision checkpoints, manifest shape, revisioning, reproducibility, and privacy across the process mining skill suite.
How to decompose a design into reviewable implementation stages. Use when planning how to implement multi-stage features, breaking down design documents into PRs, or reviewing implementation plans before starting work.
Use this skill when users need to create complex stateful D&R rules that correlate multiple events over time, track parent-child relationships, or count event occurrences within timeframes.
Orchestrate complex multi-phase projects using Ralph Loop coordination. Use when tasks require decomposition, multiple specialized roles (hats), event-driven coordination, or parallel workstreams. Triggers: "orchestrate", "coordinate loops", "plan and execute", "multi-phase project", "hat-based workflow", "decompose this task".
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.
Guides DDD discovery for the ToDo domain: ubiquitous language, bounded context, aggregates, invariants.
Design software concepts using Daniel Jackson's methodology. This skill should be used when analyzing existing applications to identify concepts, designing new concepts for features or systems, defining concept structure (purpose, operational principles, state, actions), or composing multiple concepts together. Handles queries like "design a concept for X", "what concepts does this app have", "help me model this feature as a concept".
