Deep Breakdown Skill

Read .hackathon/ARCHITECTURE.md and .hackathon/contracts/ first.

Hard gate: Architecture must be complete.

Process

For EACH major component identified in the architecture, create a detailed spec file in .hackathon/specs/[component-name].md.

Spec Template

---
owner: [assigned dev]
status: draft
created-at: [timestamp]
last-modified: [timestamp]
phase: breakdown
component: [component-name]
estimated-hours: [number]
priority: [critical | high | medium | low]
---

# [Component Name] Specification

## Purpose
[What this component does and why it exists]

## User Stories
- As a [user], I want to [action], so that [benefit]

## Detailed Requirements
### Functional
- [Requirement 1]
- [Requirement 2]

### Non-Functional
- Performance: [expectations]
- Error handling: [strategy]

## Technical Design

### Files to Create
- `apps/[app]/src/[path]/[file].ts` — [purpose]
- `apps/[app]/src/[path]/[file].ts` — [purpose]

### Key Functions/Classes
- `functionName(params): ReturnType` — [what it does]

### Dependencies
- Internal: [which shared packages/other components]
- External: [which npm packages]

### Data Flow
[How data moves through this component]

## API Endpoints Owned
[Reference to specific routes in contracts/api-routes.md]

## Edge Cases
- [Edge case 1]: [how to handle]
- [Edge case 2]: [how to handle]

## Testing Strategy
- [What to test and how]

## Implementation Tasks
Ordered by dependency:
1. [ ] [Task — e.g., "Create route handler for POST /documents/upload"]
2. [ ] [Task — e.g., "Implement OCR processing pipeline"]
3. [ ] [Task — e.g., "Add error handling for corrupt files"]
4. [ ] [Task — e.g., "Write integration test for upload→process flow"]

## Mock Strategy
[How to mock this component's dependencies during development]

Approach

If the team has 2+ developers, consider spinning up parallel subagents to spec out independent components simultaneously. Use the spec-writer agent for this.

After all specs are written:

1. Cross-reference specs against contracts — ensure they're consistent
2. Identify any gaps (routes in contracts not covered by specs, or spec requirements not reflected in contracts)
3. Update contracts if gaps are found (this is the last chance before they get locked)

Output

• .hackathon/specs/[component].md for each component
• Updated contracts (if gaps found)
• Updated STATE.md
• Log to changelog