Use when partner provides a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes tasks in batches, reports for review between batches
Structured retrospective for incidents and mistakes. Transforms problems into systematic improvements.
Break down GitHub issues into official GitHub sub-issues by parsing task lists from parent issue descriptions. Use this skill when a user wants to convert a parent issue with tasks into linked sub-issues, when managing complex features that need hierarchical breakdown. Accepts issue number as parameter or prompts user if not provided.
ๆฐๅๆๆดๆฐ Project Guardrails/ๅทฅ็จ่ง่๏ผๅ็ซฏ/ๅ็ซฏ/API/ๆฐๆฎ/ๅฎๅ จ/่ฟ็ปด/ๅๅธ๏ผใ็จไบๆฐ้กน็ฎๅฏๅจใๆๆฏๆ ๅๆดใๅคๅข้ๅไฝใไบๆ ๅค็ๆๆ็ปญๆผ็งปๅบ็ฐๆถๅปบ็ซ็ปไธ็บฆๆไธๆไฝๆ ๅใ
Create detailed implementation plans before coding (saves tokens later)
This skill should be used when the user asks to "analyze slide quality", "review slide", "check slide design", "optimize slide", "improve slide content", "assess slide clarity", or needs evidence-based quality evaluation using the 12-point checklist for presentation slides.
Read project session context from .sessions/index.md to understand ongoing work, previous decisions, blockers, and history. Use when the user asks about project context, previous sessions, what was worked on before, architectural decisions, blockers, or when they reference "last time", "previously", "the session", or "what we decided".
Discovery questions, checklists, and techniques for gathering requirements. Use during discovery to ensure thorough understanding before creating issues.
Auto-update status metrics across governance documents - scans MCP issues/specs to calculate current counts and percentages, updates README files and NEXT_STEPS with accurate data
Fetch unresolved PR review comments from GitHub. Use when working with pull request reviews, addressing review feedback, or checking outstanding review comments on a PR. Triggers on requests like "get PR reviews", "fetch review comments", "show unresolved comments", or "what feedback is pending on this PR".
INVOKE after research or brainstorming to synthesize findings. Produces visible aggregation with conflict resolution. Use when multiple inputs need combining into coherent output. Triggers: synthesizing research, combining ideas, merging approaches, integrating findings.
Systematic questioning to clarify requirements, goals, and constraints. Use when there's ambiguity about what the user wants, hidden complexity needs uncovering, or you need to understand before proceeding. Triggers on unclear requirements, vague goals, or when other skills encounter fundamental ambiguity.
Automated technical debt identification, tracking, and prioritization system
Log work activity to a specific project folder. Maintains changelogs, session notes, and decision records for projects.
Search for features and automatically retrieve all child work items (stories, tasks, bugs) under that feature. Use when planning or reviewing feature scope.
Use BEFORE using the Task tool. Ensures you select the correct specialized subagent_type instead of generic agents.
์คํฌ ์ํ๊ณ๋ฅผ ๊ด๋ฆฌํ๊ณ ํ์ง์ ์ ์งํฉ๋๋ค. ์ ์ฒด ์คํฌ ํํฉ ํ์ , ํ์ง ๋ถ์, ๋ฌธ์ ์ ์ง๋จ, ๊ฐ์ ์ ์, ์๋ ์์ , ์ ์คํฌ ์์ฑ ๊ฐ์ด๋๋ฅผ ์ ๊ณตํฉ๋๋ค. "์คํฌ ๋ถ์", "์คํฌ ํํฉ", "์คํฌ ๋ง๋ค๊ธฐ", "์คํฌ ๊ฐ์ " ์์ฒญ ์ ํ์ฑํ๋ฉ๋๋ค.
Create a new project with proper PARA structure. Ensures consistent project setup with completion criteria and status tracking.
Use during planning to discover and document available project commands (make targets, npm scripts, etc.) for success criteria.
Transform PBIs into ready status for AI execution. Use when refining backlog items, writing acceptance criteria, splitting stories, or ensuring Definition of Ready.
Use when creating implementation plans to research codebase patterns and gather context for planning.
