Automated summary
This skill provides a structured framework for planning development tasks by assessing complexity tier and decomposing work into testable units.
Strengths
- Step-by-step guidance with questions to evaluate impact and tier (S/M/L).
- Template for decomposing work into independent, testable tasks.
- Clear output format for presenting the plan to the user.
Limitations
- Requires the user to provide sufficient information about the task.
- Can be too generic for very specific projects.
- Does not handle complex dependencies across teams or services.
Use this skill at the beginning of a new feature or refactoring to get a structured plan.
Avoid for trivial changes (single file, no impact) where detailed planning is unnecessary.
Security analysis
SafeThis skill is a planning template with no executable instructions, dangerous commands, or data exfiltration risks. It only provides a checklist and output format for task decomposition.
No concerns found
How this analysis is madeExamples
I need to add a search feature to our product catalog. Please use the planning skill to assess the tier, decompose the work, and provide a plan.We need to refactor the user authentication module to use OAuth2. Plan the work using the tier judgment and task decomposition templates.Planning Skill
작업 계획 수립 시 참조하는 체크리스트와 템플릿.
1. 티어 판단
다음 질문에 순서대로 답하라:
- 변경 영향도: 핵심 도메인 로직이 바뀌는가? → Yes면 L
- 레이어 횡단: FE + BE 동시 변경인가? → 영향도에 따라 M 또는 L
- 설계 결정: 새로운 아키텍처/패턴 도입이 필요한가? → Yes면 L
- 위 모두 No: 파일 수와 변경 단순성으로 S/M 판단
2. 작업 분해 템플릿
요구사항 정리
- [ ] 사용자가 원하는 최종 결과물은?
- [ ] 변경되는 레이어는? (UI / API / Domain / DB)
- [ ] 기존 코드에 영향을 주는 범위는?
작업 단위 분해
각 작업 단위는 독립적으로 테스트 가능한 단위로 나눈다:
1. [작업명] - [대상 파일/모듈] - [티어]
2. [작업명] - [대상 파일/모듈] - [티어]
의존성 확인
- [ ] 작업 간 순서 의존성이 있는가? (예: BE API 먼저 → FE 연동)
- [ ] 외부 의존성이 있는가? (패키지 설치, DB 마이그레이션 등)
3. 계획 출력 형식
사용자에게 계획을 제시할 때 다음 형식을 따른다:
**티어**: S / M / L
**변경 범위**: [레이어 목록]
**작업 목록**:
1. [작업] → [담당 에이전트]
2. [작업] → [담당 에이전트]
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/development-task-planning-mm5t8a53/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/development-task-planning-mm5t8a53' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/development-task-planning-mm5t8a53/download' --output '.skill-downloads/development-task-planning-mm5t8a53/SKILL.md.part' && mv '.skill-downloads/development-task-planning-mm5t8a53/SKILL.md.part' '.skill-downloads/development-task-planning-mm5t8a53/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/development-task-planning-mm5t8a53/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.