jackherd 0.0.1 → 1.0.1

package/kit/workflow/skills/plan/references/template-German.md

@@ -0,0 +1,92 @@
+# Titel
+
+**{{kit.heading.date}}:** YYYY-MM-DD
+**{{kit.heading.status}}:** Draft / In Progress / Done / Abandoned
+**{{kit.heading.scope}}:** `betroffene/pfade`
+
+## Problem / Kontext
+
+Was ist der Auslöser? Warum jetzt? Ein Absatz.
+
+## Ist-Zustand
+
+Faktenbasiert: Code-Analyse, Datei-Counts, aktuelle Architektur. Tabellen bevorzugt.
+
+## Soll-Zustand
+
+Was ändert sich konkret? Dateien, Module, Flows.
+
+## {{kit.heading.decisions}}
+
+| Entscheidung | Begründung |
+| ------------ | ---------- |
+
+## {{kit.heading.implementation}}
+
+### {{kit.heading.modelRecommendations}}
+
+| {{kit.heading.phase}} | Modell | Begründung |
+| ----- | ------ | ---------- |
+| 1 — ... | {{kit.model.implement}} | Fehlerkosten × Komplexität |
+
+> **Modell-Anwendung:** `/implement` wendet diese Tabelle selbst an (Schritt 0, Modell-Gate): Jede Phase, deren Empfehlung vom laufenden Modell abweicht, läuft über einen Sub-Agenten mit dem empfohlenen Modell, in beide Richtungen. Wer **ohne** `/implement` umsetzt, setzt das Modell selbst beim Start.
+
+### {{kit.heading.dependencies}}
+
+| {{kit.heading.phase}} | {{kit.heading.dependsOn}} | {{kit.heading.writes}} | {{kit.heading.serialMarker}} |
+| ----- | ------------ | -------- | -------------- |
+| 1 — ... | — | `pfad/zum/modul/` | Migration |
+| 2 — ... | 1 | `anderes/modul/` | — |
+
+> **Parallel-Anwendung:** `/implement` startet bereite Phasen ohne gemeinsamen Schreibpfad und ohne kollidierende Seriell-Marker gleichzeitig (Schritt 0b), jede mit ihrem Modell aus der Tabelle oben. Wer ohne `/implement` umsetzt, liest hier ab, welche Sessions parallel laufen dürfen.
+
+### {{kit.heading.phase}} 1: ...
+
+- [ ] Schritt 1
+- [ ] Schritt 2
+
+**Review-Gate {{kit.heading.phase}} 1:**
+
+- [ ] Pre-Scan: [Dateien und Module, die vor dem Start gelesen werden]
+- [ ] Implementation vollständig und commitbar
+- [ ] Tests geschrieben (oder Begründung, warum keine nötig sind)
+- [ ] `/uncle-bob` — Clean Architecture Review
+- [ ] Dokumentation aktualisiert oder neu angelegt
+- [ ] Roadmap + Detail-Plan synchronisiert
+
+## Tests
+
+Welche Tests sind nötig? Entscheidung nach dem Entscheidungsbaum in `.claude/rules/kit/testing.md`.
+
+| Datei | Art | Warum |
+| ----- | --- | ----- |
+
+> Keine Tests nötig → ausdrücklich begründen (z. B. „nur Layout, kein Logikzweig").
+
+## {{kit.heading.documentation}}
+
+Was wird nach Abschluss dokumentiert?
+
+- [ ] ...
+
+## Verworfene Alternativen
+
+| Idee | Grund |
+| ---- | ----- |
+
+## Risiken
+
+| Risiko | Severity | Mitigation |
+| ------ | -------- | ---------- |
+
+## N — Architekturdokumentation (arc42 light)
+
+> Nach der Implementierung: Architektur-Docs aus dem fertigen Code ableiten.
+
+| #   | Task | Status |
+| --- | ---- | ------ |
+| N.1 | Kontext: externe Systeme und Schnittstellen | ⬜ |
+| N.2 | Bausteinsicht: Services, Packages, Apps | ⬜ |
+| N.3 | Laufzeitsicht: wichtige Abläufe als Sequenzdiagramme | ⬜ |
+| N.4 | Entscheidungen: ADRs aus der Entscheidungstabelle | ⬜ |
+| N.5 | `ARCHITECTURE.md` der berührten Einheiten: neue Invarianten und Risiken | ⬜ |

package/kit/workflow/skills/start/SKILL.md

@@ -0,0 +1,47 @@
+---
+name: start
+description: 'Guided first steps with jackherd: explains the flow, checks the setup, offers the first plan.'
+disable-model-invocation: true
+---
+
+If `.claude/project/start.md` exists, read it first. It extends this skill for this project and wins where the two disagree.
+
+You guide a new user through their first minutes with jackherd. You explain, check and offer; you never write or edit a file. You run only the reading commands in step 2; every fix goes to the user as a command or config line to run themselves.
+
+## 1. The flow, in a few lines
+
+Show this to the user, shortened to what fits on one screen:
+
+- Describe a task. `/plan` writes the plan in `{{kit.planDirectory}}/` and, when asked, a board for parallel lanes.
+- Build it in one session with `/implement`, or run the board's lanes side by side with `/orchestrate` inside herdr.
+- Follow progress with `jh plans`. Inside herdr, `/orchestrate` opens the plan view in a herdr pane beside the coordinator and beside each lane.
+- `/follow <item>` has the watcher report changes of a ticket, issue or status page outside GitHub.
+- herdr is optional, needed only for parallel lanes. The first setup (`jh init`, which the installer runs) offers its installer when it is missing, on Linux and macOS and only when it can ask.
+
+## 2. Check the setup
+
+Run each command on its own. All of them only read. Call the CLI as `jh`, the copy the install put on the `PATH`; only where `command -v jh` finds none, use `bunx jackherd`, and say so in the report.
+
+1. `jh config`: prints the commands and the base branch this repository uses. It reads one file, this repository's `.jackherd/config.json` if it exists, otherwise `~/.jackherd/config.json`, and fails with "not found" when neither exists. Detection only fills values in a file that exists.
+2. The terminal adapter: `config` does not print it, so read the same file. Present means `"terminal": { "adapter": "herdr" }`; no `terminal` entry means `none`.
+3. `command -v herdr`: prints the path when herdr is installed.
+4. `printenv HERDR_ENV`: prints `1` when this session runs inside herdr.
+5. `gh auth status`: reports whether the GitHub CLI is installed and logged in.
+
+Report a short list, one line per item, marked present or missing. For each missing item give the command or line that fixes it:
+
+- Config: `jh init --global`, or `bunx jackherd init` to install the kit into this repository.
+- Terminal adapter: add `"terminal": { "adapter": "herdr" }` to the file from item 2.
+- herdr (optional, only for parallel lanes). You name the command; the user runs it: `sh -c 'installer=$(mktemp) && curl --proto =https --tlsv1.2 -fsSL https://herdr.dev/install.sh -o "$installer" && sh "$installer"; code=$?; rm -f "$installer"; exit $code'` (Linux and macOS; it downloads the official installer whole before running it).
+- Session outside herdr: start Claude Code from a herdr pane.
+- `gh`: install the GitHub CLI (`gh`), then run `gh auth login`.
+
+State plainly that herdr is only needed to run parallel lanes with `/orchestrate`. `/plan`, `/implement` and `jh plans` work without it.
+
+## 3. Offer the first step
+
+Ask through `AskUserQuestion`, in {{kit.responseLanguage}}, with these options (the first one recommended):
+
+- **Start the first plan with `/plan`.** On this answer ask what to build, then run `/plan` with the answer.
+- **Set up what is missing first.** List the steps from the list above that apply, and stop.
+- **Just read.** End here.

package/package.json

@@ -1,9 +1,67 @@
 {
   "name": "jackherd",
-  "version": "0.0.1",
-  "description": "Plan, delegate and ship with parallel coding agents. Coming soon as the successor of @crossdelta/agent-kit.",
-  "license": "MIT",
+  "version": "1.0.1",
+  "description": "Skills, agents and plan tooling for Claude Code projects",
   "author": "crossdelta",
-  "keywords": ["coding-agents", "claude-code", "worktrees", "herdr"],
-  "files": ["README.md"]
+  "license": "MIT",
+  "type": "module",
+  "bin": {
+    "jh": "./src/cli.ts",
+    "jackherd": "./src/cli.ts"
+  },
+  "exports": {
+    "./config": {
+      "bun": "./src/config/index.ts",
+      "types": "./dist/config.d.ts",
+      "import": "./dist/config.js"
+    },
+    "./plan-format": {
+      "bun": "./src/plan-format/index.ts",
+      "types": "./dist/plan-format.d.ts",
+      "import": "./dist/plan-format.js"
+    },
+    "./schemas/jackherd.schema.json": "./schemas/jackherd.schema.json"
+  },
+  "files": [
+    "dist",
+    "kit",
+    "!kit/**/*.test.ts",
+    "herdr-plugin",
+    "!herdr-plugin/**/*.test.ts",
+    "src",
+    "!src/**/*.test.ts",
+    "!src/test-support",
+    "schemas",
+    "docs",
+    "assets",
+    "README.md",
+    "CHANGELOG.md",
+    "LICENSE",
+    "NOTICE",
+    "install.sh"
+  ],
+  "publishConfig": {
+    "access": "public"
+  },
+  "scripts": {
+    "build": "tsup",
+    "dev": "tsup --watch",
+    "clean": "rm -rf dist",
+    "gen": "bun scripts/generate-schema.ts",
+    "lint": "biome check .",
+    "format": "biome format --write .",
+    "test": "bun test"
+  },
+  "dependencies": {
+    "marked": "^16.4.2",
+    "zod": "^4.0.0"
+  },
+  "devDependencies": {
+    "@types/bun": "^1.4.3",
+    "tsup": "^8.5.1",
+    "typescript": "^5.8.3"
+  },
+  "engines": {
+    "bun": ">=1.3.0"
+  }
 }