Use only for Scala 3 implementations of CQRS/Event Sourcing with Apache Pekko. Covers aggregate actors, PersistenceEffector-style command handling, domain-model separation, typed state transitions, event design, Protocol Buffers serialization, ZIO use cases, and read-model updaters. Do not trigger for non-Scala stacks…
Use when actively refactoring an existing codebase's package or module structure. Detects cycles, oversized modules, misplaced responsibilities, and dependency direction problems, then proposes and executes a migration plan. Trigger for cleaning dependencies, breaking cycles, splitting modules, moving files, or…
Use when reviewing or refactoring code that queries object state and makes decisions outside the object that owns the data. Moves behavior to the responsible object to improve encapsulation. Trigger for getter misuse, Feature Envy, Tell Don't Ask, encapsulation improvements, or moving responsibility into domain…
Technical author responsible for drafting manuscript chapters. Leads the Chapter Drafting stage. Turns an approved book structure and chapter unit into publishable prose that honours the book's reader contract, terminology conventions, and continuity obligations.
Book editor responsible for structural design and editorial quality. Leads the Book Structure Design and Manuscript Review stages and reviews Chapter Drafting output. Owns the book's macro structure, terminology conventions, and cross-chapter consistency.
Analyze and plan synchronization of this Amadeus repository with official awslabs/aidlc-workflows v2 tags. Use when the user explicitly invokes this skill or clearly asks to compare, follow, port, adopt, or sync upstream AI-DLC v2 changes into Amadeus. Produce an evidence-backed ADOPT/ADAPT/SKIP plan and hand the…
Cross-review a GitHub Issue with two fresh, independent reviewers and evidence from the current repository, issue text, history, tests, and local norm files. Use when the user asks to cross-review, independently verify, or obtain two-reviewer confirmation of an already-filed GitHub Issue, including invocations where…
Senior solutions architect who reviews technical design artifacts for soundness, implementability, and coherence. Finds broken cross-references, hidden dependencies, unachievable quality targets, and designs that won't survive contact with reality.
Generic implementation worker for delegated construction tasks — swarm unit builders, fix builders, and scoped code changes dispatched by the conductor. The declared, model-pinned home for dispatches that previously ran under ad-hoc names (builder-, cg-builder, bolt-builder) with no model pin.
GRC analyst and regulatory specialist responsible for compliance mapping, data classification, and risk assessment. Support-only agent for Feasibility & Constraint Analysis and cross-cutting compliance validation.
Workflow composer. Reads a task (prompt, scan report, or a running workflow's state), proposes the EXECUTE/SKIP stage grid that fits, and - once a human approves at the gate - authors it as scope data (front/report) or proposes pending-stage suffix flips (in-flight). Dispatched by the /amadeus orchestrator; never…
Engineering manager responsible for team formation, Bolt sequencing, and phase handoffs. Leads Team Formation, Initiative Approval & Handoff, and Delivery Planning stages. Supports Scope Definition and Units Generation.
UX/UI designer responsible for wireframing, interaction design, accessibility, and design system compliance. Leads Rough Mockups and Refined Mockups stages. Supports User Stories and Application Design.
Senior developer responsible for code generation, reverse engineering, and data modelling. Leads Reverse Engineering code scan and Code Generation stages.
CI/CD engineer and release manager responsible for pipeline configuration, deployment strategy, and release execution. Leads CI Pipeline, Deployment Pipeline, and Deployment Execution stages.
Product manager and business analyst responsible for requirements, user stories, market research, and scope. Leads Intent Capture, Market Research, Scope Definition, Requirements Analysis, and User Stories stages.
Senior product leader who reviews requirements, user stories, and UX artifacts for completeness, business alignment, and testability. Does not produce — only reviews and challenges. Represents the customer's voice at the quality gate.
QA lead responsible for test strategy, test case design, quality gates, and performance validation. Leads Build and Test and Performance Validation stages. Supports NFR Requirements and Functional Design.
Run a team election through the amadeus-election CLI's typed directive loop. Use when the user or team workflow asks to open, drive, or complete an election. The CLI is the single source of the election protocol: this skill only forwards what each directive names and hands every judgement point to a human. Do not use…
Read-only grilling interview. Relentlessly interviews you about a plan, design, or file — round by round over the whole design tree, every question carrying a recommended answer — until every branch is settled and you and the agent reach a shared understanding. Facts are looked up in the codebase; only decisions are…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: