Help leaders give effective feedback using Kim Scott's Radical Candor framework. Use this skill when asked to: draft feedback for team members, prepare for difficult conversations, review feedback for tone and effectiveness, coach on giving/receiving feedback, prepare 1:1 talking points, or help navigate challenging interpersonal situations at work. The skill helps balance caring personally while challenging directly.
작업 계획서를 기반으로 TDD 방식으로 구현을 진행합니다. "구현 시작해줘", "개발 진행해줘", "코드 작성해줘", "작업 시작" 등을 요청할 때 활성화됩니다.
A comprehensive framework for high-performance engineering management and task execution. It guides users through reducing ambiguity, defining "Done," choosing the optimal leadership positioning, and managing risks via implication-based communication.
To be used for planning the implementation of feature specifications. Follow these instructions to create a detailed implementation plan.
Execute research experiments using TDD methodology. Pops plans from .claude/plans/research_tasks/, implements with smoke/unit/integration tests, and documents results to results.md. Use when: (1) executing the next experiment from the queue, (2) executing a specific plan by number, (3) running an ad-hoc research idea with TDD.
Core planning principles for Portfolio Buddy 2 development. Use when: planning any feature implementation, modification, or refactoring. Ensures code preservation, mobile/desktop optimization, and thorough requirement gathering.
Analyze code review findings and create execution plan. Decides parallel vs sequential fixing based on issue severity and independence. Returns structured task list with clear fixer instructions.
Comprehensive guide to delivery governance including quality gates, standards, compliance, and balancing governance with agility
Best practices for using Claude Code in team environments. Covers skill management, knowledge capture, version control, and collaborative workflows.
Analyzes ideas and extracts functional and non-functional requirements. Use when breaking down concepts into specific, measurable requirements. Identifies what needs to be built, constraints, and success criteria.
Creates an implementation plan for an existing GitHub issue and adds it as a comment. Takes a GitHub issue number. Use when the user wants to plan a ticket, plan an issue, or says "plan ticket X" or "how should we implement issue
General programming best practices applicable to all languages. Covers clean code, testing, refactoring, version control, and development workflows. Use when writing or reviewing code in any language.
TDD-based implementation workflow for feature development, bug fixes, and code changes. Use when: implementing features, fixing bugs, adding functionality, writing new code, or making any code changes. Triggers: "implement", "add feature", "fix bug", "build", "create", "develop", "write code", "TDD", "test-driven".
Analyzes a single problem tree node and either decomposes it into sub-problems OR solves it directly. Never handles multiple nodes or siblings.
Determines phase and execution chain based on analysisContext (task type, complexity, signals). Use after uncertainty detection.
Эксперт по расписаниям проектов. Используй для WBS, Gantt charts, dependency mapping и resource allocation.
Plan and review product scope, value, metrics, and rollout via a structured interview. Use when product direction or scope must be clarified.
检查VS↔SD/DM一致性（value_path是否与序列图/数据模型匹配），生成不一致项清单和修复建议。当Self-Reflection报告一致性问题或准备CONSTRAINT验收前使用。
複数のコンテキストウィンドウにまたがる大規模タスクを検出した際に自動発動。セッション分割、進捗保存、引き継ぎの最適パターンを適用する。
Workflow bug triage for OpenEvent. Use when you have a regression/bug report (wrong step, wrong detour, HIL stuck, site visit issues) and need a minimal reproduction trace plus a fix plan tied to workflow invariants and tests.
Linear 이슈의 세션 transcript에서 도구 사용 내역(성공/실패)을 분석합니다
