analyzing-requirements
ユーザー要件を分析し、システム設計ドキュメント(DESIGN.md)を生成します。ユーザー要件が曖昧または不明確な場合、システムアーキテクチャの設計が必要な場合、大規模な機能開発の設計仕様が必要な場合、技術的実現可能性の検証が必要な場合に使用します。不明点はAskUserQuestionツールで確認します。
ユーザー要件を分析し、システム設計ドキュメント(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