Execution Plan: Shoe Choo

Detailed Analysis Summary

Change Impact Assessment

• User-facing changes: Yes — entire application is user-facing (WYSIWYG editor, focus mode, export, sidebar)
• Structural changes: Yes — new macOS application with MVVM architecture, TextKit 2 editor engine
• Data model changes: Yes — document model, editor state, image asset management
• API changes: N/A — desktop app, no external APIs
• NFR impact: Yes — performance (sub-16ms keystroke latency), security (App Sandbox, Hardened Runtime)

Risk Assessment

• Risk Level: Medium — TextKit 2 WYSIWYG rendering is the primary technical risk; well-understood NSDocument and SwiftUI patterns reduce other risks
• Rollback Complexity: Easy — greenfield project, no existing users
• Testing Complexity: Moderate — WYSIWYG rendering requires visual verification; parser/export/file operations are unit-testable

Workflow Visualization

flowchart TD
    Start(["User Request"])

    subgraph INCEPTION["INCEPTION PHASE"]
        WD["Workspace Detection<br/><b>COMPLETED</b>"]
        RA["Requirements Analysis<br/><b>COMPLETED</b>"]
        US["User Stories<br/><b>COMPLETED</b>"]
        WP["Workflow Planning<br/><b>COMPLETED</b>"]
        AD["Application Design<br/><b>EXECUTE</b>"]
        UG["Units Generation<br/><b>EXECUTE</b>"]
    end

    subgraph CONSTRUCTION["CONSTRUCTION PHASE"]
        FD["Functional Design<br/><b>EXECUTE</b>"]
        NFRA["NFR Requirements<br/><b>EXECUTE</b>"]
        NFRD["NFR Design<br/><b>SKIP</b>"]
        ID["Infrastructure Design<br/><b>SKIP</b>"]
        CG["Code Generation<br/><b>EXECUTE</b>"]
        BT["Build and Test<br/><b>EXECUTE</b>"]
    end

    Start --> WD
    WD --> RA
    RA --> US
    US --> WP
    WP --> AD
    AD --> UG
    UG --> FD
    FD --> NFRA
    NFRA --> CG
    CG -->|Next Unit| FD
    CG --> BT
    BT --> End(["Complete"])

    style WD fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff
    style RA fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff
    style US fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff
    style WP fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff
    style AD fill:#FFA726,stroke:#E65100,stroke-width:3px,stroke-dasharray: 5 5,color:#000
    style UG fill:#FFA726,stroke:#E65100,stroke-width:3px,stroke-dasharray: 5 5,color:#000
    style FD fill:#FFA726,stroke:#E65100,stroke-width:3px,stroke-dasharray: 5 5,color:#000
    style NFRA fill:#FFA726,stroke:#E65100,stroke-width:3px,stroke-dasharray: 5 5,color:#000
    style NFRD fill:#BDBDBD,stroke:#424242,stroke-width:2px,stroke-dasharray: 5 5,color:#000
    style ID fill:#BDBDBD,stroke:#424242,stroke-width:2px,stroke-dasharray: 5 5,color:#000
    style CG fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff
    style BT fill:#4CAF50,stroke:#1B5E20,stroke-width:3px,color:#fff
    style Start fill:#CE93D8,stroke:#6A1B9A,stroke-width:3px,color:#000
    style End fill:#CE93D8,stroke:#6A1B9A,stroke-width:3px,color:#000
    style INCEPTION fill:#BBDEFB,stroke:#1565C0,stroke-width:3px,color:#000
    style CONSTRUCTION fill:#C8E6C9,stroke:#2E7D32,stroke-width:3px,color:#000

    linkStyle default stroke:#333,stroke-width:2px

Text Alternative

Phase 1: INCEPTION
  - Workspace Detection (COMPLETED)
  - Requirements Analysis (COMPLETED)
  - User Stories (COMPLETED)
  - Workflow Planning (COMPLETED)
  - Application Design (EXECUTE)
  - Units Generation (EXECUTE)

Phase 2: CONSTRUCTION (per-unit loop)
  - Functional Design (EXECUTE, per-unit)
  - NFR Requirements (EXECUTE, per-unit)
  - NFR Design (SKIP)
  - Infrastructure Design (SKIP)
  - Code Generation (EXECUTE, per-unit)
  - Build and Test (EXECUTE)

Phases to Execute

INCEPTION PHASE

• Workspace Detection (COMPLETED)
• Requirements Analysis (COMPLETED)
• User Stories (COMPLETED)
• Workflow Planning (COMPLETED)
• Application Design - EXECUTE
  • Rationale: New application requires component identification, service layer design, and dependency mapping. 8 epics with 26 stories need structured component architecture.
• Units Generation - EXECUTE
  • Rationale: Complex project with multiple subsystems (editor engine, document management, export, sidebar) benefits from decomposition into parallel units of work.

CONSTRUCTION PHASE (per-unit)

• Functional Design - EXECUTE
  • Rationale: TextKit 2 WYSIWYG engine requires detailed business logic design. Document model, parser integration, and rendering pipeline need formal specification before code generation.
• NFR Requirements - EXECUTE
  • Rationale: Performance targets (sub-16ms latency, <50MB memory), App Sandbox entitlements, and Hardened Runtime require explicit NFR specification. Security Baseline extension is enabled.
• NFR Design - SKIP
  • Rationale: Desktop macOS app with no cloud infrastructure. NFR patterns (caching, scaling) are straightforward for a native app — performance optimization can be addressed during implementation.
• Infrastructure Design - SKIP
  • Rationale: No cloud infrastructure, no server deployment. Distribution is via GitHub Releases with notarization — handled in Build and Test.
• Code Generation - EXECUTE (ALWAYS)
  • Rationale: Implementation planning and Swift/SwiftUI code generation for all units.
• Build and Test - EXECUTE (ALWAYS)
  • Rationale: Xcode build, XCTest/Swift Testing, notarization instructions.

OPERATIONS PHASE

• Operations - PLACEHOLDER
  • Rationale: Future deployment and monitoring workflows.

Tool Strategy (per ツール比較)

Based on the spec-driven development tool comparison, the recommended tools per phase:

Transition Point: After AI-DLC Code Generation planning (Part 1), switch to tsumiki:kairo-tasks for 1-day granularity task splitting, then tsumiki:kairo-loop for automated TDD implementation.

Success Criteria

• Primary Goal: Working MVP of Shoe Choo with WYSIWYG editing, focus mode, and export
• Key Deliverables:
  • Xcode project with SwiftUI + AppKit app
  • TextKit 2 WYSIWYG Markdown editor
  • Focus mode and typewriter scrolling
  • NSDocument-based file management
  • HTML and PDF export
  • App Sandbox + Hardened Runtime + Developer ID signing
• Quality Gates:
  • All unit tests passing (parser, document model, export)
  • App Sandbox entitlements validated
  • Notarization successful
  • Cold launch < 1 second
  • Memory < 50MB on typical documents