Launch Spec Kit

## Overview
Launch Spec Kit turns a rough product idea into a clean implementation handoff: a PRD, an execution plan, and documentation that the next builder can actually use.

## Quick Start
1. Start with `github-prd` to convert the idea into a Product Requirements Document. Capture the executive summary, user stories, technical specifications, scope boundaries, and risk analysis.
2. Use `sickn33-plan-writing` to break the PRD into structured work: milestones, dependencies, acceptance criteria, and verification steps for each implementation phase.
3. Finish with `github-documentation-writer` to package the outcome into Diataxis-style documentation, separating tutorials, how-to guides, explanations, and reference material.

## Key Commands
- `github-prd` — Generate a high-quality PRD for software systems or AI-powered features, including user stories and risk analysis.
- `sickn33-plan-writing` — Build a structured execution plan with task breakdowns, dependencies, and verification criteria.
- `github-documentation-writer` — Produce Diataxis-based documentation so the final handoff is organized and maintainable.

## Tips
- Run the flow in order: PRD first, plan second, documentation last. Reordering it usually creates duplicate work.
- Treat acceptance criteria from `sickn33-plan-writing` as the source of truth for review and QA.
- Use `github-documentation-writer` after scope is stable; it is best for turning settled decisions into docs, not for deciding scope.
- For larger launches, keep the PRD, plan, and docs as separate artifacts so product, engineering, and support can each consume the right level of detail.