Total 50,510 skills, Project Management has 1846 skills
Showing 12 of 1846 skills
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.
Manage a team's tasks and use Box as the file storage backend
Add a new feature with design, TDD, and PR workflow
Build a retrospective or forward-looking work timeline from git commits, project docs, user notes, or chat records, then output a Markdown and/or HTML report with a Gantt chart or timeline visualization. Use when the user wants to review past work across one or more projects, explain time allocation to a mentor, summarize what was done in a period, or plan the next phase with a timeline.
People leadership for scaling companies. Hiring strategy, compensation design, org structure, culture, and retention. Use when building hiring plans, designing comp frameworks, restructuring teams, managing performance, building culture, or when user mentions CHRO, HR, people strategy, talent, headcount, compensation, org design, retention, or performance management.
Issue/PR の状態とプロジェクト Status の自動同期を設定する。モード A は `Fandhe-AI/actions/project-sync` Composite Action を使う `.github/workflows/project-sync.yml` を生成 (PAT または GitHub App トークン)。モード B は既存の不整合を一括補正。「自動同期セットアップ」「PR レビュー時に In Review 化」「ボードと Issue の状態を同期」などで使用。
Helps engineering managers identify, quantify, and reduce hidden capacity drains that make teams miss commitments even when everyone is busy. Use this skill whenever the user mentions invisible work, untracked work, support requests consuming the team, glue work, shadow backlog, sprint spillover, capacity planning being wrong, teams always underestimating, senior engineers burning out, or "we are busy but nothing ships." Produces a diagnostic, evidence plan, and concrete interventions.
Helps engineering managers respond to high-urgency requests and use deadlines effectively — produces a five-question framework for evaluating unreasonable deadlines, guidance on scope/staffing/intensity decisions under pressure, Parkinson's Law applied to engineering, and five common deadline mistakes to avoid. Use when the user says "urgent deadline," "everything is on fire," "we need to ship fast," "fake deadline," "unreasonable timeline," "crisis mode," "working weekends," "Parkinson's Law," or "leadership is pushing for faster delivery."
VP of Engineering advisory for startups: delivery throughput (DORA 4 metrics + bottleneck identification), engineering hiring funnel (sourcing → screen → onsite → offer conversion + time-to-fill + pipeline gap), engineering team structure (squad/tribe/chapter design + tech-lead manager-trigger thresholds), and production discipline (on-call, deployment cadence, postmortem culture). Use when sprint velocity is dropping, eng hiring is broken, team structure is unclear, or deciding when to add a tech-lead manager. NOT a CTO skill (which owns architecture) — VPE owns delivery operations and how the team ships.
Triage Linear or Jira backlogs and run bug sweeps via the Composio CLI. Bulk-fetch issues, dedupe, relabel, reassign, and post summaries — all from the shell without clicking through the UI.
Captures real usage feedback for agile skills and turns it into evidence-backed proposals to improve, merge, split, deprecate, or remove skills and templates. Use when a skill does not fit a real workflow, when templates need refinement, when skills overlap, or when the process library needs maintenance.
Plans sprint by selecting items from backlog, defining objective, capacity, and execution order. Use at the beginning of a work cycle to align what will be done.