Total 43,685 skills, Project Management has 1608 skills
Showing 12 of 1608 skills
Select the most appropriate pipeline for a user goal, lock it in `PIPELINE.lock.md`, and route checkpoint questions into `DECISIONS.md`. **Trigger**: pipeline router, choose pipeline, workflow selection, PIPELINE.lock.md, 选择流程. **Use when**: 用户目标/交付物不清晰，需要在 snapshot/survey/tutorial/systematic-review/peer-review 中选一个并设置最小 HITL 问题集。 **Skip if**: pipeline 已锁定（`PIPELINE.lock.md` 存在）且所需问题已回答/签字完成。 **Network**: none. **Guardrail**: 尽量一次性提问；信息不足就写 `DECISIONS.md` 并停下等待。
Displays progress dashboard showing phase completion, blocked tasks, and remaining work estimate. Provides at-a-glance view of implementation status. Run anytime to check progress.
Technical spike and research investigation specialist. Use when exploring options for a technical decision, conducting timeboxed investigations, or evaluating technology choices.
Use when identifying launch risks, mitigation plans, and escalation owners.
Document and communicate plans clearly. Structures implementation plans with tasks, decisions, and success criteria.
Automatically create or update GitHub Pull Requests. When you need to create a PR for Paddle-related repositories, prioritize using this skill.
Interactive feature development workflow from idea to implementation. Creates requirements (EARS format), design documents, and implementation task lists. Use when creating feature specs, requirements documents, design documents, or implementation plans. Triggered by "kiro" or references to .kiro/specs/ directory.
Break down large tasks into smaller, actionable items. Use when planning sprints, estimating work, or creating implementation plans. Covers task breakdown strategies.
Use when designing organizational structure (team topologies, Conway's Law alignment), mapping stakeholders by power-interest for change initiatives, defining team interface contracts (APIs, SLAs, decision rights, handoffs), assessing capability maturity (DORA, CMMC, agile maturity models), planning org restructures (functional to product teams, platform teams, shared services), or when user mentions "org design", "team structure", "stakeholder map", "team interfaces", "capability maturity", "Conway's Law", or "RACI".
Use after research (Z01 files exist) to create implementation plan - follow structured workflow
Convert vague or high-level requests into a concrete engineering plan with goals, constraints, steps, success criteria, and validation. Stop and wait for human confirmation.
Designs high-performing team structures using organizational psychology AND creates new skills on-the-fly when team needs unmet expertise. Expert in team composition, personality balancing, collaboration ritual design, and skill creation for missing capabilities. Use for team design, role definition, skill gap identification. Activates on 'team building', 'team composition', 'skills needed', 'what skills'. NOT for general project management or solo work planning.