Total 50,320 skills, Project Management has 1841 skills
Showing 12 of 1841 skills
Evaluate, compare, and manage vendor relationships. Trigger with "evaluate this vendor", "compare vendors", "vendor review", "should we renew", "RFP", or when the user is making procurement or vendor decisions.
Writes precise, autonomous-execution-ready tasks using the SMART+ framework (Specific, Measurable, Actionable, Referenced, Testable, +Context). Transforms vague task descriptions into detailed specifications with file paths, verification commands, and clear success criteria. Use when writing tasks for any agent, creating todos, planning features, decomposing work, or when tasks lack precision. Triggers on "write task", "create todo", "break down feature", "make task precise", "task is vague", or when task descriptions are missing file paths, verification steps, or clear success criteria. Works with todo.md, task lists, project planning documents, and agent instructions.
Expert at detecting stories that are too big and applying splitting heuristics. Use when user describes work that seems large, mentions multiple features in one story, or needs help breaking down requirements. Detects linguistic red flags (and, or, manage, handle) and suggests concrete splitting strategies. Use when: - Story has obvious red flags: "and", "or", "manage", "handle", "including" - User describes multiple features bundled together - Story feels vague or too large - User asks "how to split this story" Do NOT use when: - Story is already small and focused (< 1 day work) - Feature needs layered analysis without obvious split points (use hamburger-method instead) - User asks HOW to implement (use micro-steps-coach instead)
Use when you need to execute I1 (Implementation Plan) in the Spec Pack of sdlc-dev, convert requirements/design into `{FEATURE_DIR}/implementation/plan.md` (the single source of truth (SSOT) for execution checklist and status), and provide an unambiguous task list for subsequent I2 execution.
[Planning] Validate plan with critical questions interview
Expert program management covering multi-project coordination, portfolio governance, strategic alignment, and cross-functional leadership.
GitHub issue state machine and code integration patterns. Covers state transitions (needs-triage → accepted → in-progress → completed), branch naming (feat/123-desc), PR linking (Closes
Define the structure and organization of storage functions within a project.
In-repo planning and specification system for software projects. Use when asked to "create a plan", "write a spec", "document a proposal", "blueprint a feature", or when doing architectural planning work.
Project development lifecycle management with a strict three-phase workflow (investigate -> proposal -> implement), file-based plan tracking in docs/plan/, task tracking in docs/task/, and claim-before-work multi-agent coordination. Use when handling feature development, bug fixes, refactors, planning, progress tracking, or multi-agent execution in an existing codebase. Supports English and Chinese project templates.
Use this when you need to execute R4 (generate an interactive Demo project based on requirements/prototype.md) in the sdlc-dev product requirement Spec process, and need to avoid skipping spec-context, proceeding when prototype.md is missing or the runnable Demo project root directory is missing, or creating custom pages/directories that lead to untraceability and inability to close the loop.
Implementation feedback capture. Appends effort accuracy, scope changes, and blockers to {repo}/.groom/retro.md. Read by /groom for planning. Invoked by /done and /pr, or manually via /retro append.