System design, architecture decisions, and technical planning. Use when evaluating trade-offs, designing a feature or module, making refactoring or library choices, or before any task touching 3+ files that needs a plan first.
Expert code review for correctness, conventions, performance, and maintainability. Use after a build phase, on a PR, or when asked for a second opinion on code quality.
Marketing strategy, positioning, copywriting, SEO, CRO, and content creation. Works as a peer to the PM — not a subordinate. Gives the product/market direction while the PM gives the technical direction. Use PROACTIVELY when: working on landing pages, pricing pages, social media posts, email sequences, SEO…
DevOps, SRE, and FinOps specialist for infrastructure, CI/CD, deployment, monitoring, and cost optimization. Use for CI/CD pipelines, Dockerfiles, infrastructure-as-code, monitoring/alerting, cloud-cost work, deployment troubleshooting, or environment configuration.
Operations monitor and first responder. Reads diagnostics, scheduled-task outputs, and monitoring data, triages issues, recommends severity, and assists with remote fixes. Use to process a diagnostic, triage an alert, or investigate a production issue.
QA specialist for test strategy, edge cases, regression testing, and coverage. Use to validate coverage after a build, find missing tests during review, add regression tests for a bug, or design a test strategy for a new module.
Application security auditor and red team specialist. Use when reviewing auth/authorization, billing/payment, data handling, internet-exposed endpoints, cryptographic operations, or any security-sensitive code.
Product Manager for autonomous sprint orchestration. Plans sprints, makes product decisions, executes sprint cycles, and updates project state. Use PROACTIVELY when: planning what to build next, prioritizing backlog items, making product decisions, or orchestrating sprint execution. Also use when the user says "plan…
Tech Lead and QA reviewer for autonomous sprint orchestration. Reviews completed sprints, challenges PM decisions, runs smoke tests, and ensures quality standards. Use PROACTIVELY when: a sprint completes, sprint output files are present, reviewing PM decisions, or when quality validation is needed. Also use when the…
Ship and capture lessons workflow. Creates the PR, updates lessons learned, updates documentation, generates the sprint retrospective, and updates the backlog. Use at the end of a sprint cycle, or when the user says "ship", "capture", "lessons", "retro", "retrospective", "wrap up", or "done with this sprint". Also use…
Generate changelogs, release notes, and feature announcements from sprint artifacts. Use when a sprint is complete and needs to be communicated to users. Also use when the user says "changelog", "release notes", "what's new", "announce this", "communicate this feature", "write the update", or after a capture-lessons…
Fetch, query, and analyze project data. Use this skill when the user wants to investigate metrics, understand user behavior, debug a data issue, or answer a question that requires looking at real data. Triggers on "what happened", "why did X drop", "show me the numbers", "query", "metrics", "funnel", "cohort", "data"…
Fix phase workflow. Fixes issues identified during code review, based on the triaged review output. Use after a review phase is complete and the human has triaged the findings, or when the user says "fix", "fix the issues", "address review feedback", or "apply fixes". Also use when the user says "fix these" after…
Orchestrates a complete sprint cycle autonomously. Each phase runs as a separate claude -p session for context isolation. Use when the sprint-directive.md is ready and the sprint should execute end-to-end. Also use when the user says "run a full sprint", "execute the sprint", "build everything", "autonomous sprint"…
Synchronize product state with marketing strategy. Use after sprints ship, when user feedback arrives, or when the marketing-context needs updating. Also use when the user says "sync marketing", "update positioning", "what should we communicate", "user feedback review", "marketing brief", or "prepare marketing for…
Quick monitoring briefing. Reads all reports in monitoring/ and tasks/backlog.md, produces a 5-10 line status summary. Designed for remote use via Telegram/Channels. Use when the user says "status", "monitoring", "bilan", "what's the state", "any alerts", or "how's the project".
Drive the running product and verify it works end-to-end. Use this skill after a deploy, before a release, or when the user says "verify", "smoke test", "does it work", "test the flow", "check staging", "end-to-end test", or "drive the product". Also use when the user wants to verify a specific user journey (signup…
Security red team that produces executable attack scripts and a static code audit. Use this skill for any security sprint, pre-release hardening, or when code touches authentication, billing, data storage, API endpoints, or secrets. Also use when the user says "red team", "pentest", "attack surface", "security audit"…
Remote fix workflow. Receives a diagnostic (from Cowork scheduled task, manual observation, or user report), investigates the issue, fixes it, and creates a PR. Designed for quick fixes triggered remotely via Channels (Discord/Telegram). Use when the user says "fix this", "handle this diagnostic", "the scheduled task…
Code review workflow. Reviews the build output for quality, conventions, performance, security, and test coverage. Use after a build phase is complete, or when the user says "review", "check the code", "PR review", "quality check", or "is this good". Also use when the user wants a second opinion on code that was just…
Investigate production issues from symptom to structured report. Use this skill when something is broken, slow, or behaving unexpectedly in production or staging. Triggers on "it's broken", "users are reporting", "alert fired", "error in prod", "why is X slow", "investigate", "incident", "outage", "debug production"…
Generate project-specific boilerplate and scaffolding. Use this skill when the user wants to create a new module, service, endpoint, command, component, migration, or any structural unit that follows the project's patterns. Triggers on "new endpoint", "new command", "add a route", "create a component", "scaffold"…
Post-sprint validation. Verifies the application works as expected after a sprint completes. Use after any sprint or deployment, or when the user says "smoke test", "verify it works", "test the app", "does it still work", "regression check", "post-deploy check", or "sanity check". Invoked by SP-QA during post-sprint…
Sprint planning workflow. Creates a structured plan from the backlog with tasks, acceptance criteria, dependencies, and risks. Use when starting a new sprint, planning work, or when the user says "plan", "sprint", "what should we work on", or "next sprint". Always use this skill to start a sprint cycle — never plan…
★not rated 5 3mo agoA75 tokens
originalApache-2.0
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: