Total 50,327 skills, Project Management has 1841 skills
Showing 12 of 1841 skills
Use when new insights change the scope, acceptance criteria, domain language, or technical constraints of an existing Epic, Feature, or Task — for example "refine epic
Consolidates objective metrics of a sprint. Use when you need quantitative data about deliveries, blockers, deviations, and velocity to feed retro, sprint review, or capacity decisions.
Breaks down the design into an atomic, ordered, and verifiable task plan stored in tasks.md. Trigger: /sdd-tasks <change-name>, task plan, break down implementation, task breakdown.
Manages a GitHub Project board + Issues as the source of truth for product backlog, tasks, stories, and bugs. Provides three flows: bootstrap (/track-init), track (/track), and query (/backlog). Uses gh CLI for project operations and MCP tools for issue creation. Trigger: /track-init, /track <description>, /backlog, "qué tenemos pendiente?", "what's pending?", "acordate que hay que...", "remember to...", or when SDD generates tasks via sdd-tasks.
Closes a completed SDD change by saving an archive report to engram and optionally updating ai-context/ memory. Trigger: /sdd-archive <change-name>, archive change, finalize SDD cycle, close change.
Easy Project integration. Manage Projects. Use when the user wants to interact with Easy Project data.
Use BEFORE coding any non-trivial change. Explores user intent, demand, tradeoffs, and approach. Produces a design doc in docs/design-docs/, not code. Required for LARGE tasks, optional for MEDIUM, skip for SMALL.
When developing new features, follow this sub-process — take the vague idea of "add X capability" through to the acceptance closure, with solution documents archived so that both AI and users can later check the original thinking and decision rationale. Trigger scenarios are focused on adding new capabilities ("develop new feature", "add X", "implement XX"), and do not handle bugs in existing code. This skill only acts as a router, deciding which sub-skill to trigger next among brainstorm / design / fastforward / implement / acceptance based on existing artifacts.
creates draft task file in .specs/tasks/draft/ with original user intent
Use when a request or repository needs roadmap decomposition before spec writing because milestone boundaries, module grouping, or independently reviewable tasks are unclear.
Plance integration. Manage data, records, and automate workflows. Use when the user wants to interact with Plance data.
Produces a private strategic preparation document for the user before a meeting that matters. Captures stakes, stakeholder positions and reads, ranked desired outcomes, key messages, anticipated questions with prepared responses, risks and tensions, specific asks, and success signals. Distinct from meeting-agenda because this artifact is not shared with attendees; it is the user's personal tactical prep for meetings where positioning matters.