get-ticket-info
fetches the information about the work that should be done on the current branch. Use when the user tells you to "get the ticket info"
fetches the information about the work that should be done on the current branch. Use when the user tells you to "get the ticket info"
This skill provides patterns for identifying, categorizing, and tracking technical debt. It includes scoring methodologies, YAML schemas for tracking files, and strategies for systematic debt resolution.
Write effective progress files that enable continuity across sessions and agent handoffs in spec-driven development. Use when starting work sessions, resuming after breaks, completing tasks or milestones, encountering blockers, handing off work, recording test results, or documenting issues and resolutions. Triggers include "progress log", "session log", "write progress", "handoff notes", "work log", or when capturing session-by-session work history for continuity.
Summarize feature or product requirements into clear scope, constraints, and risks. Use when the user asks for requirement summary/้ๆฑๆป็ป/้ๆฑ่ฆ็น or wants a concise spec snapshot.
PM Planner Agent. ๊ธฐ๋ฅ ๊ธฐํ, ์๊ตฌ์ฌํญ ์ ์, ๋ช ์ธ์ ์์ฑ์ ๋ด๋นํฉ๋๋ค. ๊ธฐํ, ๋ช ์ธ, ์๊ตฌ์ฌํญ, PRD, ์คํ ๊ด๋ จ ์์ฒญ ์ ์ฌ์ฉ๋ฉ๋๋ค.
Formulates a comprehensive strategy for TDD-based implementation. Analyzes specifications (Specs) and handover items, defines shared implementation policies, and drafts specific TDD tasks (Issues).
Convert BPMN 2.0 XML files into Draw.io native format (.drawio) using the bpmn2drawio Python tool. Renders properly in Draw.io Desktop or web applications. Use this skill when a user wants to visualize a BPMN process in Draw.io, convert BPMN to editable diagrams, or create Draw.io files from process definitions. Triggers on: "convert BPMN to Draw.io", "create drawio from BPMN", "visualize BPMN in Draw.io".
์ด ์คํฌ์ ์ฌ์ฉ์๊ฐ "์์ ์๊ฐ ๊ธฐ๋ก", "์๊ฐ ๋ฑ๋ก", "ํ์ ๋ก๊ทธ", "์์ ์๊ฐ ์กฐํ", "๋ช ์๊ฐ ์ผํ์ด", "time entry", "log hours", "time tracking", "work hours" ๋ฑ์ ์ธ๊ธํ ๋ ์ฌ์ฉ๋ฉ๋๋ค. Redmine ์์ ์๊ฐ ๊ด๋ฆฌ ๊ธฐ๋ฅ์ ์ ๊ณตํฉ๋๋ค.
Decompose a phase plan into atomic beads and sub-beads. Use when breaking down a phase into tasks, when the user mentions "decompose" or "break down", when creating beads from a plan, or when structuring work for parallel execution.
Use when executing implementation plans with independent tasks in the current session
Analyze coverage of business requirements across feature plans, wave plans, and implementations to ensure completeness. Creates traceability matrices mapping requirements to features/waves/user stories, identifies uncovered or partially covered requirements, detects orphaned features, and validates acceptance criteria. Use after feature planning, before wave design, during epic reviews, for stakeholder reporting, or when validating requirement coverage.
Design comprehensive technical specifications and strategic plans for data architecture and analytics projects. This skill should be used when planning major features, creating SPEC documents, assessing product requirements, breaking down complex projects into phases, or documenting architectural strategies like SPEC-1. Guides through requirements gathering, MoSCoW prioritization, phase planning, and open items tracking.
Plan and document coding tasks with PLAN.md and ADRs in docs/ADR. Use when a task can be decomposed, when asked to create or update PLAN.md, or when capturing technical decisions.
Estimate issue complexity before implementation to prevent timeouts. Uses cheap estimation to save expensive implementation tokens.
Manage implementation tasks with sequential sub-steps within a plan
Use when preparing to implement instructions by reviewing documentation and TODO.md so the actual work starts with a shared plan.
ํ๋ก์ ํธ ์์ ๊ณํ ๋ฐ ์งํ ์ํฉ์ ์ฒด๊ณ์ ์ผ๋ก ๊ด๋ฆฌํ๋ ๋ฌธ์ ์์คํ . ์์ ์์ ์ , ์์ ์ค, ์์ ์๋ฃ ํ ๋ฐ๋์ ์ฌ์ฉ. PRD ํ์ธ, TODO ์ ๋ฐ์ดํธ, ๋์์ ํด๋ ์์ฑ ๋ฐ ๊ด๋ฆฌ ์ ์ฌ์ฉ
Conduct a periodic collaboration quality review to proactively identify improvements before friction occurs. Assesses communication patterns, trust calibration, framework effectiveness, and session flow across 4 key dimensions.
Comprehensive feature plan document, creation, editing, and archiving. When LLM needs to work with feature plan documents for (1) Starting a new feature, (2) Reviewing progress of a feature, (3) Reviewing an existing feature plan's requirements, references, and TODOs, or (4) Marking a plan as achieved.
์ํฐํ๋ผ์ด์ฆ ํ ํ๋ฆฟ ๊ด๋ฆฌ (์ฝ๋ ๋ณด์ผ๋ฌํ๋ ์ดํธ, ํผ๋๋ฐฑ ํ ํ๋ฆฟ, ํ๋ก์ ํธ ์ต์ ํ ์ํฌํ๋ก์ฐ ํฌํจ)
Generate CA Lobby completion reports with all 12 required sections. Use when CA Lobby phase complete, user says "phase complete" or "create completion report". Ensures comprehensive documentation and master plan update.