GitHub
retrospective
Conducts retrospectives, archives items, and reprioritizes backlog
Skills IA databases project management
Découvrez les skills databases project management, comparez leurs dépôts et consultez leurs instructions.
Catégories: databases project management
databases project management Effacer les filtres
Explorer
GitHub
scan-prioritize
Scans repository and builds priority queue
GitHub
task-scanner-agent
Scans infrastructure task repositories for active and backlog tasks, builds priority queue based on criticality and dependencies
GitHub
project-context
Provides current project state, architecture overview, and structured metadata
GitHub
reflect
Reflect on a session to identify learnings, friction points, and improvements. Captures valuable insights for future sessions and system evolution.
GitHub
jira-task
Creates Jira tasks following Prowler's standard format. Trigger: When user asks to create a Jira task, ticket, or issue.
GitHub
mixseek-config-validate
MixSeekの設定ファイル（team.toml、orchestrator.toml、evaluator.toml、judgment.toml）を検証します。「設定を検証」「TOMLをチェック」「設定ファイルの確認」「バリデーション」「ワークスペースの検証」といった依頼で使...
GitHub
mixseek-evaluator-config
MixSeekの評価設定ファイル（evaluator.toml、judgment.toml）を生成します。「評価設定を作成」「スコアリング設定」「判定設定を作って」「メトリクスを設定」といった依頼で使用してください。Submissionの評価基準と最終判...
GitHub
mixseek-orchestrator-config
MixSeekのオーケストレーター設定ファイル（orchestrator.toml）を生成します。「オーケストレーターを設定」「チーム競合設定」「複数チームで競わせる」「マルチチーム実行設定」といった依頼で使用してください。複数チーム...
GitHub
spec-plan
Translate an approved plan into specs with acceptance criteria and derived tasks. Use after plan mode when transitioning to implementation.
GitHub
jira-epic
Creates Jira epics for large features following Prowler's standard format. Trigger: When user asks to create an epic, large feature, or multi-task initiative.
GitHub
commit-push-pr-flow
タスク完了後に自律的に実行する必要があるフロースキルです。 Trigger: task completed, ready to submit code
GitHub
worktree
Planが承認/完了した直後に自律的に呼び出す必要があるスキルです。 Trigger: plan approved, plan completed, taskを開始します
GitHub
mixseek-team-config
MixSeekのチーム設定ファイル（team.toml）を生成します。「チームを作成」「エージェント設定を生成」「Web検索チームを作って」「分析チームを設定」といった依頼で使用してください。Leader AgentとMember Agentの構成を定...
GitHub
review-code
Provides a structured workflow for planning and executing code reviews like a senior engineer. Use when asked to review code, PRs, or plan a code review task.
GitHub
managing-workflow
Manages the specification-driven development workflow. Use this skill when the user runs /orbit, requests to "define feature", "create plan", "implement", or needs workflow guidance. It detects the current phas...
GitHub
health-bugs
Inline orchestration workflow for automated bug detection and fixing with Beads integration. Provides step-by-step phases for bug-hunter detection, history enrichment for priority bugs, priority-based fixing wi...
GitHub
create-plan
Creates comprehensive implementation plans through codebase exploration, research, and iterative clarification. Use when asked to plan, design, architect, or figure out how to implement a feature, refactor, or...
GitHub
memory-bank
Persistent project documentation system that maintains context across sessions. Creates structured Memory Bank files to preserve project knowledge, decisions, and progress.
GitHub
jira
Use for all Jira-related tasks. When user mentions a ticket (PROJ-123) or shares a Jira URL, use the jira CLI instead of web fetching.
GitHub
plan
Guidelines for iteratively planning tasks and changes before implementation. Use this when the user requests a non-trivial task or when you need to align on a complex implementation strategy.
GitHub
wip-lifecycle-manager
Manage WIP document lifecycle: create, track, review, and archive work-in-progress documentation; use when starting features, reviewing active WIPs, or archiving completed work (project)
GitHub
writing-plans
Create detailed implementation plans with granular tasks. Use before implementing features or complex changes.
GitHub
dev-log
Document development work and save it to Notion database. Use when the user completes a feature or change and wants to create a comprehensive development log including Git branch differences, discussion points...
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é.