Skip to content

CLAUDE.md

Latest commit

 

History

History
87 lines (57 loc) · 3.36 KB

CLAUDE.md

File metadata and controls

87 lines (57 loc) · 3.36 KB
Raw

Claude Code Spec-Driven Development

Kiro-style Spec Driven Development implementation using claude code slash commands, hooks and agents.

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
  • readme-creation: プロジェクトのREADME.mdファイルを作成
  • code-refactoring: プロジェクト全体のコードリファクタリング

Development Guidelines

  • Think in English, but generate responses in Japanese (思考は英語、回答の生成は日本語で行うように)
  • API更新ルール: API関連の作業（エンドポイントの追加・変更・削除）を行った際は、必ずOpenAPI仕様書（api.yaml）を更新すること
  • ビルド確認ルール: タスク完了時は必ずビルド（./gradlew build -x detekt）とアプリケーション起動（./gradlew bootRun）を確認すること

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. You 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: "Have you reviewed 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

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