dev-taskRuns the managed, approval-gated workflow for one large, multi-file Feature-class change. Use when such a change needs that workflow or the user asks for it, such as building a new feature across several files, implementing an approved spec or tracker item end to end, or wanting a plan to approve be
feature-walkthroughRecords a browser walkthrough video of a finished web feature. Use when the user asks for, or accepts an offer of, a recorded walkthrough, demo video, or screen recording of a web feature. Not for native or simulator apps.
house-rulesProvides Studio Moser conventions for change classes, branches, file naming, commits, pull requests, testing, and pre-commit security checks. Use when naming a branch or file, writing a commit message or PR body, choosing tests for a change, or running the pre-commit security check.
ingestImports new Product Pulse daily, weekly, or deep-dive reports into the configured issue tracker. Use when new reports are ready to import. Not for triaging existing candidates or reconciling completed work.
reconcileReconciles the issue tracker against git history and current project state. Use when the tracker may be stale after merges or sprints, or for a periodic reality check. Not for deciding new items or implementing ready work.
setupConfigures PM's issue-tracker backend for a workspace. Use when PM is not yet configured or the user asks to reconfigure it.
shipCarries the current change, or someone else's pull request, to a ready-to-merge or merged PR without further check-ins: proves it, files the PR, watches checks and reviews, fixes findings, and asks only when blocked. Use when the user says "full stop" (stop when ready to merge) or "full send" (merge
sprint-devBuilds ready owner/ai backlog items from the configured tracker as one sprint. Use when the user asks for a sprint.
tidy-upCleans up the current repository after merged work: fetches the remote first, proves which branches, worktrees, and stashes are already in the base branch, integrates or keeps unmerged work, and deletes merged local and remote branches after one approved plan. Use when the user asks to tidy up, clea
triageMakes keep, reject, and deduplication decisions on `status/needs-triage` items and prepares kept items for execution. Use when items await triage. Not for raw-report ingestion, ready-item implementation, or tracker reconciliation.