Total 43,756 skills, Project Management has 1613 skills
Showing 12 of 1613 skills
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.
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.
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.
Expert agile coaching covering team transformation, agile frameworks, coaching techniques, organizational change, and continuous improvement.
Design, validate, and plan a startup from scratch. Covers market research, competitive analysis, business model, brand identity, product definition, financial projections, and validation experiments. Trigger when the user has a startup idea to explore, wants to validate a business concept, needs a business plan or lean canvas, asks for market sizing or competitive landscape, wants brand positioning or go-to-market strategy, or says anything like "I have an idea for..." or "is this idea worth pursuing". Also handles resuming from a previous checkpoint.
Conduct structured interviews to gather requirements, clarify specifications, or understand context. This skill should be used when starting a new task that requires understanding user intent, requirements, technical specifications, or context. It supports various interview types including requirements definition, debugging investigation, architecture review, and general information gathering.
Final pass to identify missed items, edge cases, and risks before considering a scope done
PRD review, requirements review, check PRD quality. Use when: Review is required after PRD completion, "review PRD", "PRD review", "requirements review"
Expert at evaluating software projects for production readiness. Assesses codebases holistically to determine what's shippable, what's blocking launch, and how to get from current state to "good enough to charge money for."
ShapeUp: Facilitate the complete ShapeUp workflow with triad collaboration
Use this skill when the user asks to triage issues, organize the issue list, "triage issues", "show me all open issues", "categorize issues", "triage-issues". Requires Gitee MCP Server to be configured.