Total 53,944 skills, Project Management has 1958 skills
Showing 12 of 1958 skills
Manage Jira Agile boards and sprints. Use when listing boards, creating sprints, or moving issues to/from sprints.
Use GitHub Spec Kit (https://github.com/github/spec-kit) to create new requirement definitions and specifications (including specification formulation, specification document creation, and specification design) or append to existing specifications, and generate/update spec.md/plan.md/tasks.md. It is used when requirement definition, requirement addition/modification, requirement organization based on TDD, specification documentation, and execution of Spec Kit's specify/clarify/plan/tasks workflow are required.
Manage Azure Boards work items including user stories, tasks, and bugs with WIQL queries. Use when managing Azure Boards work items or creating sprint backlogs.
You must use it before any creative work - creating features, building components, adding functionality, or modifying behavior. Explore user intentions, requirements, and design before implementation.
Use when you need to execute I2 (Implementation Execution) in the Spec Pack of sdlc-dev, using `{FEATURE_DIR}/implementation/plan.md` as the sole SSOT to implement in batches, run minimal validation, write back audit information, and report at batch checkpoints; stop immediately when encountering blocks or clarification items.
Create a comprehensive specification from a brief description. Manages specification workflow including directory creation, README tracking, and phase transitions.
Collaborative problem-solving protocols: write technical specifications (spec, or alspec), create implementation plans (plan, or alplan), or use Align-and-Do Protocol (AAD). Also generates PR/MR descriptions (aldescription).
Use this before touching code when you have a requirement for a specification or multi-step task
This skill scopes and researches a single new task to insert into an existing project's ROADMAP.md. It should be used when a developer identifies a gap in the roadmap during the do-task/checkpoint loop and needs to properly scope a new action item before implementing it. Triggered by requests like '/scope-task 2.5 Integrate Research into SPEC.md', '/scope-task 3.3 Add WebSocket support', or 'scope task 1.4 Set up CI pipeline'. Works alongside project-init (which creates the roadmap) and do-task (which implements tasks).
Use when making architecture decisions, evaluating build-vs-buy, planning tech stack, prioritizing tech debt, writing PRDs, or needing strategic technical leadership
Create a TODO or initiative task in One Horizon. Use when asked "log this task", "create a todo", "track this small task", "create an initiative", "plan this project", or "start a roadmap initiative". For bugs or feature requests, use report-issue instead. Requires One Horizon MCP.
Generate standup talking points from One Horizon task data. Supports personal and team scope. Use when asked "prep my standup", "what should I say", "give me my standup update", "team standup summary", or "what should we cover in standup". Requires One Horizon MCP.