code-review
Expert code review specialist for quality, security, and maintainability. Use when reviewing code changes, ensuring high development standards, or conducting security audits. Provides actionable feedback organi...
Discover devops project management skills, compare source repositories and read the instructions for each workflow.
Expert code review specialist for quality, security, and maintainability. Use when reviewing code changes, ensuring high development standards, or conducting security audits. Provides actionable feedback organi...
Scan conductor/ directory for project direction, workflows, and task planning when present
Use when a task requires a spec-driven workflow: draft/refresh PRD + TECH_SPEC + ACTION_PLAN + tasks, link TECH_SPEC in tasks/index.json, and run docs-review before implementation.
Developer Experience specialist for tooling, setup, and workflow optimization. Use when setting up projects, reducing friction, improving development workflows, or automating repetitive tasks. Focuses on making...
Spawn subagents early and often to conserve context and parallelize research, review, and planning.
Automatically activated when user mentions sprint planning, backlog refinement, iteration planning, sprint goals, capacity planning, velocity tracking, or asks to plan/start/close a sprint. Provides comprehensi...
Use PROACTIVELY to document new features, significant code changes, or when creating technical specifications for a feature not included in the original project technical specification. Specializes in creating...
Refine and clarify PRDs via structured AskUserQuestion sessions. Use when a PRD is ambiguous, missing acceptance criteria, or needs scoped clarification before planning.
Generate a lite architecture snapshot from a PRD with a minimal component list, primary flow, and top risks. Use when you need demo-grade architecture guidance without full governance overhead.
Generate a phased roadmap from a PRD with goals, dependencies, and validation gates. Use when sequencing and milestone logic must be explicit without dates.
Plan and review product scope, value, metrics, and rollout via a structured interview. Use when product direction or scope must be clarified.
Create or review PRDs/tech specs for product ideas; use when you need structured requirements, UX spec, and build plan, especially for high-risk scopes.
Generate a risk register and mitigation plan from a PRD, covering product, security, delivery, and dependency risks. Use when risks must be explicitly enumerated and owned.
Generate a performance plan from a tech spec with budgets, load tests, thresholds, and monitoring. Use when performance targets must be explicit and verifiable.
Manage Google Jules PR lifecycle - batch investigation, reverse-order processing, and tiered decision presentation.
This skill should be used for Jira backlog refinement via text conversation. It pulls non-ready tickets, facilitates requirements discussion, and marks tickets ready when complete.
Anime.js animation patterns for web interfaces including timelines, staggering, and motion design.
Structured workflow for co-authoring documentation, PRDs, technical specs, and decision docs. Use when writing substantial documentation, creating proposals, drafting specifications, or any structured content t...
Query Prometheus metrics, Loki logs, and Grafana dashboards for diagnostics and incident response.
React and Next.js performance optimization guidelines. Use when writing, reviewing, or refactoring React/Next.js code. Applies to Blaze (web), Spark (desktop), and Tap (mobile) agents.
Compound Engineering methodology - Plan→Work→Review→Compound loop where each unit of work makes subsequent work easier. Use when implementing features, fixing bugs, or any development work.
Adapt UI scheduling behavior dynamically based on runtime conditions and user context.
複雑なタスク(3ステップ以上・複数ファイル変更)の実装前に使用。計画ファイルを作成し進捗を追跡。
專案管理:敏捷開發、Scrum、甘特圖、風險管理、團隊協作
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.