rn-harness-spec

rn-harness-spec — Phase 2.5: Spec Planning

Breaks down the PRD into file-level task checklists under docs/specs/, organized by feature and implementation phase. Sits between Plan (Phase 2) and Design (Phase 3).

Trigger

Called by the orchestrator after Phase 2 (Plan) completes.

Input

• docs/harness/plans/YYYY-MM-DD-prd.md (PRD from Phase 2)
• docs/harness/config.md

Process

Step 1: Extract Feature List

Read the PRD and extract the full list of features to implement. Map each feature to the FSD module structure defined in the PRD (features/, entities/, widgets/, shared/).

Sort features by priority:

• P0 features first (MVP required)
• P1 features next (important)
• P2 features last (future roadmap)

Step 2: Create Feature Spec Directories

For each feature, create a numbered directory under docs/specs/:

docs/specs/
├── 01-auth/
├── 02-home/
├── 03-profile/
├── ...
└── README.md

The NN prefix reflects implementation priority order (01, 02, 03...).

Step 3: Generate Phase Files

Inside each feature directory, create phase markdown files:

docs/specs/01-auth/
├── phase1-mvp.md           # Core MVP functionality
├── phase2-enhancement.md   # Enhancements and extensions
└── phase3-polish.md        # Optimization and polish (if needed)

Phase breakdown rules:

• Phase 1 (MVP): Minimum viable implementation — types, API, store, core UI, screen, barrel export
• Phase 2 (Enhancement): Extended features — validation, error states, loading states, edge cases
• Phase 3 (Polish): Optimization — animations, accessibility, performance tuning

P0 features should have at least Phase 1 and Phase 2. P1 features may only have Phase 1. P2 features are documented but not given phase files (noted in README as future scope).

Step 4: Write Tasks in Checkbox Format

Each phase file must follow this exact structure:

---
feature: auth
phase: 1
title: MVP - Authentication
status: not-started
created: YYYY-MM-DD
updated: YYYY-MM-DD
---

# Phase 1: MVP - Authentication

## Tasks

### Entity Setup
- [ ] `src/entities/user/types/index.ts` — IUser interface definition
- [ ] `src/entities/user/store/index.ts` — Zustand user store

### Feature Implementation
- [ ] `src/features/auth/api/auth.api.ts` — Login/signup API calls
- [ ] `src/features/auth/hooks/useLogin.ts` — Login mutation hook
- [ ] `src/features/auth/hooks/useRegister.ts` — Signup mutation hook
- [ ] `src/features/auth/store/index.ts` — Token management store
- [ ] `src/features/auth/ui/LoginForm.tsx` — Login form component
- [ ] `src/features/auth/types/index.ts` — Auth-related types
- [ ] `src/features/auth/index.ts` — Barrel export

### Screen Implementation
- [ ] `app/(auth)/login.tsx` — Login screen
- [ ] `app/(auth)/register.tsx` — Register screen

### QA
- [ ] typecheck passes
- [ ] lint passes
- [ ] feature functions correctly