{"id":"feature-planning","name":"feature-planning","summary":"機能リクエストを詳細で実行可能な計画に分解し、明確なタスクを提示しましょう。ユーザーが新機能、拡張機能、または複雑な変更を要望した場合に利用してください。","body":"# Feature Planning\n\nSystematically analyze feature requests and create detailed, actionable implementation plans.\n\n## When to Use\n\n- Requests new feature (\"add user authentication\", \"build dashboard\")\n- Asks for enhancements (\"improve performance\", \"add export\")\n- Describes complex multi-step changes\n- Explicitly asks for planning (\"plan how to implement X\")\n- Provides vague requirements needing clarification\n\n## Planning Workflow\n\n### 1. Understand Requirements\n\n**Ask clarifying questions:**\n- What problem does this solve?\n- Who are the users?\n- Specific technical constraints?\n- What does success look like?\n\n**Explore the codebase:**\nUse Task tool with `subagent_type='Explore'` and `thoroughness='medium'` to understand:\n- Existing architecture and patterns\n- Similar features to reference\n- Where new code should live\n- What will be affected\n\n### 2. Analyze & Design\n\n**Identify components:**\n- Database changes (models, migrations, schemas)\n- Backend logic (API endpoints, business logic, services)\n- Frontend changes (UI, state, routing)\n- Testing requirements\n- Documentation updates\n\n**Consider architecture:**\n- Follow existing patterns (check CLAUDE.md)\n- Identify reusable components\n- Plan error handling and edge cases\n- Consider performance implications\n- Think about security and validation\n\n**Check dependencies:**\n- New packages/libraries needed\n- Compatibility with existing stack\n- Configuration changes required\n\n### 3. Create Implementation Plan\n\nBreak feature into **discrete, sequential tasks**:\n\n```markdown\n## Feature: [Feature Name]\n\n### Overview\n[Brief description of what will be built and why]\n\n### Architecture Decisions\n- [Key decision 1 and rationale]\n- [Key decision 2 and rationale]\n\n### Implementation Tasks\n\n#### Task 1: [Component Name]\n- **File**: `path/to/file.py:123`\n- **Description**: [What needs to be done]\n- **Details**:\n  - [Specific requirement 1]\n  - [Specific requirement 2]\n- **Dependencies**: None (or list task numbers)\n\n#### Task 2: [Component Name]\n...\n\n### Testing Strategy\n- [What types of tests needed]\n- [Critical test cases to cover]\n\n### Integration Points\n- [How this connects with existing code]\n- [Potential impacts on other features]\n```\n\n**Include specific references:**\n- File paths with line numbers (`src/utils/auth.py:45`)\n- Existing patterns to follow\n- Relevant documentation\n\n### 4. Review Plan with User\n\nConfirm:\n- Does this match expectations?\n- Missing requirements?\n- Adjust priorities or approach?\n- Ready to proceed?\n\n### 5. Execute with plan-implementer\n\nLaunch plan-implementer agent for each task:\n\n```\nTask tool with:\n- subagent_type: 'plan-implementer'\n- description: 'Implement [task name]'\n- prompt: Detailed task description from plan\n```\n\n**Execution strategy:**\n- Implement sequentially (respect dependencies)\n- Verify each task before next\n- Adjust plan if issues discovered\n- Let test-fixing skill handle failures\n- Let git-pushing skill handle commits\n\n## Best Practices\n\n**Planning:**\n- Start broad, then specific\n- Reference existing code patterns\n- Include file paths and line numbers\n- Think through edge cases upfront\n- Keep tasks focused and atomic\n\n**Communication:**\n- Explain architectural decisions\n- Highlight trade-offs and alternatives\n- Be explicit about assumptions\n- Provide context for future maintainers\n\n**Execution:**\n- Implement one task at a time\n- Verify before moving forward\n- Keep user informed\n- Adapt based on discoveries\n\n## Integration\n\n- **plan-implementer agent**: Receives task specs, implements\n- **test-fixing skill**: Auto-triggered on test failures\n- **git-pushing skill**: Triggered for commits","author":"@mhattingpete","ownerProfile":null,"authorContacts":null,"sourceUrl":"https://github.com/mhattingpete/claude-skills-marketplace/tree/main/engineering-workflow-plugin/skills/feature-planning","license":"Apache-2.0","category":"coding","lang":"en","tokens":796,"stars":0,"calls30d":2,"claimed":false,"visibility":"public","origin":"crawler","version":"0.1.0","createdAt":"2026-08-22","updatedAt":"2026-08-22","files":[{"path":"references/planning-best-practices.md","size":10881,"sha256":"810ae496aa4ab569e0e9f57ab8d2cff0f36efdfa5640706df6ba244ccee6d174"}],"requires":{"mcp":[],"tools":[]},"safety":{"flags":[],"scannedAt":"2026-08-22","hasScripts":false,"networkEndpoints":[]}}