Total 30,695 skills, Project Management has 1151 skills
Showing 12 of 1151 skills
Feishu Task, tasklist, subtask, comment, and attachment management. Activate when user mentions tasks, tasklists, subtasks, task comments, task attachments, or task links.
Scrum framework fundamentals and sprint goal writing. Covers sprint planning, sprint goals, daily scrums, sprint reviews, retrospectives, scrum roles, artifacts, and goal-writing templates (SMART, FOCUS, FAB). Use when planning sprints, writing sprint goals, or facilitating scrum events.
Refines a v1 project plan into agent-ready tasks with clear context, implementation steps, and validation criteria. Use after /plan-project has produced a v1 plan.
Conducts structured interviews to derive technical requirements from business requirements. Requires completed business-requirements.yaml as input. Asks targeted technical questions about architecture, technology stack, data model, APIs, security, testing, and deployment. Generates technical-requirements.yaml output.
Conversational SDD (Specification-Driven Development) guidance skill based on OpenSpec. It is automatically triggered when a user describes development requirements, and guides the user through the entire SDD process via conversations without any manual command input.
Based on the KISS (Keep It Simple, Stupid) and "Minimum Viable Brilliance" complexity control principles. It is used for design and implementation decisions at all levels of projects, systems, modules, code, and functions, helping to prioritize core values, reduce unnecessary complexity, and avoid over-design. Keywords: KISS, simplification, focus, complexity control, Minimum Viable Brilliance.
Create a Plane task in Plane. By default, use the interview skill first to flesh out the issue before creating it; only skip the interview when the user clearly wants a minimal quick capture.
Use when you need to perform I2 (Implementation Execution) in the Spec Pack of sdlc-dev, implement in batches with `{FEATURE_DIR}/implementation/plan.md` as the only SSOT, run minimal verification, write back audit information, and report at batch checkpoints; stop immediately when encountering blocking or clarification required items.
Creates detailed technical specifications for software projects covering requirements, architecture, APIs, and testing strategies. Use when planning features, documenting system design, or creating architecture decision records.
LOAD THIS SKILL when: gathering requirements for new features, user mentions 'requirements', 'requirements-start', 'requirements-end', 'requirements-status', 'requirements-current', 'requirements-list', 'requirements-remind'. Covers structured Q&A workflow with 5-phase requirements gathering, codebase analysis, and spec generation.
Produces calibrated three-point estimates (best/likely/worst case) with explicit unknowns, confidence intervals, and assumption documentation. Breaks work into atomic units, identifies technical and scope uncertainties, calculates PERT ranges, and provides confidence rationale. Triggers on: "estimate this", "how long will this take", "effort estimate", "time estimate", "best case worst case", "confidence interval", "sizing", "estimate effort", "how big is this", "story points", "t-shirt sizing", "estimate the work", "PERT". NOT for task decomposition, implementation plans, or dependency mapping — use task-decomposer instead. Use this skill when a task or project needs an effort estimate with explicit uncertainty.
Use when partner provides a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes tasks in batches, reports for review between batches