petrogurcak/finish

Finish

Orchestrate all post-execution phases. One command to go from "done coding" to "merged and wrapped up".

Announce: "Spoustim finish - verify, demo, merge, QA kroky, wrapup."

Project State (auto-injected)

Branch: !git branch --show-current

Latest plan

!ls -t docs/plans/*.md 2>/dev/null | head -1

Uncommitted changes

!git diff --stat HEAD

When to Use

• After all tasks from implementation plan are complete
• User says "finish" / "dokonci" / "hotovo" / "zabal to"
• Execution skill (subagent/session/team) reports all tasks done

Flow

/development:finish
  ├─ Phase 5:  Verify    → tests, build, lint, plan checklist, browser smoke
  ├─ Phase 5b: Demo      → executable demo document (optional)
  ├─ Phase 6:  Merge     → commit, merge to development, cleanup
  ├─ Phase 6b: QA Steps  → automatic manual testing checklist
  └─ Phase 7:  Wrapup    → context, mistakes, lessons, docs

Each phase gates the next. Failures stop the flow until resolved.

Process

Phase 5: Verify

Invoke: development:verify

Run full verification suite:

• Tests, build, lint/types
• Plan task completion check
• Browser smoke test (optional, for UI features)

Gate: ALL checks must pass before continuing.

• If failures: fix, re-run verify. Do NOT proceed.
• If pass: announce results and continue.

Phase 5b: Demo (optional)

Ask: "Feature ma UI nebo API? Chces vytvorit demo dokument?"

| Answer | Action | | -------------------- | --------------------------------------------------------- | | Yes / ano | Invoke: development:demo - create showboat document | | No / ne / skip | Skip, continue to merge | | Refactoring / config | Skip automatically (no visible output to demo) |

Phase 6: Merge

Invoke: development:merge

• Commit current work
• Merge to development branch
• Verify on development (tests + build)
• Delete feature branch / worktree

Gate: Merge + verification on development must succeed.

Phase 6b: QA Steps (automatic)

No asking — always generate after successful merge.

Generate practical manual testing steps based on:

1. Read the plan — docs/plans/*.md or ~/.claude/plans/*.md for the feature
2. Read the diff — git log development --oneline -5 + git diff HEAD~1..HEAD --stat to see what changed
3. Read ARCHITECTURE.md — for app URLs, ports, access info

Output format:

## Jak otestovat

**Feature:** <co bylo implementovano>
**Kde:** <URL / CLI command / app location>

### Kroky

1. <konkretni akce — klikni, otevri, zadej>
   → Ocekavany vysledek: <co by se melo stat>

2. <dalsi akce>
   → Ocekavany vysledek: <...>

3. ...

### Edge cases

- <co zkusit navic — prazdny input, refresh, jiny jazyk, mobilni pohled>

### Regrese

- <co overit ze se nerozbilo — existujici funkce ktere mohly byt dotcene>

Rules for QA steps:

• Max 5-8 kroků — hlavní happy path, ne exhaustivni test suite
• Konkrétní — "klikni na 'Uložit'" ne "otestuj uložení"
• Včetně URL/portu — "otevři http://localhost:5173/settings"
• Edge cases — 2-3 důležité, ne každý možný
• Regrese — jen pokud diff ukazuje změny v sdíleném kódu
• Jazyk — česky (matching user preference)

Save to file: docs/qa/YYYY-MM-DD-<feature-name>.md

mkdir -p docs/qa
# Write QA steps to file

Also output to terminal — user sees it immediately without opening a file.

Phase 7: Wrapup

Invoke: development:wrapup

• Save ACTIVE_CONTEXT.md
• Check for mistakes to log
• Check for lessons learned
• Check for documentation updates

Final Report

Finish kompletni:
- Verify: PASS (testy X/X, build OK, lint OK)
- Demo: [vytvoreno: docs/demos/... / preskoceno]
- Merge: <branch> merged do development, branch smazan
- QA kroky: docs/qa/YYYY-MM-DD-<feature>.md (X kroku, Y edge cases)
- Wrapup: kontext ulozen, [mistakes/lessons: zadne | zapsano]

Hotovo.

Error Recovery

| Error | Action | | ---------------------------- | ----------------------------------------------- | | Tests fail in verify | Fix + re-run verify, don't proceed | | Merge conflict | Resolve conflict, re-run tests on development | | Tests fail on development | Fix on development, re-run, don't leave broken | | Demo fails (showboat/rodney) | Skip demo, continue to merge (demo is optional) |

Rules

• Sequential, gated - each phase must pass before next starts
• Demo is optional - never block merge because of demo failure
• Individual skills still work - user can call /development:verify, /development:demo, /development:merge, /development:wrapup separately at any time
• Don't re-ask what verify already confirmed - carry results forward