jira-activity-type-categorizer
Detailed categorization logic for assigning JIRA tickets to activity type categories
发现 devops project management 相关 Skills,比较来源仓库和用途,查看适合你工作流的技能说明。
Detailed categorization logic for assigning JIRA tickets to activity type categories
Jira conventions for the CNTRLPLANE project used by OpenShift teams
Implementation guide for creating well-formed Jira user stories with acceptance criteria
Query and summarize JIRA bugs for a specific project with counts by component
Detailed implementation guide for recursively analyzing Jira features and generating comprehensive documentation
Implementation guide for creating Jira epics with proper scope and parent linking
Implementation guide for creating Jira features representing strategic objectives and market problems
Implementation guide for creating Jira tasks for technical and operational work
HyperShift team-specific Jira requirements for component selection and conventions
Systematic spec-driven workflow (specification→clarification→planning→tasks→implementation→validation) for feature development. Auto-executes when user clearly wants to build, create, add, implement, develop, m...
Manage backlog and archive completed work. Use for backlog operations, archiving phases, or keeping active plan focused. Curates plan organization.
Guide architectural decisions and PLAN.md updates using Flow framework. Use when user discusses "architecture", "how should we architect", "design patterns", "how should we structure", "how do we structure", "t...
Navigate Flow projects with dashboard-first pattern. Use when user asks about status, current work, what's next, or project progress. Read-only skill.
Verify plan consistency, generate summaries, maintain plan health. Use for review, verification, summaries, or plan maintenance. Mostly read-only with maintenance operations.
Document findings and maintain task notes using Flow framework. Use when user says "document", "document this", "document finding", "add notes", "add this to notes", "write this down", "summarize", "summarize t...
Design features through brainstorming and make architectural decisions. Use when user wants to brainstorm, design approach, make architecture choices, or update PLAN.md.
Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context
Plan phases, tasks, and iterations. Use when structuring new work, adding features, or organizing development plans.
Lightweight, git-native issue tracking (aka beads) for AI agents. Use for creating, planning, updating, and tracking issues with dependencies. Invoke when user mentions tbd, beads, to-do lists, planning, tracki...
Preflight bead work: verify beads are in use, confirm explicit start/continue, identify active bead or select next `bd ready`, clarify done criteria, and scope audit before marking `in_progress`.
bd (beads) issue-tracking workflow; use when `.beads/` exists or when running `bd` commands.
Iterate a markdown list of prompts in order, repeating passes until an explicit stop condition is met. Use when asked to loop over prompts or skills to drive work to completion.
Jujutsu (jj) Git-compatible VCS. Use for any version-control work (status/diff/commit/branch/rebase/merge/etc.).
Git workflow best practices including commit messages, branching strategies, pull requests, and collaboration patterns. Use when working with Git version control.
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。