Total 30,738 skills, Project Management has 1152 skills
Showing 12 of 1152 skills
Agile methodologies, issue tracking, and team collaboration tools
Compound engineering loop — 5 stages to reduce rework. Use when: (1) starting new work (brainstorm); (2) planning implementation (plan); (3) writing code (work); (4) evaluating output (review); (5) capturing lessons (compound). NOT for: daily rhythm (use daily); task management only (use task).
Estimates task effort by analyzing complexity, dependencies, historical velocity, and risk factors. Produces a structured estimate with confidence levels.
Interactive project initialization with git setup, workflows, hooks, and build configuration. project setup, initialization, scaffold, bootstrap, new project.
Generate phased, dependency-ordered tasks from specs. Identifies parallelization opportunities. task planning, dependency ordering, phased breakdown, parallel tasks Use when: converting specifications to implementation tasks DO NOT use when: writing specs - use spec-writing. Not for execution - use speckit-implement.
Outputs markdown digests and CSV exports for GitHub issues and PRs. Use when creating status reports, weekly updates, stakeholder briefings, generating GitHub comment digests, tracking initiative health. Do not use when release gates/readiness - use release-health-gates. DO NOT use when: project planning - use spec-kit:speckit-orchestrator.
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.
Architecture-aware project initialization combining online research with archetype selection. project initialization, new project, architecture decision, project setup, which architecture, choose architecture, project architecture Use when: initializing a new project and need to select an appropriate architecture based on project type, team size, domain complexity, and current best practices DO NOT use when: architecture is already decided - use project-init instead.
Generates a comprehensive pre-release validation checklist covering build verification, certification requirements, store metadata, and launch readiness.
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.