Total 50,510 skills, Project Management has 1846 skills
Showing 12 of 1846 skills
Linear project management via Composio API. Use when: (1) Listing, creating, or updating Linear issues (2) Getting teams, users, or workflow states (3) Managing projects or adding comments (4) Running custom GraphQL queries DO NOT use `linear` CLI - use Composio HTTP API only.
Create a new feature/bug track with spec and implementation plan. Interactive interview generates requirements spec, then phased TDD plan. Use when starting work on a new feature, bug fix, or chore.
Issue quality primitives: lint, enrich, decompose. `/issue lint [#N|--all]` — Score issues against org-standards. `/issue enrich [#N]` — Fill gaps with sub-agent research. `/issue decompose [#N]` — Split oversized issues into atomic sub-issues.
Creates a comprehensive action plan that addresses both substance (strengthening your proposal, filling evidence gaps, doing research) and politics (winning over key people, sequencing conversations, handling objections). Use after /clarify or when you need to turn a goal into concrete actions that make your case stronger AND navigate the people involved.
Analyzes impact of proposed changes on existing systems (brownfield projects) with delta spec validation. Trigger terms: change impact, impact analysis, brownfield, delta spec, change proposal, change management, existing system analysis, integration impact, breaking changes, dependency analysis, affected components, migration plan, risk assessment, brownfield change. Provides comprehensive change analysis for existing systems: - Affected component identification - Breaking change detection - Dependency graph updates - Integration point impact - Database migration analysis - API compatibility checks - Risk assessment and mitigation strategies - Migration plan recommendations Use when: proposing changes to existing systems, analyzing brownfield integration, or validating delta specifications.
Agile methodologies, issue tracking, and team collaboration tools
Feature review and prioritization with RICE/WSJF/Kano scoring. Creates GitHub issues for suggestions. feature review, prioritization, RICE, WSJF, roadmap, backlog Use when: reviewing features or suggesting new features DO NOT use when: evaluating single feature scope - use scope-guard.
Use this skill BEFORE implementing any new feature. This is NON-NEGOTIABLE for scope control. Use when evaluating features during brainstorming, planning new functionality, branches approach size limits (1000/1500/2000 lines, 15/25/30 commits). Do not use when feature is already approved and in progress. DO NOT use when: simple bug fixes with clear scope.
Convenes expert panels for problem-solving. Use when user mentions panel, experts, multiple perspectives, MECE, DMAIC, RAPID, Six Sigma, root cause analysis, strategic decisions, or process improvement.
Senior Agile Facilitator & Delivery Architect for 2026. Specialized in AI-enhanced Scrum orchestration, automated ticket management, and high-velocity sprint coordination. Expert in utilizing LLMs to synthesize daily updates, detect blockers before they arise, and maintain a high-integrity backlog across GitHub Issues, Jira, and linear.
Use when you have confirmed the scope of Discover (P0/P1/P2), and now need to quickly build the Level-0 North Star (memory) and Level-1 map layer index skeleton (components/products) under `.aisdlc/project/`, so that you can supplement evidence by module later without double writing and drift.
Use when starting a new project, adding a major feature to an existing system, or when unsure which skills to run and in what order. Supports macOS, iOS, web, full-stack, voice agent, and edge/IoT+ML projects.