Total 50,341 skills, Project Management has 1841 skills
Showing 12 of 1841 skills
Document the pitfalls encountered or good practices discovered during this work into searchable learning documents, which can be accessed by both AI and humans when similar tasks arise in the future. Two tracks: The pitfall track records experiences where "things should have worked but didn't" — including bugs, configuration traps, environment issues, and integration failures; The knowledge track records findings that "should be the default approach going forward" — including best practices, workflow improvements, and reusable patterns. Trigger scenarios: Proactively prompt at the end of feature-acceptance or issue-fix workflows, or when the user mentions phrases like "document knowledge", "learning", "document learnings", or "record this experience". Spec documents record what was done, while learning documents record what pitfalls were encountered / what was learned — they complement each other and are not interchangeable.
Document the finalized tech stack selections, architecture decisions, long-term constraints, and coding conventions in the project into searchable permanent records. No one will remember why X was chosen six months later, but with decision documents, at least the background can be understood before making changes next time. Four categories: tech-stack (which tools/libraries/frameworks to use), architecture (how the system is organized), constraint (what is not allowed), convention (what is uniformly done). Trigger scenarios: Proactively trigger after making important choices during feature-design or issue-analyze, or when the user says "record the decision", "archive tech selection", "ADR", "record this constraint", "write down the convention". Only archive finalized decisions; do not archive proposed solutions under discussion.
Phase 3 of the feature workflow – Complete the acceptance closed-loop. Four tasks: 1. Check layer by layer against {slug}-design.md to verify if the implementation deviates from the plan; fix any deviations on the spot instead of just "noting them" in the report. 2. Incorporate this feature into the project's overall architecture documentation. 3. If this feature changes the user story or boundaries of the corresponding requirement, update the requirement doc accordingly. 4. If this feature originated from a roadmap item, change the status of the corresponding entry in roadmap items.yaml to done and sync it with the main document. Finally, produce a {slug}-acceptance.md as the closed-loop proof for the entire workflow. Prerequisite: cs-feat-impl is completed. Trigger scenarios: User says "The feature is done, let's accept it", "Do the final check", "Prepare for merge", "Generate the acceptance report".
Help users get started with ZenTao and zentao-cli in a casual chat-based way. Let users follow their roles (Product Manager/Project Manager/Tester/Developer/Executive) to explore and practice in a real ZenTao environment, and get familiar with the CRUD operations and status transitions of modules such as Product, Requirement, Plan, Task, Bug, and Test Case. This skill is used when users are first exposed to ZenTao, want to get started with zentao-cli, hope to learn what ZenTao can do, or explicitly ask "Show me around ZenTao/Give me a ZenTao tour/Experience ZenTao".
Guide a PhD student through a structured weekly review of their research progress. Use this skill whenever the user wants to do a weekly check-in, prepare a progress update for their advisor, reflect on the past week's research, or plan the upcoming week. Trigger on phrases like "weekly review", "this week's progress", "advisor update", "reflect on my week", "plan next week", "how did my week go", or whenever the user mentions wanting to take stock of their recent research work. Also trigger when the user seems to be venting about the week without structure — help them channel it into a productive review.
Identify disruption opportunities and architect business model innovation. Use when the user says "lets create an innovation strategy" or "I want to find disruption opportunities"
Systematic Fishbone analysis exploring problem causes across six categories
Phased software engineering execution for large refactors, migrations, feature work, testing efforts, and modularization. Executes through strict planning, workspace setup, dependency analysis, PRD-driven parallel implementation, and merge phases. Each subagent runs in an isolated Ralph workspace (CLAUDE.md + prd.json + progress.txt) and executes the Ralph agent loop autonomously. Use when a task needs isolated workspaces, atomic commits, parallel branches, and controlled merge sequencing.
Plans development tasks in a structured way for teams. Use this skill when the user triggers /plan-task with a description, or when asking to plan, detail, or break down a development task into steps. Always use when the message starts with /plan-task.
Facilitates and documents a team retrospective capturing what went well, what to improve, and action items. Use at the end of sprints, projects, or milestones to reflect and improve team practices.
Issue triage: audit open issues, categorize, detect duplicates, cross-ref PRs, risk assessment, post comments. Args: "all" for deep analysis of all, issue numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.
You are **SeniorProjectManager**, a senior PM specialist who converts site specifications into actionable development tasks. You have persistent memory and learn from each project.