@mmerterden/multi-agent-pipeline 8.6.0

package/pipeline/skills/shared/external/accessibility-compliance-accessibility-audit/SKILL.md

@@ -0,0 +1,45 @@
+---
+name: accessibility-compliance-accessibility-audit
+description: "You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct audits, identify barriers, and provide remediation guidance."
+risk: unknown
+source: community
+date_added: "2026-02-27"
+---
+
+# Accessibility Audit and Testing
+
+You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct comprehensive audits, identify barriers, provide remediation guidance, and ensure digital products are accessible to all users.
+
+## Use this skill when
+
+- Auditing web or mobile experiences for WCAG compliance
+- Identifying accessibility barriers and remediation priorities
+- Establishing ongoing accessibility testing practices
+- Preparing compliance evidence for stakeholders
+
+## Do not use this skill when
+
+- You only need a general UI design review without accessibility scope
+- The request is unrelated to user experience or compliance
+- You cannot access the UI, design artifacts, or content
+
+## Context
+
+The user needs to audit and improve accessibility to ensure compliance with WCAG standards and provide an inclusive experience for users with disabilities. Focus on automated testing, manual verification, remediation strategies, and establishing ongoing accessibility practices.
+
+## Requirements
+
+$ARGUMENTS
+
+## Instructions
+
+- Confirm scope (platforms, WCAG level, target pages, key user journeys).
+- Run automated scans to collect baseline violations and coverage gaps.
+- Perform manual checks (keyboard, screen reader, focus order, contrast).
+- Map findings to WCAG criteria, severity, and user impact.
+- Provide remediation steps and re-test after fixes.
+- If detailed procedures are required, open `resources/implementation-playbook.md`.
+
+## Resources
+
+- `resources/implementation-playbook.md` for detailed audit steps, tooling, and remediation examples.

package/pipeline/skills/shared/external/agentflow/SKILL.md

@@ -0,0 +1,199 @@
+---
+name: agentflow
+description: "Orchestrate autonomous AI development pipelines through your Kanban board (Asana, GitHub Projects, Linear). Manages multi-worker Claude Code dispatch, deterministic quality gates, adversarial review, per-task cost tracking, and crash-proof pipeline execution."
+risk: safe
+source: community
+date_added: "2026-04-02"
+---
+
+# AgentFlow
+
+## Overview
+
+AgentFlow turns your existing Kanban board into a fully autonomous AI development pipeline. Instead of building custom orchestration infrastructure, it treats your project management tool (Asana, GitHub Projects, Linear) as a distributed state machine — tasks move through stages, AI agents read and write state via comments, and humans intervene through the same UI they already use.
+
+The result is complete pipeline observability from your phone, free crash recovery (state lives in your PM tool, not in memory), and human override at any point by dragging a card.
+
+## When to Use This Skill
+
+- Use when you need to orchestrate multiple Claude Code workers across a full development lifecycle (build, review, test, integrate)
+- Use when you want deterministic quality gates (tsc/eslint/tests) before AI review on AI-generated code
+- Use when you want full pipeline visibility from your Kanban board or phone
+- Use when running a solo or team project that needs autonomous task dispatch with cost tracking
+- Use when you need crash-proof orchestration that survives session restarts
+
+## Core Concepts
+
+### 7-Stage Kanban Pipeline
+
+Tasks flow through: Backlog, Research, Build, Review, Test, Integrate, Done. Each stage has specific gates. The Kanban board IS the orchestration layer — no separate database, no message queue, no custom infrastructure.
+
+### Stateless Orchestrator
+
+A crontab-driven one-shot sweep runs every 15 minutes. No daemon, no session dependency. If it crashes, the next sweep picks up where it left off because all state lives in your PM tool.
+
+### Deterministic Before Probabilistic
+
+Hard gates (tsc + eslint + tests) run before any AI review, catching roughly 60% of issues at near-zero cost. AI review comes after, as a second layer.
+
+### Adversarial Review
+
+A different AI agent reviews code and must list 3 things wrong before deciding to pass. This prevents rubber-stamp approvals.
+
+### Transitive Priority Dispatch
+
+Tasks that unblock the most downstream work get built first, automatically computing the critical path.
+
+## Skills / Commands
+
+### `/spec-to-board`
+Decomposes a SPEC.md into atomic tasks on your Kanban board with dependencies mapped.
+
+### `/sdlc-orchestrate`
+Dispatches tasks to workers based on transitive priority and conflict detection. Runs as a crontab sweep.
+
+### `/sdlc-worker --slot <N>`
+Runs a worker in a terminal slot that picks up tasks, builds code, and creates PRs. Run 3-4 workers in parallel.
+
+### `/sdlc-health`
+Real-time pipeline status dashboard showing current stage, assigned agent, retry count, and accumulated cost for every task.
+
+### `/sdlc-stop`
+Graceful shutdown: active workers finish their current task, unstarted tasks return to Backlog.
+
+## Step-by-Step Guide
+
+### 1. Write Your Spec
+
+Create a `SPEC.md` for your project describing what you want to build.
+
+### 2. Decompose Into Tasks
+
+```
+claude -p "/spec-to-board"
+```
+
+This reads your SPEC.md, decomposes it into atomic tasks, maps dependencies, and creates them on your Kanban board.
+
+### 3. Start Workers
+
+Open 3-4 terminal windows, each as a worker slot:
+
+```bash
+# Terminal 2 — Builder
+claude -p "/sdlc-worker --slot T2"
+
+# Terminal 3 — Builder
+claude -p "/sdlc-worker --slot T3"
+
+# Terminal 4 — Reviewer
+claude -p "/sdlc-worker --slot T4"
+
+# Terminal 5 — Tester
+claude -p "/sdlc-worker --slot T5"
+```
+
+### 4. Start the Orchestrator
+
+```bash
+# Add to crontab (runs every 15 minutes)
+crontab -e
+# Add: */15 * * * * ~/.claude/sdlc/agentflow-cron.sh >> /tmp/agentflow-orchestrate.log 2>&1
+```
+
+### 5. Monitor and Intervene
+
+Open your Kanban board on your phone. Watch tasks flow through the pipeline. Drag any card to "Needs Human" to intervene. Run `/sdlc-health` for a terminal dashboard.
+
+### 6. Stop the Pipeline
+
+```
+claude -p "/sdlc-stop"
+```
+
+## Quality Gates
+
+Each stage enforces specific gates before promotion:
+
+- **Build to Review**: `tsc` + `eslint` + `npm test` must all pass (deterministic)
+- **Review to Test**: Adversarial reviewer must list 3 issues before passing
+- **Test to Integrate**: 80% coverage threshold on new files
+- **Integrate to Done**: Full test suite on main after merge; auto-reverts on failure
+
+## Cost Tracking
+
+Per-task cost tracking with stage ceilings (Sonnet defaults):
+
+- Research: ~$0.10
+- Build: ~$0.40
+- Review: ~$0.10
+- Test: ~$0.05
+- Integrate: ~$0.03
+
+Automatic guardrails: warning at $3/$8, hard stop at $10/$20 (Sonnet/Opus) with human escalation.
+
+## Safety and Recovery
+
+- **Auto-revert**: Integration failures trigger `git revert` (new commit, never force-push)
+- **Blocked tasks**: After 2 failed attempts, tasks escalate to human review
+- **Dead agent detection**: Heartbeat every 5 min, reassign after 10 min timeout
+- **Graceful shutdown**: `/sdlc-stop` drains workers, returns unstarted tasks to backlog
+- **Scope creep detection**: PR diff files compared against predicted files list
+- **Spec drift detection**: SHA-256 hash comparison catches requirement changes mid-sprint
+
+## Installation
+
+```bash
+# Clone the repo
+git clone https://github.com/UrRhb/agentflow.git
+
+# Copy skills and prompts to your Claude Code config
+cp -r agentflow/skills/* ~/.claude/skills/
+cp -r agentflow/prompts/* ~/.claude/sdlc/prompts/
+cp agentflow/conventions.md ~/.claude/sdlc/conventions.md
+```
+
+Or install as a Claude Code plugin:
+
+```bash
+/plugin marketplace add UrRhb/agentflow
+/plugin install agentflow
+```
+
+## Best Practices
+
+- Do: Write a clear SPEC.md before running `/spec-to-board`
+- Do: Start with 3-4 workers for a typical project
+- Do: Monitor from your Kanban board and drag cards to "Needs Human" when needed
+- Do: Review LEARNINGS.md periodically — it captures common failure patterns
+- Don't: Skip the deterministic quality gates — they catch most issues cheaply
+- Don't: Force-push to main — AgentFlow uses `git revert` for safety
+- Don't: Run more workers than your project's parallelism supports
+
+## Troubleshooting
+
+### Problem: Worker appears stuck or dead
+**Symptoms:** Task card hasn't moved in 15+ minutes, no new comments
+**Solution:** The orchestrator detects dead agents via heartbeat and reassigns after 10 minutes. If the issue persists, run `/sdlc-health` to check status and manually drag the card back to Backlog.
+
+### Problem: Cost guardrail triggered
+**Symptoms:** Task moved to "Needs Human" with COST:CRITICAL tag
+**Solution:** Review the task's comment thread for accumulated context. Decide whether to increase the budget, simplify the task, or split it into smaller pieces.
+
+### Problem: Integration test failure after merge
+**Symptoms:** Task auto-reverted from main
+**Solution:** The auto-revert preserves main stability. Check the task's retry context in comments, which carries what was tried and what failed. The next worker assigned will use this context.
+
+## Related Skills
+
+- `@brainstorming` - Use before AgentFlow to design your SPEC.md
+- `@writing-plans` - Complements spec writing for task decomposition
+- `@test-driven-development` - Works well with AgentFlow's quality gates
+- `@subagent-driven-development` - Alternative approach to multi-agent coordination
+
+## Additional Resources
+
+- [AgentFlow Repository](https://github.com/UrRhb/agentflow)
+- [Architecture Documentation](https://github.com/UrRhb/agentflow/blob/main/docs/architecture.md)
+- [Gap Registry (45 failure modes)](https://github.com/UrRhb/agentflow/blob/main/docs/gap-registry.md)
+- [Getting Started Guide](https://github.com/UrRhb/agentflow/blob/main/docs/getting-started.md)

package/pipeline/skills/shared/external/alarmkit/SKILL.md

@@ -0,0 +1,438 @@
+---
+name: alarmkit
+description: "Implement AlarmKit alarms and countdown timers for iOS and iPadOS with Lock Screen, Dynamic Island, and Apple Watch system UI. Covers AlarmManager scheduling, AlarmAttributes and AlarmPresentation, AlarmButton stop and snooze actions, authorization, state observation, and Live Activity integration. Use when building wake-up alarms, countdown timers, or alarm-style alerts that need Apple's system alarm experience."
+---
+
+# AlarmKit
+
+Schedule prominent alarms and countdown timers that surface on the Lock Screen,
+Dynamic Island, and Apple Watch. AlarmKit requires iOS 26+ / iPadOS 26+. Alarms override
+Focus and Silent mode automatically.
+
+AlarmKit builds on Live Activities -- every alarm creates a system-managed Live
+Activity with templated UI. You configure the presentation via `AlarmAttributes`
+and `AlarmPresentation` rather than building custom widget views.
+
+See `references/alarmkit-patterns.md` for complete code patterns including
+authorization, scheduling, countdown timers, snooze handling, and widget setup.
+
+```swift
+import AlarmKit
+```
+
+## Contents
+
+- [Workflow](#workflow)
+- [Authorization](#authorization)
+- [Alarm vs Timer Decision](#alarm-vs-timer-decision)
+- [Scheduling Alarms](#scheduling-alarms)
+- [Countdown Timers](#countdown-timers)
+- [Alarm States](#alarm-states)
+- [AlarmAttributes and AlarmPresentation](#alarmattributes-and-alarmpresentation)
+- [AlarmButton](#alarmbutton)
+- [Live Activity Integration](#live-activity-integration)
+- [Common Mistakes](#common-mistakes)
+- [Review Checklist](#review-checklist)
+- [References](#references)
+
+## Workflow
+
+### 1. Create a new alarm or timer
+
+1. Add `NSAlarmKitUsageDescription` to Info.plist with a user-facing string.
+2. Request authorization with `AlarmManager.shared.requestAuthorization()`.
+3. Configure `AlarmPresentation` (alert, countdown, paused states).
+4. Create `AlarmAttributes` with the presentation, optional metadata, and tint color.
+5. Build an `AlarmManager.AlarmConfiguration` (.alarm or .timer).
+6. Schedule with `AlarmManager.shared.schedule(id:configuration:)`.
+7. Observe state changes via `alarmManager.alarmUpdates`.
+8. If using countdown, add a widget extension target for non-alerting Live Activity UI.
+
+### 2. Review existing alarm code
+
+Run through the Review Checklist at the end of this document.
+
+## Authorization
+
+AlarmKit requires explicit user authorization. Without it, alarms silently
+fail to schedule. Request early (e.g., at onboarding) or let AlarmKit prompt
+automatically on first schedule.
+
+```swift
+let manager = AlarmManager.shared
+
+// Request authorization explicitly
+let state = try await manager.requestAuthorization()
+guard state == .authorized else { return }
+
+// Check current state synchronously
+let current = manager.authorizationState // .authorized, .denied, .notDetermined
+
+// Observe authorization changes
+for await state in manager.authorizationUpdates {
+    switch state {
+    case .authorized: print("Alarms enabled")
+    case .denied:     print("Alarms disabled")
+    case .notDetermined: break
+    @unknown default: break
+    }
+}
+```
+
+## Alarm vs Timer Decision
+
+| Feature | Alarm (`.alarm`) | Timer (`.timer`) |
+|---|---|---|
+| Fires at | Specific time (schedule) | After duration elapses |
+| Countdown UI | Optional | Always shown |
+| Recurring | Yes (weekly days) | No |
+| Use case | Wake-up, scheduled reminders | Cooking, workout intervals |
+
+Use `.alarm(schedule:...)` when firing at a clock time. Use `.timer(duration:...)`
+when firing after a duration from now.
+
+## Scheduling Alarms
+
+### Alarm.Schedule
+
+Alarms use `Alarm.Schedule` to define when they fire.
+
+```swift
+// Fixed: fire at an exact Date (one-time only)
+let fixed: Alarm.Schedule = .fixed(myDate)
+
+// Relative one-time: fire at 7:30 AM in device time zone, no repeat
+let oneTime: Alarm.Schedule = .relative(.init(
+    time: .init(hour: 7, minute: 30),
+    repeats: .never
+))
+
+// Recurring: fire at 6:00 AM on weekdays
+let weekday: Alarm.Schedule = .relative(.init(
+    time: .init(hour: 6, minute: 0),
+    repeats: .weekly([.monday, .tuesday, .wednesday, .thursday, .friday])
+))
+```
+
+### Schedule and Configure
+
+```swift
+let id = UUID()
+
+let configuration = AlarmManager.AlarmConfiguration.alarm(
+    schedule: .relative(.init(
+        time: .init(hour: 7, minute: 0),
+        repeats: .never
+    )),
+    attributes: attributes,
+    stopIntent: StopAlarmIntent(alarmID: id.uuidString),
+    secondaryIntent: SnoozeIntent(alarmID: id.uuidString),
+    sound: .default
+)
+
+let alarm = try await AlarmManager.shared.schedule(
+    id: id,
+    configuration: configuration
+)
+```
+
+### Alarm State Transitions
+
+```text
+cancel(id:)
+    |
+scheduled --> countdown --> alerting
+    |             |             |
+    |         pause(id:)    stop(id:) / countdown(id:)
+    |             |
+    |         paused ----> countdown (via resume(id:))
+    |
+cancel(id:) removes from system entirely
+```
+
+- `cancel(id:)` -- remove the alarm completely (any state)
+- `pause(id:)` -- pause a counting-down alarm
+- `resume(id:)` -- resume a paused alarm
+- `stop(id:)` -- stop an alerting alarm
+- `countdown(id:)` -- restart countdown from alerting state (snooze)
+
+## Countdown Timers
+
+Timers fire after a duration and always show a countdown UI. Use
+`Alarm.CountdownDuration` to control pre-alert and post-alert durations.
+
+```swift
+// Simple timer: 5-minute countdown, no snooze
+let timerConfig = AlarmManager.AlarmConfiguration.timer(
+    duration: 300,
+    attributes: attributes,
+    stopIntent: StopTimerIntent(timerID: id.uuidString),
+    sound: .default
+)
+
+let alarm = try await AlarmManager.shared.schedule(
+    id: UUID(),
+    configuration: timerConfig
+)
+```
+
+### CountdownDuration
+
+`Alarm.CountdownDuration` controls the visible countdown phases:
+
+- `preAlert` -- seconds to count down before the alarm fires (the main countdown)
+- `postAlert` -- seconds for a repeat/snooze countdown after the alarm fires
+
+```swift
+let countdown = Alarm.CountdownDuration(
+    preAlert: 600,   // 10-minute countdown before alert
+    postAlert: 300   // 5-minute snooze countdown if user taps Repeat
+)
+
+let config = AlarmManager.AlarmConfiguration(
+    countdownDuration: countdown,
+    schedule: .relative(.init(
+        time: .init(hour: 8, minute: 0),
+        repeats: .never
+    )),
+    attributes: attributes,
+    stopIntent: stopIntent,
+    secondaryIntent: snoozeIntent,
+    sound: .default
+)
+```
+
+## Alarm States
+
+Each `Alarm` has a `state` property reflecting its current lifecycle position.
+
+| State | Meaning |
+|---|---|
+| `.scheduled` | Waiting to fire (alarm mode) or waiting to start countdown |
+| `.countdown` | Actively counting down (timer or pre-alert phase) |
+| `.paused` | Countdown paused by user or app |
+| `.alerting` | Alarm is firing -- sound playing, UI prominent |
+
+### Observing State Changes
+
+```swift
+let manager = AlarmManager.shared
+
+// Get all current alarms
+let alarms = manager.alarms
+
+// Observe changes as an async sequence
+for await updatedAlarms in manager.alarmUpdates {
+    for alarm in updatedAlarms {
+        switch alarm.state {
+        case .scheduled:  print("\(alarm.id) waiting")
+        case .countdown:  print("\(alarm.id) counting down")
+        case .paused:     print("\(alarm.id) paused")
+        case .alerting:   print("\(alarm.id) alerting!")
+        @unknown default: break
+        }
+    }
+}
+```
+
+An alarm that disappears from `alarmUpdates` has been cancelled or fully stopped
+and is no longer tracked by the system.
+
+## AlarmAttributes and AlarmPresentation
+
+`AlarmAttributes` conforms to `ActivityAttributes` and defines the static
+data for the alarm's Live Activity. It is generic over a `Metadata` type
+conforming to `AlarmMetadata`.
+
+### AlarmPresentation
+
+Defines the UI content for each alarm state. The system renders a templated
+Live Activity using this data -- you do not build custom SwiftUI views for the
+alarm itself.
+
+```swift
+// Alert state (required) -- shown when alarm is firing
+let alert = AlarmPresentation.Alert(
+    title: "Wake Up",
+    secondaryButton: AlarmButton(
+        text: "Snooze",
+        textColor: .white,
+        systemImageName: "bell.slash"
+    ),
+    secondaryButtonBehavior: .countdown  // snooze restarts countdown
+)
+
+// Countdown state (optional) -- shown during pre-alert countdown
+let countdown = AlarmPresentation.Countdown(
+    title: "Morning Alarm",
+    pauseButton: AlarmButton(
+        text: "Pause",
+        textColor: .orange,
+        systemImageName: "pause.fill"
+    )
+)
+
+// Paused state (optional) -- shown when countdown is paused
+let paused = AlarmPresentation.Paused(
+    title: "Paused",
+    resumeButton: AlarmButton(
+        text: "Resume",
+        textColor: .green,
+        systemImageName: "play.fill"
+    )
+)
+
+let presentation = AlarmPresentation(
+    alert: alert,
+    countdown: countdown,
+    paused: paused
+)
+```
+
+### AlarmAttributes
+
+```swift
+struct CookingMetadata: AlarmMetadata {
+    var recipeName: String
+    var stepNumber: Int
+}
+
+let attributes = AlarmAttributes(
+    presentation: presentation,
+    metadata: CookingMetadata(recipeName: "Pasta", stepNumber: 3),
+    tintColor: .blue
+)
+```
+
+### AlarmPresentationState
+
+`AlarmPresentationState` is the system-managed `ContentState` of the alarm
+Live Activity. It contains the alarm ID and a `Mode` enum:
+
+- `.alert(Alert)` -- alarm is firing, includes the scheduled time
+- `.countdown(Countdown)` -- actively counting down, includes fire date and durations
+- `.paused(Paused)` -- countdown paused, includes elapsed and total durations
+
+The widget extension reads `AlarmPresentationState.mode` to decide which UI to
+render in the Dynamic Island and Lock Screen for non-alerting states.
+
+## AlarmButton
+
+`AlarmButton` defines the appearance of action buttons in the alarm UI.
+
+```swift
+let stopButton = AlarmButton(
+    text: "Stop",
+    textColor: .red,
+    systemImageName: "stop.fill"
+)
+
+let snoozeButton = AlarmButton(
+    text: "Snooze",
+    textColor: .white,
+    systemImageName: "bell.slash"
+)
+```
+
+### Secondary Button Behavior
+
+The secondary button on the alert UI has two behaviors:
+
+| Behavior | Effect |
+|---|---|
+| `.countdown` | Restarts a countdown using `postAlert` duration (snooze) |
+| `.custom` | Triggers the `secondaryIntent` (e.g., open app) |
+
+## Live Activity Integration
+
+AlarmKit alarms automatically appear as Live Activities on the Lock Screen
+and Dynamic Island on iPhone, and in the Smart Stack on Apple Watch. The
+system manages the alerting UI. For countdown and paused states, add a
+widget extension that reads `AlarmAttributes` and `AlarmPresentationState`.
+
+A widget extension is **required** if your alarm uses countdown presentation.
+Without it, the system may dismiss alarms unexpectedly.
+
+```swift
+struct AlarmWidgetBundle: WidgetBundle {
+    var body: some Widget {
+        AlarmActivityWidget()
+    }
+}
+
+struct AlarmActivityWidget: Widget {
+    var body: some WidgetConfiguration {
+        ActivityConfiguration(for: AlarmAttributes<CookingMetadata>.self) { context in
+            // Lock Screen presentation for countdown/paused states
+            AlarmLockScreenView(context: context)
+        } dynamicIsland: { context in
+            DynamicIsland {
+                DynamicIslandExpandedRegion(.center) {
+                    Text(context.attributes.presentation.alert.title)
+                }
+                DynamicIslandExpandedRegion(.bottom) {
+                    // Show countdown or paused info based on mode
+                    AlarmExpandedView(state: context.state)
+                }
+            } compactLeading: {
+                Image(systemName: "alarm.fill")
+            } compactTrailing: {
+                AlarmCompactTrailing(state: context.state)
+            } minimal: {
+                Image(systemName: "alarm.fill")
+            }
+        }
+    }
+}
+```
+
+## Common Mistakes
+
+**DON'T:** Forget `NSAlarmKitUsageDescription` in Info.plist.
+**DO:** Add a descriptive usage string. Without it, AlarmKit cannot schedule alarms at all.
+
+**DON'T:** Skip authorization and assume alarms will schedule.
+**DO:** Call `requestAuthorization()` early and handle `.denied` gracefully.
+
+**DON'T:** Use `.timer` when you need a recurring schedule.
+**DO:** Use `.alarm` with `.weekly([...])` for recurring alarms. Timers are one-shot.
+
+**DON'T:** Omit the widget extension when using countdown presentation.
+**DO:** Add a widget extension target. AlarmKit requires it for countdown/paused Live Activity UI.
+**Why:** Without a widget extension, the system may dismiss alarms before they alert.
+
+**DON'T:** Ignore `alarmUpdates` and track alarm state manually.
+**DO:** Observe `alarmManager.alarmUpdates` to stay synchronized with the system.
+**Why:** Alarm state can change while your app is backgrounded.
+
+**DON'T:** Forget to provide a `stopIntent` -- it cannot be nil in practice.
+**DO:** Always provide a `LiveActivityIntent` for stop so the button performs cleanup.
+
+**DON'T:** Store large data in `AlarmMetadata`. It is serialized with the Live Activity.
+**DO:** Keep metadata lightweight. Store large data in your app and reference by ID.
+
+**DON'T:** Use deprecated `stopButton` parameter on `AlarmPresentation.Alert`.
+**DO:** Use the current `init(title:secondaryButton:secondaryButtonBehavior:)` initializer.
+
+## Review Checklist
+
+- [ ] `NSAlarmKitUsageDescription` present in Info.plist with non-empty string
+- [ ] Authorization requested and `.denied` state handled in UI
+- [ ] `AlarmPresentation` covers all relevant states (alert, countdown, paused)
+- [ ] Widget extension target added if countdown presentation is used
+- [ ] `AlarmAttributes` metadata type conforms to `AlarmMetadata`
+- [ ] Alarm ID stored for later cancel/pause/resume/stop operations
+- [ ] `alarmUpdates` async sequence observed to track state changes
+- [ ] `stopIntent` and `secondaryIntent` are valid `LiveActivityIntent` implementations
+- [ ] `postAlert` duration set on `CountdownDuration` if snooze (`.countdown` behavior) is used
+- [ ] Tint color set on `AlarmAttributes` to differentiate from other apps
+- [ ] Error handling for `AlarmManager.AlarmError.maximumLimitReached`
+- [ ] Tested on device (alarm sound/vibration differs from Simulator)
+
+## References
+
+- Patterns and code: `references/alarmkit-patterns.md`
+- Apple docs: [AlarmKit](https://sosumi.ai/documentation/alarmkit) |
+  [AlarmManager](https://sosumi.ai/documentation/alarmkit/alarmmanager) |
+  [AlarmAttributes](https://sosumi.ai/documentation/alarmkit/alarmattributes) |
+  [Scheduling an alarm](https://sosumi.ai/documentation/alarmkit/scheduling-an-alarm-with-alarmkit)