Total 52,164 skills, Project Management has 1902 skills
Showing 12 of 1902 skills
Audit GDD-specified content counts against implemented content. Identifies what's planned vs built.
View and manage workflow states. Use when checking or configuring issue statuses for a team.
Use when running the CTO flow-optimization loop — WIP scan, epic focus, triage unlabeled issues, and dispatch.
Prioritization techniques including MoSCoW, Kano model, weighted scoring, and value-effort matrices. Ranks requirements, features, backlog items, and investment decisions.
스프린트 내 모든 에픽이 완료된 후 스프린트 문서를 아카이빙한다. 문서 이동, changelog 업데이트, git commit을 자동으로 수행한다.
Determine if proposed changes require an RFC. Use when planning significant changes, before starting major work, or when asked whether an RFC is needed.
Manage the academic workspace — project structure, templates, and output organization.
Unified prompt engineering and requirements planning. Use when exploring ideas, improving prompts, creating PRDs, generating task breakdowns, or iterating on existing plans. Includes Jira integration for creating subtasks from plans.
Coordinates album release including QA, distribution prep, and platform uploads. Use when mastering and album art are complete and the user is ready to release.
Expert at detecting stories that are too big and applying splitting heuristics. Use when user describes work that seems large, mentions multiple features in one story, or needs help breaking down requirements. Detects linguistic red flags (and, or, manage, handle) and suggests concrete splitting strategies. Use when: - Story has obvious red flags: "and", "or", "manage", "handle", "including" - User describes multiple features bundled together - Story feels vague or too large - User asks "how to split this story" Do NOT use when: - Story is already small and focused (< 1 day work) - Feature needs layered analysis without obvious split points (use hamburger-method instead) - User asks HOW to implement (use micro-steps-coach instead)
Structured clarification and requirements gathering through focused dialogue. Use when a task is ambiguous, underspecified, or requires user input before any action can be taken. Do not plan or implement anything—only ask questions to collect the information needed. Triggers on: 'ask me', 'ask questions about', 'clarify requirements', 'gather requirements', 'I need you to ask', or when the user explicitly wants a question-and-answer session before work begins.
Socratic discovery and design exploration before planning. Activates when starting non-trivial work — asks clarifying questions, explores alternatives and tradeoffs, produces a design document for approval. Pulls context from Linear issue description, linked docs, and existing CLAUDE.md learnings. Simple bugs and fixes skip this automatically.