claude-soul: Command for Claude Code

breakdown-design Command

Create a detailed step-by-step implementation plan for $ARGUMENTS with comprehensive before/after code examples create file at .docs/year(YYYY)/month(MM)/day(DD)/{number-in-DD-folder(01)}-{Feature Spec}/{Feature Spec}-implementation-plan.md if requirement is clear or no have follow up question. think hard and provide a comprehensive implementation plan with before/after code examples for each step. follow YAGNI principle so dont create dead code or unnecessary files. max 29000 characters. If the result exceeds 29000 characters, leave it as is — do NOT truncate, summarize, or drop sections to fit the limit. Completeness of the implementation plan takes precedence over the character cap.

Template Structure

Step-by-Step Implementation Plan with Before/After Code

Provide a breakdown that includes:

1. Clear Step Numbering: Each step should be numbered and have a descriptive title
2. Before/After Code Blocks: Show exact code changes for each step (add comments for code what you are changing)
3. Technical Rationale: Explain why each change is needed
4. Dependencies: Note any imports or setup required
5. Testing Considerations: How to verify each step works
6. Observability logging: Add logging at the appropriate level — see §Observability for the full Decision Guide:
   • Timber.e(throwable, "…") — errors with a Throwable (records a non-fatal in Crashlytics)
   • Timber.e("…") — errors without a Throwable (breadcrumb + pattern scan)
   • Timber.w("…") — degraded-behaviour paths in real app logic (breadcrumb + pattern scan)
   • Timber.d("…") — diagnostics + monitoring/instrumentation chatter (breadcrumb only)
   • Timber.i("…") — lifecycle / info-level milestones (breadcrumb only) Fall back to Log.d/i/w/e("TAG", "…") if Timber is not on the module classpath.
7. Unit Testing: Include unit tests for each step
8. Flow Diagram Update: Include an ASCII flow diagram showing the BEFORE and AFTER user/data flow (screen transitions, ViewModel ↔ UseCase ↔ Repository calls, branches, side-effects). Use ASCII box-drawing (┌─┐ │ └─┘ → ↓ ↑) — no Mermaid, no images. If the change does not alter any flow (pure refactor / cosmetic), write Flow Diagram: N/A — no flow change and explain in one line why.