---
name: help
description: Context-aware guide — where the project stands and what to do next.
argument-hint: "optional question"
user-invocable: true
---

# Help

Work out where the project actually stands, then say what to do next. Be concrete,
be short.

## 1. Read the state

1. `docs/PRD.md` — still the empty template, or filled in?
2. `features/INDEX.md` — which features exist, at which status?
3. For the active feature, check which sections its spec already has:
   Tech Design (`/architecture`), QA Test Results (`/qa`), Deployment (`/deploy`)
4. Quick scan: `ls src/components/ui/`, `ls src/app/api/ 2>/dev/null`, `ls tests/ 2>/dev/null`

Trust the files over the status column if they disagree — and say so when they do.

## 2. Name the next step

| State | Next step |
|-------|-----------|
| PRD is the empty template | `/init` mit einer kurzen Beschreibung der Idee |
| PRD filled, no features | `/write-spec` für das erste Feature |
| Status Roadmap | `/write-spec PROJ-X` — Spec schreiben |
| Status Planned | `/architecture PROJ-X` — technisches Design |
| Status Architected | `/frontend PROJ-X` — UI bauen |
| Frontend done, needs a server side | `/backend PROJ-X` |
| Implemented, no QA section | `/qa PROJ-X` |
| Status Approved | `/deploy PROJ-X` |
| Everything deployed | `/write-spec` für das nächste Feature aus der PRD-Roadmap |

## 3. Answer the question, if there was one

If the user asked something specific, answer that **first**, then show the status.
Common ones: which skills exist, how to add a feature, how to customize the
template (CLAUDE.md, `.claude/rules/`, `.claude/skills/`), how deployment works
(Docker Compose, `scripts/update.sh` — no Vercel).

## Output

### Stand
_Zwei, drei Sätze: wo das Projekt steht._

### Features
_Tabelle aus INDEX.md._

### Nächster Schritt
_Der eine wichtigste Schritt, mit dem exakten Kommando._

### Sonst möglich
_Kurze Liste weiterer sinnvoller Aktionen._

Give exact commands and real file paths. Do not explain the framework unless asked.