Total 54,172 skills, Project Management has 1983 skills
Showing 12 of 1983 skills
Trigger: Call this skill when the task you are facing clearly requires collaboration of multiple ideological tools. Common trigger signals include: starting a new project from scratch, tackling complex and difficult problems, iterating and optimizing existing solutions. This skill provides standardized cross-skill workflow combinations to solve the problem of "which skill to use first and how to connect them". English: Trigger when a task clearly requires multiple skills in sequence. Use this skill to select a standard workflow that chains skills together, defines data handoff between steps, and specifies termination conditions.
Phase-based development workflow manager that guides projects through structured phases from strategy and design through implementation, quality assurance, and launch. Manages roadmaps, feature branches, agent orchestration, and MCP server configuration.
Integrate development-related requirement convergence, structured review, execution ruling and resumption closure into a fully automatically advancing workflow harness
Query project member list
Apply Lean and Six Sigma principles to eliminate waste and reduce process variation. Use this skill when the user needs to improve operational efficiency, identify the seven wastes (TIMWOOD), run DMAIC improvement projects, or streamline workflows — even if they say 'our process is too slow', 'where are we wasting resources', or 'how do we reduce defects'.
Generates professional Statements of Work from a project brief. Use when a user needs to create an SOW, scope a project, define deliverables and milestones, or produce a consulting engagement document.
Dual-mode meta-skill for (A) pre-plan field validation of business ideas through Customer Development and (B) post-plan auditing of market claims against evidence. Integrates Customer Development methodology (Blank/Dorf), rapid validation (Kagan), customer discovery steps (Cooper/Vlaskovits), and empathy-based research (Alam).
Use when the war plan is approved and it is time for parallel execution — dispatches soldiers through capos to implement work packages with TDD enforcement, tribute collection, and escalation protocols
Phase 1 of the Issue Workflow - Translate the user's problem into a reproducible, traceable {slug}-report.md through conversation. The AI only asks "what you saw, how to reproduce it, what should happen" here, and does not guess the root cause for the user (that's Phase 2's responsibility). This phase is also the only official decision point for determining whether to take the fast track or the standard path: first read the relevant code based on the user's description, and if the root cause can be identified at a glance and the changes required are minor, directly inform the user to take the fast track. Trigger scenarios: The user says "file an issue", "log this bug", "I found a problem". This is the starting point of the issue workflow with no pre-requisites.
Maintainer workflow for reviewing, triaging, preparing, closing, or landing OpenClaw pull requests and related issues. Use when Codex needs to validate bug-fix claims, search for related issues or PRs, apply or recommend close/reason labels, prepare GitHub comments safely, check review-thread follow-up, or perform maintainer-style PR decision making before merge or closure.
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".
Creates and maintains analise.md and plano.md for technical discussions and implementation planning. Use when starting a technical discussion, planning implementation, or when the user asks for analysis documentation or a plan.