project-onboarding
Project-specific onboarding context (roles, key flows, data sensitivity, how to run tests, and where the canonical docs live).
Explorez des skills pour le développement, le contenu, les données et la productivité. Comparez les descriptions et dépôts.
Project-specific onboarding context (roles, key flows, data sensitivity, how to run tests, and where the canonical docs live).
Create Linear ticket and PR for experimental features after implementation
Performs gap analysis between specs and code to generate IMPLEMENTATION_PLAN.md. Use when creating, updating, or regenerating the implementation plan.
Coordinate the multi-agent workflow across planning, validation, implementation, and verification.
Orchestrates 4-stage development workflow (PLAN → IMPLEMENT → TEST → FINAL)
Role - DevOps Engineer / Infrastructure
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Build and deploy Microsoft Power Automate flows using natural language. Use when working with Power Platform, PAC CLI, flow automation, or when users mention power automate, flows, or deployments.
端到端工作流編排器 - 串聯 RESEARCH → PLAN → IMPLEMENT → REVIEW → VERIFY
スマホレビュー向き作業の洗い出しとIssue作成。土日リモート対応用のタスクストックを作成。
Orchestrate complex tasks by delegating work to parallel subagent teams, preserving the main context window and preventing auto-compact. This skill should be used when users ask to apply subagent-teams, when pe...
Task groups and development planning. Use when managing task groups, development plans, or success criteria.
Team capacity planning, workload balancing, and resource management
Risk identification, assessment, and mitigation using the risk-tracker tool
Production incident response for GTS. Use for outages, degraded performance, security incidents, and emergency rollbacks.
Generate markdown reports from issues. Filter by type, priority, epic, date range. Supports summary, detailed, progress, completion, velocity, and backlog analysis views.
Use when executing implementation plans with independent tasks in the current session
Transition from brainstorming to rough-draft skill
Use when orchestrating a complete 9-phase development iteration. Activated by /superpowers-iterate:iterate command or when user asks to follow the iteration workflow.
This skill should be used when the user asks to "disaster recovery, backup strategy, failover, business continuity, RTO, RPO, recovery plan", or needs help with Backups, failover, business continuity.
This skill should be used when the user asks to "compare plan to implementation", "check plan adherence", "review against the plan", "how well does this match the plan", or wants to verify implementation follow...
Skill for breaking down goals into atomic, verifiable steps and managing them in .gemini/todo.md. Used when (1) creating a detailed step-by-step execution plan, (2) tracking progress of multi-step operations to...
A skill for conducting business requirement interviews and creating requirements definition documents. Understands client business challenges and converts them into measurable, implementable requirements.
Query and manage JIRA issues using the jira CLI. Search issues, view details, and transition statuses. READ-ONLY by default - always ask user approval before modifying issues.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.