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…
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…
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…
Generate a comprehensive handover document at workflow close so the team can own, operate, and continue the system without re-running the workflow. Stage/phase/learning counts come from amadeus-runtime.ts summary; prose comes from the artefacts. Writes OUTCOMES.md but never mutates workflow state or emits audit events.
Print a structured session narrative for stakeholders who weren't in the room. Numbers (stage counts, phase rollup, duration) come from amadeus-runtime.ts summary; prose comes from the audit trail and artefacts. Renders to the terminal only — writes no file, never mutates workflow state, never emits audit events.
Read-only session cost view. Prints deterministic aggregates for the current workflow — duration, stage outcomes, memory entries, sensor firings, learnings captured — sourced entirely from amadeus-runtime.ts summary. Never mutates workflow state, never emits audit events, never writes files.
AI-DLC workflow orchestrator. Start, resume, or manage an AI-driven development lifecycle. Scopes are defined one file per scope under .claude/scopes/; run bun .claude/tools/amadeus-utility.ts help for the authoritative list and descriptions. Utilities: --status, --doctor, --migrate [path], --stage, --phase, --scope…
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: