Total 50,476 skills, Project Management has 1846 skills
Showing 12 of 1846 skills
Stop being a "nice" manager. Learn Kim Scott's framework for caring personally while challenging directly—the combination that builds trust and drives performance. Use when: **Giving feedback** (positive or constructive); **Building trust** with direct reports; **Performance conversations** that need to happen; **Team culture building** for high performance; **New manager development** learning to have hard conversations
Phase 2 of the feature workflow — Write code according to the implementation sequence in {slug}-design.md, and submit a completion report in a unified format for user review after finishing. Prerequisites: {slug}-design.md has been approved (standard design includes test design, or fastforward design includes acceptance criteria), and {slug}-checklist.yaml exists in the same directory. Trigger scenarios: User says "The plan is confirmed, start implementation", "Write code according to the plan", "Start working". If you encounter situations not covered by the plan during implementation (new concepts, out-of-scope files, need for patch branches), proactively stop and discuss with the user based on the plan, do not proceed forcefully.
Fast Track for Feature Process - When requirements are clear and scope is small, skip the complete design process, write a compact {slug}-design.md, and proceed directly to implementation after one confirmation from the user. What is compressed is divergent discussions and phased reviews, not quality standards - code pointers, acceptance criteria, etc., must not be omitted. Trigger scenarios: User says "quick mode", "fastforward", "cut the steps", "just start working". Not suitable for complex features involving cross-subsystem integration, new terminology sorting, or more than 4 promotion steps - in these cases, proactively inform the user to revert to the complete process.
Phase 1 of the feature workflow — Draft a design document for the new feature, serving as the sole input for subsequent implementation and acceptance. First gather evidence (read architecture docs, review relevant code, grep to prevent term conflicts, check archives), then write a complete first draft in one go (including YAML frontmatter + three-tier structure + test design), submit it to the user for overall review, and iterate until approval. After approval, extract {slug}-checklist.yaml from {slug}-design.md for use in the next two phases. Trigger scenarios: "Start designing the solution", "Write design doc", "Prepare to implement XX", with the prerequisite that you already know what to do, who it's for, and how to define success.
Used when users want to analyze task scheduling, personnel distribution, man-hours, and risk status under a specific TAPD requirement.
PRD/Requirement Document Anti-Omission Assistant. When a user provides a requirement document (PRD, functional specification, product document, etc.) and requests to generate front-end pages, implement functions, or carry out development, this Skill must be used first to convert the requirement document into a structured Checklist, then implement code module by module to prevent function omissions. Trigger scenarios: The user sends a .md/.docx/.pdf requirement document and asks you to "generate pages", "implement functions", "write code", "develop this system"; the user says "develop according to this PRD", "generate based on the requirement document", "implement this document"; the user provides a requirement description of more than 200 lines. Even if the user does not mention the checklist, this process should be automatically triggered if the input is a long requirement document (>200 lines) and the goal is to generate code.
Help a PhD student prepare for a meeting with their advisor so that both sides get maximum value from the limited time. Use this skill whenever the user has an upcoming advisor meeting, lab meeting presentation, or committee meeting, and needs help structuring what to bring. Trigger on phrases like "meeting with my advisor", "advisor meeting tomorrow", "what do I show my PI", "prepare for lab meeting", "committee meeting prep", "I meet my advisor in", or whenever the user expresses anxiety about an upcoming research check-in. Also trigger when the user is unsure how to communicate a research problem or a setback to their advisor.
Help a PhD student set and revise a realistic 3-month research plan that connects to their longer-term goals. Use this skill whenever the user wants to plan a new quarter, review how the last quarter went, set research goals for the next few months, think about what papers to aim for, or reorient after things drift off course. Trigger on phrases like "quarterly plan", "next 3 months", "plan my quarter", "what should I work on this quarter", "review last quarter", "my research goals", or whenever the user talks about mid-range planning (longer than a week, shorter than a year). Also trigger if the user is feeling directionless about what to focus on next.
Zoho Bugtracker integration. Manage Projects. Use when the user wants to interact with Zoho Bugtracker data.
Draft a structured decision memo for Ane. Use when the user asks for a "decision memo", "decision doc", "options paper", "recommendation brief", or equivalent. Produces a scannable document with context, options, recommendation, risks, and reversibility. Applies Ane's CLAUDE.md writing style automatically.
Build a rigorous Theory of Change for MEL/SRHR programmes following Vogel (2012) DFID criteria and van Eerdewijk et al. (2017) KIT feminist ToC model. Use when Ane asks for a "theory of change", "ToC", "programme logic", "change pathway", "pathway analysis", or similar. Produces articulated outcomes, preconditions, assumptions (tested vs untested), contribution questions, and an evidence plan. Flags missing feminist political economy analysis.
Cross-meeting archaeology skill. Consumes multiple meeting recaps (or raw notes) over a period and surfaces patterns invisible in any single meeting. Shows how decisions evolved, who has been saying what, where threads are stalling, and where contradictions have emerged. Produces a plain-text timeline, themes with confidence markers, stakeholder position tracking, consolidated decision list, contradiction flags, open items, narrative summary, and prioritized follow-ups.