ใฆใผใถใผ่ฆไปถใๅๆใใใทในใใ ่จญ่จใใญใฅใกใณใ(DESIGN.md)ใ็ๆใใพใใใฆใผใถใผ่ฆไปถใๆๆงใพใใฏไธๆ็ขบใชๅ ดๅใใทในใใ ใขใผใญใใฏใใฃใฎ่จญ่จใๅฟ ่ฆใชๅ ดๅใๅคง่ฆๆจกใชๆฉ่ฝ้็บใฎ่จญ่จไปๆงใๅฟ ่ฆใชๅ ดๅใๆ่ก็ๅฎ็พๅฏ่ฝๆงใฎๆค่จผใๅฟ ่ฆใชๅ ดๅใซไฝฟ็จใใพใใไธๆ็นใฏAskUserQuestionใใผใซใง็ขบ่ชใใพใใ
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.
Document and track feature implementation with user stories. Workflow for authoring stories, building features, and marking acceptance criteria as passing.
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 asked to design a new feature or project
AI-Agentic Product Owner accountable for maximizing product value through effective Product Backlog management. Use when creating PBIs, ordering backlog, or accepting sprints.
Use when creating implementation plans to research codebase patterns and gather context for planning.
Use when adding a new feature, endpoint, UI flow, integration, or data model change with multi-file impact or unclear requirements that need scoped planning.
This skill should be used when performing any coding task including implementing features, fixing bugs, refactoring code, or making any modifications to source code. Provides best practices, security considerations, testing guidelines, and a structured workflow for development tasks.
๋ฆด๋ฆฌ์ค ๋ ธํธ ์์ฑ. ์์/๋ ํ๊ทธ๋ฅผ ๋ฐ์ ICJC-Backend, ICJC-Frontend, ICJC-Agent ์๋ธ๋ชจ๋์ ๋ณ๊ฒฝ์ฌํญ์ ๋ถ์ํ์ฌ ์ฌ์ฉ์ ์นํ์ ์ธ ๋ฆด๋ฆฌ์ค ๋ ธํธ๋ฅผ ์์ฑํ๋ค. "๋ฆด๋ฆฌ์ค ๋ ธํธ", "release notes", "๋ณ๊ฒฝ์ฌํญ", "์ ๋ฐ์ดํธ ๋ด์ญ" ๋ฑ ์์ฒญ ์ ์ฌ์ฉ.
Creates PRDs using persistent file-based planning. Use when user explicitly says "PRD", "product requirements document", or "ไบงๅ้ๆฑๆๆกฃ". Combines PRD methodology with planning-with-files to avoid context switching.
Begin each work session by understanding the current state and context
