Generates a sprint or milestone retrospective by analyzing completed work, velocity, blockers, and patterns. Produces actionable insights for the next iteration. Use at sprint end, milestone close, or after a missed deadline.
Generates a PRD or architecture doc from existing implementation — works backward from code to the doc that should have been written first. Use this for brownfield projects with working code but no design docs, or when a feature shipped without a PRD.
Holistic cross-PRD review — reads every PRD together to find contradictions, dominant strategies, cognitive overload, broken funnels, and missing-system gaps that single-PRD review cannot detect. Run after all MVP PRDs are individually approved, before architecture begins.
Compares current sprint or feature scope against the original plan to detect scope creep. Quantifies bloat, names additions, recommends cuts. Use mid-sprint when the team feels overloaded, or before adding a 'small' new story to a running sprint.
Audit the app for vulnerabilities: insecure storage, improper TLS, OWASP MASVS coverage, dependency CVEs, exposed secrets, unsafe deep links, JS-bridge exploits, WebView attack surface. Produces a prioritized remediation report. Run before any public release.
Pins the project's mobile framework (React Native, Flutter, iOS native, Android native), captures the version, populates docs/framework-reference/ /, and writes the Framework field to technical-preferences.md and CLAUDE.md. Use this once during early onboarding before any PRD or ADR authoring. Knowledge-cutoff aware…
Improve a SKILL.md file via static lint, fix proposal, rewrite, and re-test loop. Runs structural checks, proposes targeted fixes, applies them, re-tests, and either keeps or reverts based on score change.
Validates skill files for structural compliance and behavioral correctness in three modes (static lint / spec / audit). Use this before publishing skill changes or to audit the whole skill library for drift.
Run the critical-path smoke gate before QA hand-off. Executes the automated suite, verifies the core user flows defined in the QA plan, and produces a PASS/FAIL report. A failed smoke check means the build is not ready for QA.
Generate a soak-test protocol for extended app sessions. Defines what to observe and log during long sessions to surface memory leaks, battery drain, background-foreground crashes, and network flapping. Used in Polish and Release phases.
Generates a new sprint plan or updates an existing one based on the current milestone, completed work, and team capacity. Pulls context from production docs and the story backlog. Run at sprint start, sprint mid-correction, or after a milestone shift.
Fast sprint status check — reads the active sprint plan, scans story files for status, and produces a concise progress snapshot with burndown read and emerging risks. Use any time during a sprint for situational awareness.
First-time onboarding for the mobile app studio template. Asks where the user is starting from, classifies them, and routes them to the right next skill. Use this on the very first session, or whenever the project feels unmoored.
End-of-story completion review. Verifies each acceptance criterion against the implementation, surfaces deviations, prompts code review if not yet done, marks the story Complete, and surfaces the next ready story. Use after /code-review.
Validates that a story file is implementation-ready — checks for embedded TR-ID, ADR references, framework notes, clear acceptance criteria, no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict. Use before /dev-story to confirm a story can be started safely.
Orchestrate the server / data side of a feature. Coordinates backend-engineer, api-designer, database-specialist, offline-sync-specialist, push-notification-specialist, and firebase-specialist for the data layer.
Orchestrate the content pipeline. Coordinates content-strategist, content-designer, localization-lead, and ux-designer to take a content brief from concept through written, localized, and shipped state.
Orchestrate a full design cycle. Coordinates lead-designer, ux-designer, visual-design-director, interaction-designer, and motion-designer to take a feature from brief through to implementation-ready specs.
Orchestrate the mobile UI build. Coordinates lead-developer, framework specialist (RN/Flutter/iOS/Android), state-management specialist, and animation-specialist to ship a feature's frontend layer end-to-end.
Orchestrate the live-ops team for post-launch content planning. Coordinates live-ops-designer, monetization-designer, analytics-engineer, community-manager, and content-strategist to plan a season, event, or live update.
Orchestrate the polish phase. Coordinates performance-analyst, accessibility-specialist, animation-specialist, qa-tester, and content-designer to harden a feature or area to release quality.
Orchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + sign-off) and qa-tester (test cases + bug reports) for a sprint or feature. Covers plan, smoke gate, manual execution, bug filing, and sign-off.
Orchestrate the release team: release-manager, qa-lead, mobile-devops, and producer. Drives a release from candidate through certification, rollout, and post-launch monitoring.
Track, categorize, and prioritize technical debt across the codebase. Scans for debt indicators (TODO, FIXME, deprecated APIs, version-skew, dead flags, stale dependencies), maintains a debt register, and recommends repayment scheduling.
★not rated 42▲
+1 5mo agoA50 tokens
originalMIT
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: