Total 54,003 skills, Project Management has 1964 skills
Showing 12 of 1964 skills
List all plans from the KB database with key metadata. Use to get a quick overview of plan statuses, priorities, and story counts.
Help turn ideas into fully formed plans through collaborative dialogue. Use before starting any project - product features, business ideas, creative projects, or process improvements.
Manage tasks, track progress, and log daily updates via the ai-todo CLI. Trigger scenarios: 1) EXPLICIT — user mentions tasks, todos, to-do lists, progress tracking, daily standup, sprint planning, project management, work logs, or task completion. 2) POST-ACTION (proactive) — after git commit, git push, deploy to Vercel, merge PR, release, or any significant milestone (feature implemented, bug fixed, refactor done), proactively log progress and update/complete related tasks. When git-tools or vercel:deploy skill finishes, ALWAYS trigger this skill to record what was accomplished. 3) PRE-ACTION (proactive) — when user discusses implementation plans, architecture design, feature breakdown, technical specs, RFC, sprint planning, or requirement analysis, proactively suggest creating tasks to track planned work. When brainstorming skill completes, trigger this skill to convert outcomes into trackable tasks. 4) SESSION-END — when a work session involves substantial code changes, suggest a progress summary before ending. This skill connects to ai-todo (https://ai-todo.stringzhao.life) for persistent task management across sessions.
Creates detailed technical specifications for software projects covering requirements, architecture, APIs, and testing strategies. Use when planning features, documenting system design, or creating architecture decision records.
Manage project structure and workflows
Strategic requirement roadmap with iterative decomposition and issue creation. Outputs roadmap.md (human-readable, single source) + issues.jsonl (machine-executable). Handoff to team-planex.
Provide development estimates for tasks, features, or projects with intelligent analysis. Use when planning timelines, assessing complexity, or scoping resources.
Use this when you need to evaluate the risks and benefits of accepting, negotiating before accepting, pausing, or rejecting outsourcing projects, internal projects, or requirements. It is particularly suitable for scenarios with ambiguity in scope, acceptance criteria, payment terms, compliance, project timelines, or dependencies, as well as high-uncertainty situations such as emergency task insertion, contract renewal/modification, multi-requirement prioritization, or AI/LLM-related initiatives.
Lead Développeur pour coordination technique opérationnelle et code review. Utilise ce skill quand: (1) coordination d'une équipe de développeurs, (2) code review et qualité de code, (3) mentoring technique, (4) résolution de problèmes techniques complexes, (5) planification des sprints techniques, (6) validation des merge requests.
This skill should be used when the user asks to "create an issue", "file a bug", "create a feature request", "open a GitHub issue", "report a bug", "request a feature", "create a task", "break this into issues", or describes a feature/bug they want tracked in GitHub. Guides interactive issue creation with structured templates, workspace change attachment, and optional autonomous label for the automated pipeline.
Systematic progress tracking for skill development. Manages task states (pending/in_progress/completed), updates in real-time, reports progress, identifies blockers, and maintains momentum. Use when tracking skill development, coordinating work, or reporting progress.
Create or update project charters from interactive or provided principle inputs, ensuring all dependent templates remain synchronized. Applicable to project management, specification formulation, charter maintenance, and team collaboration scenarios. Trigger words include "speckit constitution", "create charter", "update charter", "project charter", "formulate specification", "team charter"