Task Planning — 技能工具
v1.0.0[自动翻译] Plan and organize software development tasks effectively. Use when breaking down features, creating user stories, or planning sprints. Handles task br...
详细分析 ▾
运行时依赖
版本
- Initial release of the task-planning skill. - Provides clear processes for task breakdown, user stories (INVEST principle), epic-story-task decomposition, and sprint planning. - Includes templates, MoSCoW prioritization, and backlog management practices. - Outlines best practices and essential constraints for effective agile planning. - Supports usage on Claude, ChatGPT, and Gemini platforms.
安装命令 点击复制
技能文档
When to use this skill
- 피처 개발: 새 기능을 작은 태스크로 분할
- Sprint Planning: 스프린트에 포함할 작업 선정
- Backlog Grooming: 백로그 정리 및 우선순위 설정
Instructions
Step 1: User Story 작성 (INVEST)
INVEST 원칙:
- Independent: 독립적
- Negotiable: 협상 가능
- Valuable: 가치 있음
- Estimable: 추정 가능
- Small: 작음
- Testable: 테스트 가능
템플릿:
## User Story: [제목]As a [사용자 유형]
I want [기능]
So that [가치/이유]
Acceptance Criteria
- [ ] Given [상황] When [행동] Then [결과]
- [ ] Given [상황] When [행동] Then [결과]
- [ ] Given [상황] When [행동] Then [결과]
Technical Notes
- API endpoint: POST /api/users
- Database: users 테이블
- Frontend: React component
Estimation
- Story Points: 5
- T-Shirt: M
Dependencies
- User authentication must be completed first
Priority
- MoSCoW: Must Have
- Business Value: High
예시:
## User Story: User RegistrationAs a new visitor
I want to create an account
So that I can access personalized features
Acceptance Criteria
- [ ] Given valid email and password When user submits form Then account is created
- [ ] Given duplicate email When user submits Then error message is shown
- [ ] Given weak password When user submits Then validation error is shown
- [ ] Given successful registration When account created Then welcome email is sent
Technical Notes
- Hash password with bcrypt
- Validate email format
- Send welcome email via SendGrid
- Store user in PostgreSQL
Estimation
- Story Points: 5
Dependencies
- Email service integration (#123)
Priority
- MoSCoW: Must Have
Step 2: Epic → Story → Task 분해
## Epic: User Management SystemStory 1: User Registration
- Points: 5
- Tasks:
- [ ] Design registration form UI (2h)
- [ ] Create POST /api/users endpoint (3h)
- [ ] Implement email validation (1h)
- [ ] Add password strength checker (2h)
- [ ] Write unit tests (2h)
- [ ] Integration testing (2h)Story 2: User Login
- Points: 3
- Tasks:
- [ ] Design login form (2h)
- [ ] Create POST /api/auth/login endpoint (2h)
- [ ] Implement JWT token generation (2h)
- [ ] Add "Remember Me" functionality (1h)
- [ ] Write tests (2h)Story 3: Password Reset
- Points: 5
- Tasks:
- [ ] "Forgot Password" UI (2h)
- [ ] Generate reset token (2h)
- [ ] Send reset email (1h)
- [ ] Reset password form (2h)
- [ ] Update password API (2h)
- [ ] Tests (2h)
Step 3: MoSCoW 우선순위
## Feature Prioritization (MoSCoW)Must Have (Sprint 1)
- User Registration
- User Login
- Basic Profile Page
Should Have (Sprint 2)
- Password Reset
- Email Verification
- Profile Picture Upload
Could Have (Sprint 3)
- Two-Factor Authentication
- Social Login (Google, GitHub)
- Account Deletion
Won't Have (This Release)
- Biometric Authentication
- Multiple Sessions Management
Step 4: Sprint Planning
## Sprint 10 PlanningSprint Goal: Complete user authentication system
Duration: 2 weeks
Team Capacity: 40 hours × 4 people = 160 hours
Estimated Velocity: 30 story points
Selected Stories
- User Registration (5 points) - Must Have
- User Login (3 points) - Must Have
- Password Reset (5 points) - Must Have
- Email Verification (3 points) - Should Have
- Profile Edit (5 points) - Should Have
- JWT Refresh Token (3 points) - Should Have
- Rate Limiting (2 points) - Should Have
- Security Audit (4 points) - Must Have
Total: 30 points
Sprint Backlog
- [ ] User Registration (#101)
- [ ] User Login (#102)
- [ ] Password Reset (#103)
- [ ] Email Verification (#104)
- [ ] Profile Edit (#105)
- [ ] JWT Refresh Token (#106)
- [ ] Rate Limiting (#107)
- [ ] Security Audit (#108)
Definition of Done
- [ ] Code written and reviewed
- [ ] Unit tests passing (80%+ coverage)
- [ ] Integration tests passing
- [ ] Documentation updated
- [ ] Deployed to staging
- [ ] QA approved
Output format
태스크 보드 구조
Backlog → To Do → In Progress → Review → DoneBacklog:
- 우선순위별 정렬
- Grooming 완료된 스토리
To Do:
- Sprint에 선택된 작업
- 담당자 할당됨
In Progress:
- WIP Limit: 2 per person
- 진행 중인 작업
Review:
- Code review 대기
- QA 테스트 중
Done:
- DoD 충족
- 배포 완료
Constraints
필수 규칙 (MUST)
- 명확한 AC: Acceptance Criteria 필수
- 추정 완료: 모든 스토리에 포인트 할당
- 의존성 파악: 선행 작업 명시
금지 사항 (MUST NOT)
- 너무 큰 스토리: 13+ points는 분할
- 모호한 요구사항: "개선한다", "최적화한다" 금지
Best practices
- INVEST 원칙: 좋은 사용자 스토리 작성
- Definition of Ready: 스프린트 시작 전 준비 완료
- Definition of Done: 명확한 완료 기준
References
Metadata
버전
- 현재 버전: 1.0.0
- 최종 업데이트: 2025-01-01
- 호환 플랫폼: Claude, ChatGPT, Gemini
태그
#task-planning #user-stories #backlog #sprint-planning #agile #project-managementExamples
Example 1: Basic usage
Example 2: Advanced usage
免费技能或插件可能存在安全风险,如需更匹配、更安全的方案,建议联系付费定制