Total 50,473 skills, Project Management has 1846 skills
Showing 12 of 1846 skills
Conducts comprehensive requirements review including completeness validation, clarity assessment, consistency checking, testability evaluation, and standards compliance. Produces detailed review reports with findings, gaps, conflicts, and improvement recommendations. Use when reviewing requirements documents (BRD, SRS, user stories), validating acceptance criteria, assessing requirements quality, identifying gaps and conflicts, or ensuring standards compliance (IEEE 830, INVEST criteria). Trigger when users mention "review requirements", "validate requirements", "check requirements quality", "find requirement issues", or "assess BRD/SRS quality".
Direct technical advisor mode for counting/estimation and architecture/design
Use when you need to plan technical solutions that are scalable, secure, and maintainable.
Maintain durable project context in `tasks/context.md` (state, decisions, milestones, gotchas, optional context links), inline during other workflows or standalone for cleanup/backfill. Triggers: update context.md, decision log, record project context, capture high-value reference links that improve context handoff.
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.
Guides corporate transaction execution—M&A, divestitures, financings, and JVs: deal timeline, diligence workstreams, data room and Q&A, conditions precedent, closing matrix, signing logistics, funds flow, and post-close handoff to integration. Use when running a live deal, maintaining a closing checklist, coordinating legal/tax/HR/IT workstreams, tracking CPs and signatures, or preparing signing/closing binders—not for sales quote-to-cash (deal-operations-administrator), drafting board resolutions (corporate-counsel), commercial contract redlines (commercial-counsel), deal thesis or IC strategy (transaction-principal), general consulting (business-consultant), or generic software programs (technical-program-manager). Output coordinates process; human counsel and executives approve binding steps.
Mandatory only on the task-file path of `spec-loop-plan-task`. Use when an active task file already exists and the next user-facing action would otherwise present that task for evaluation, feedback, review, or implementation approval.
Validate readiness to advance between development phases. Produces a PASS/CONCERNS/FAIL verdict with specific blockers and required artifacts. Use when user says 'are we ready to move to X', 'can we advance to production', 'check if we can start the next phase', 'pass the gate'.
Score and rank product initiatives using the RICE framework. Use when asked to prioritise features, rank a backlog using RICE, score initiatives for quarterly planning, or apply an objective framework to a list of competing ideas. Produces a ranked RICE table with scores, quick wins and moonshot flags, dependency notes, and a recommended sequencing order.
Use this when you have specifications or requirements for multi-step tasks, before starting to write code