# Claude Code Spec-Driven Development
Kiro-style Spec Driven Development implementation using claude code slash commands, hooks and agents.
## 実装時の注意事項
### CLIツール開発の原則
- **シンプルに実装する** - 余計な機能を追加しない
- **要件を勝手に追加しない** - 仕様書に書かれたことのみ実装
- **過度な親切は不要** - エラー時の冗長な案内や説明は避ける
- **戦略は事前に決定** - 実行時の条件が分かるなら最初から適切な処理を選択
## Project Context
### Paths
- Steering: `.kiro/steering/`
- Specs: `.kiro/specs/`
- Commands: `.claude/commands/`
### Steering vs Specification
**Steering** (`.kiro/steering/`) - Guide AI with project-wide rules and context
**Specs** (`.kiro/specs/`) - Formalize development process for individual features
### Active Specifications
- Check `.kiro/specs/` for active specifications
- Use `/kiro:spec-status [feature-name]` to check progress
## Development Guidelines
- Think in English, but generate responses in Japanese (思考は英語、回答の生成は日本語で行うように)
## Workflow
### Phase 0: Steering (Optional)
`/kiro:steering` - Create/update steering documents
`/kiro:steering-custom` - Create custom steering for specialized contexts
**Note**: Optional for new features or small additions. Can proceed directly to spec-init.
### Phase 1: Specification Creation
1. `/kiro:spec-init [detailed description]` - Initialize spec with detailed project description
2. `/kiro:spec-requirements [feature]` - Generate requirements document
3. `/kiro:spec-design [feature]` - Interactive: "requirements.mdをレビューしましたか？ [y/N]"
4. `/kiro:spec-tasks [feature]` - Interactive: Confirms both requirements and design review
### Phase 2: Progress Tracking
`/kiro:spec-status [feature]` - Check current progress and phases
## Development Rules
1. **Consider steering**: Run `/kiro:steering` before major development (optional for new features)
2. **Follow 3-phase approval workflow**: Requirements → Design → Tasks → Implementation
3. **Approval required**: Each phase requires human review (interactive prompt or manual)
4. **No skipping phases**: Design requires approved requirements; Tasks require approved design
5. **Update task status**: Mark tasks as completed when working on them
6. **Keep steering current**: Run `/kiro:steering` after significant changes
7. **Check spec compliance**: Use `/kiro:spec-status` to verify alignment
8. **Commit frequently**: タスクが完了するごとに @git-commit-expert サブエージェントを呼び出してコミットを実行する。小さな論理的単位でこまめにコミットすることで、変更履歴を明確に保つ
## Steering Configuration
### Current Steering Files
Managed by `/kiro:steering` command. Updates here reflect command changes.
### Active Steering Files
- `product.md`: Always included - Product context and business objectives
- `tech.md`: Always included - Technology stack and architectural decisions
- `structure.md`: Always included - File organization and code patterns
### Custom Steering Files
### Inclusion Modes
- **Always**: Loaded in every interaction (default)
- **Conditional**: Loaded for specific file patterns (e.g., `"*.test.js"`)
- **Manual**: Reference with `@filename.md` syntax
-