From rn-launch-harness
Breaks down PRD into prioritized file-level task checklists under docs/specs/ organized by feature and phases for React Native progress tracking.
npx claudepluginhub tjdrhs90/rn-launch-harness --plugin rn-launch-harnessThis skill is limited to using the following tools:
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).
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Guides code writing, review, and refactoring with Karpathy-inspired rules to avoid overcomplication, ensure simplicity, surgical changes, and verifiable success criteria.
Executes ctx7 CLI to fetch up-to-date library documentation, manage AI coding skills (install/search/generate/remove/suggest), and configure Context7 MCP. Useful for current API refs, skill handling, or agent setup.
Share bugs, ideas, or general feedback.
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).
Called by the orchestrator after Phase 2 (Plan) completes.
docs/harness/plans/YYYY-MM-DD-prd.md (PRD from Phase 2)docs/harness/config.mdRead 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:
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...).
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:
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).
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
Task format rules:
- [ ]— (em dash) and a brief descriptionCreate docs/specs/README.md as a progress dashboard:
# Spec Dashboard
> Generated: YYYY-MM-DD
> Source PRD: docs/harness/plans/YYYY-MM-DD-prd.md
## Progress Overview
| # | Feature | Phase 1 | Phase 2 | Phase 3 | Status |
|---|---------|---------|---------|---------|--------|
| 01 | auth | 0/12 | 0/8 | - | not-started |
| 02 | home | 0/9 | 0/5 | - | not-started |
| 03 | profile | 0/7 | - | - | not-started |
## Feature Details
### 01-auth
- Phase 1: MVP - Authentication (12 tasks)
- Phase 2: Enhancement - Auth polish (8 tasks)
### 02-home
- Phase 1: MVP - Home feed (9 tasks)
- Phase 2: Enhancement - Feed optimization (5 tasks)
...
## Future Scope (P2)
- [ ] Feature X — deferred to post-launch
- [ ] Feature Y — deferred to post-launch
Present the spec structure summary via AskUserQuestion:
---
feature: {feature-name} # Matches directory name (without NN prefix)
phase: {1|2|3} # Implementation phase
title: {phase title} # Human-readable title
status: {not-started|in-progress|completed}
created: {YYYY-MM-DD}
updated: {YYYY-MM-DD}
---
During Phase 5 (Generator), as the Generator implements each file:
- [ ] to - [x]updated datestatus: completeddocs/specs/README.md dashboard counts (e.g., 3/12)not-started — 0 tasks completedin-progress — at least 1 task completedcompleted — all tasks completeddocs/specs/
├── 01-{feature}/
│ ├── phase1-mvp.md
│ ├── phase2-enhancement.md
│ └── phase3-polish.md (optional)
├── 02-{feature}/
│ ├── phase1-mvp.md
│ └── phase2-enhancement.md
├── ...
└── README.md
current_phase: design
next_role: rn-harness-design