Total 50,395 skills, Project Management has 1845 skills
Showing 9 of 1845 skills
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
Create or update `tasks/todo.md` as the prioritised project backlog with clear `feat`/`fix`/`chore` items and ordering. Triggers: new backlog, update todo.md, add backlog item, reprioritise roadmap.
Maintain project brain with architectural decisions in memory file.
1. Requirement Gathering
Generates a comprehensive milestone progress review including feature completeness, quality metrics, risk assessment, and go/no-go recommendation. Use at milestone checkpoints or when evaluating readiness for a milestone deadline.
Analyze competitor repositories with an evidence-based approach. Use this when tracking competitors, creating competitor profiles, or generating competitive analysis. CRITICAL - all analysis must be based on actual cloned code, never assumptions. Triggers include "analyze competitor", "add competitor", "competitive analysis", or "竞品分析".
Five Whys root cause analysis. Iteratively asks "why" to drill past symptoms to underlying causes. Use for debugging, investigating failures, or understanding why something went wrong.
Prep for a first VC meeting by mapping a founder's pitch deck against the investor's pre-meeting questions, producing an honest assessment of what is answered vs. what is missing, then generating a memo the founder can send ahead of the call. Use when a founder asks for help prepping a first VC meeting, when an investor has shared a pre-meeting question list (e.g. Jess Lin / Work-Bench), or when the user wants a deck reviewed against specific investor expectations.
Plan Requirements - generates a structured requirements document, asking clarifying questions about ambiguities before proceeding