Build, sign, notarize, and publish a new macOS ScreenCap.app release (.dmg). Bumps the app version, builds the embedded daemon with PyInstaller, builds the app with Xcode, Developer-ID signs + notarizes + staples, packages a DMG, tags `macos-app-vX.Y.Z`, and creates a GitHub prerelease. This is the app track — distinct from `local-release` (the headless CLI/`vX.Y.Z` track). Triggers on "release the macOS app", "new app release", "build a new DMG", "ship the app to testers", or after Swift/UI or embedded-daemon changes land.
Bump version, build, and release screencap locally. Mirrors the /release flow (version bump, changelog, commit, tag, push) but builds locally instead of triggering GH Actions. Supports arm64 (native on Apple Silicon), x86_64 (requires python.org universal2 Python 3.12 + Rosetta), and both. Use when CI is unavailable (billing limits, runner outages). Triggers on "local release", "release locally", "build and release", or when CI release fails.
Pick the highest-priority ready-to-start Linear ticket on the Screencap team, claim it (assign + move to In Progress / Planning), and hand off into the right Compound Engineering skill (ce-debug / ce-work / ce-plan) primed with the ticket. Flags too-thin tickets with needs-info instead of starting them. Use when you want to start the next piece of work without manually triaging the backlog. Triggers on "next ticket", "what's next", "pick a ticket", "pick the next ticket", "start next work", "grab a ticket", "work the next ticket".
End-to-end capture pipeline sanity check. Runs a real screencap recording, asks the user to perform actions, then validates the captured data (files, DB, screenshots). Use when testing capture changes, verifying the recording pipeline works, or after modifying recorder/catalog code. Triggers on "test capture", "capture test", "sanity check", "test recording pipeline", or after changes to recorder.py, catalog.py, or screencap.engine.
List all open tickets with status and priority. Shows what's pending, in-progress, blocked, or planned. Sorted by priority (urgent > high > medium > low > unset). Use when you want to see the ticket backlog, check what's blocked, find work to do, or get a status overview. Triggers on "list tickets", "ticket status", "what's open", "what needs work", "backlog", "show tickets", "ticket overview", "what's blocked".
Scan docs/ for plans, tickets, research, brainstorms, and decisions, then display them organized by topic. Shows open vs archived counts, item types, and priorities. Use when you want a project overview, need to find existing work, or want to see what's planned. Triggers on "review docs", "show docs", "what's planned", "project overview", "list tickets", "list plans", "docs overview".
Document a solved problem, completed feature, porting decision, or architecture learning to compound team knowledge. Auto-triggers on "that worked", "it's fixed", "feature complete", "porting done". Creates one MD file per item in docs/solutions/[category]/. Use after research, planning, implementation, or debugging sessions.
Record product decisions and requirements from team conversations. Use when new decisions are made, requirements change, priorities shift, or someone says "let's do X instead of Y." Triggers on "track decision", "new decision", "record this decision", "add requirement", "update requirements", "new requirement", "priority change", or when team conversation context contains a product/architecture decision that should be preserved.