Total 52,201 skills, Project Management has 1904 skills
Showing 12 of 1904 skills
Plan document manager -- create, modify, and organize plan.md with Phase/task structure. 기획서(plan.md) 자동 생성/추가/수정 스킬. Triggers: /plan, "create plan", "기획서", "plan 생성", "Phase 추가"
McKinsey-style issue tree framework for breaking down complex problems into MECE (Mutually Exclusive, Collectively Exhaustive) components. Use when users need to decompose strategic questions, structure analysis, create work plans, or prepare for case interviews. Apply hypothesis-driven approach to problem-solving.
Resolve a conflict between two functional specs in a ***plain spec file. Use when conformance tests for a previously passing spec start failing after a new spec is rendered, or when a potential conflict is detected while adding a new functional spec (via `add-functional-spec` or `add-functional-specs`).
Use when a Beat change is implemented and ready to archive — not for verifying implementation
Prepares sprint review and demo of deliveries for stakeholders. Use when the sprint has ended and it is necessary to present what was delivered, what changed in scope, what is pending, and what decisions are needed.
AI-assisted label triage for NVIDIA/NemoClaw issues and PRs. Reads triage-instructions.md at runtime for consistent label guidance. Supports single-item mode (give it a number) and batch mode (fetches up to 50 unlabeled open items). On approval, applies labels and an optional triage comment via gh CLI, then logs the session to the daily-rhythm activity folder. Trigger keywords - triage, label issues, suggest labels, batch triage, triage issue, triage PR, label this, what labels.
Mandatory only on the task-file path of `spec-loop-plan-task` after implementation approval. Use when implementation deviates from the approved task, when uncertainty must be clarified instead of guessed through, when new blocking questions arise, or before presenting the current task or subtask to the User. Governs clarification routing, canonical task updates when explicit User clarification, accepted review feedback, or explicit post-implementation User approval changes the current task definition, the post-implementation `Implementation notes` check, and whether the increment may move to `review`. May be applied in parallel with other implementation-related skills.
Gerente do ciclo de vida de stories e orquestrador de handoffs no SynkOS. Use esta skill quando o usuário pedir para decompor um épico em stories, criar stories com critérios de aceite, fazer backlog grooming, planejar sprint, orquestrar handoffs entre roles (architect → dev → qa), ou fazer perguntas como "quebre esse épico em stories", "crie a story para X", "o backlog está priorizado?", "faça o checkpoint da story Y", "orquestre o handoff para QA". Ative também para resolver dependências entre stories, escalar stories bloqueadas, e garantir que cada story tem ownerRole e reviewRole definidos antes de entrar em implementação.
Guardião da qualidade de stories e critérios de aceite no SynkOS. Use esta skill quando o usuário pedir para validar uma story antes da implementação, revisar critérios de aceite, aprovar ou rejeitar uma story para o sprint, verificar se o "definition of done" foi cumprido, ou fazer perguntas como "a story X está pronta para implementar?", "os critérios de aceite são testáveis?", "o escopo está claro?", "o que está IN e o que está OUT dessa story?". Ative também para refinar stories com escopo ambíguo, garantir rastreabilidade entre story e objetivo de produto, e para revisão pós-implementação contra os critérios originais.
Use after zanahoria-multi-assumptions has filed N parallel issue variants AND @coderabbitai has responded to all of them — closes the family by extracting the load-bearing assumption, naming a winner, capturing the decision as an ADR, and cleanly closing the rejected variants with cross-referenced reasoning. Triggers on close-the-family, pick-a-winner, commit-the-decision, decide-variants, after-CR-responds, zanahoria-decisions.
Create, triage, label, assign GitHub issues via gh or REST.
Specification-driven development from raw requirement to product design, technical design, task list, execution, and verification.