@skyf0xx/hedgehog 3.0.4 → 3.0.6

package/README.md

@@ -88,21 +88,20 @@ Artifact
 
 ### Anything else
 
-A CLI, a library, a browser extension, a data pipeline, a compiler — a
-project fitting neither shape gets its own build order, designed from
-your planning documents at intake rather than chosen from a menu. Run
-`init` with no core flag: planning intake names the system shape, picks
+A CLI, a library, a browser extension, a data pipeline, etc. fitting neither shape gets its own build order, designed at intake rather than chosen from a menu.
+
+Run `init` with no core flag: planning intake names the system shape, picks
 the stack, derives the layers, and locks them to `.hedgehog/core.yaml`,
 then generates that workspace and builds it one verified layer at a time.
 
-The layers are bespoke, the enforcement is the same — ordered steps,
-scoped file access, a verification command per layer, one commit each.
+The enforcement remains the same: ordered steps,
+scoped file access and a verification command per layer.
 
 ![Why Hedgehog works: a different way to build with AI, comparing traditional AI workflow to Hedgehog](https://raw.githubusercontent.com/skyf0xx/hedgehog/master/docs/images/why.png)
 
 ## Install
 
-From an empty project folder, ask Claude to run:
+From an empty project folder, run:
 
 ``` bash
 # Full-stack app
@@ -115,7 +114,29 @@ npx @skyf0xx/hedgehog init --landing-page
 npx @skyf0xx/hedgehog init
 ```
 
-Then open Claude Code and describe what you want to build.
+Then open your coding agent and describe what you want to build.
+
+### Coding agents
+
+Hedgehog installs for **Claude Code** by default. Add a host flag to
+install for another one, or several at once:
+
+``` bash
+npx @skyf0xx/hedgehog init --cursor              # Cursor
+npx @skyf0xx/hedgehog init --gemini              # Gemini CLI
+npx @skyf0xx/hedgehog init --host=claude,cursor  # both
+npx @skyf0xx/hedgehog init --all-hosts           # every supported agent
+```
+
+Each one gets the discipline in its own native shape — agents and skills
+in the directory it reads, and the instructions file it loads at session
+start (`CLAUDE.md`, `HEDGEHOG.md`, or `GEMINI.md`).
+
+Every install also writes **`AGENTS.md`** at the repo root: an index of
+every agent and skill, when each applies, and the build loop. Coding
+agents that read `AGENTS.md` — Codex, Copilot CLI, OpenCode, and others —
+work from that index, following the same ordered steps and the same
+`hedgehog verify` gate.
 
 Plain `init` (no core flag) installs the agents, skills, and build graph
 that every core shares. Planning intake designs an opinionated build
@@ -129,9 +150,20 @@ To update:
 npx @skyf0xx/hedgehog update
 ```
 
-This refreshes `.claude/agents/` and `.claude/skills/` only. It never
-touches `CLAUDE.md`, the build graph, the core workspace, or
-`skills/BMAD`, since those carry project-specific or write-once content.
+This refreshes the installed agents and skills — for every coding agent
+the project was set up for — along with the `AGENTS.md` index derived
+from them. It never touches the instructions file, the build graph, the
+core workspace, or `skills/BMAD`, since those carry project-specific or
+write-once content.
+
+To see the build graph:
+
+``` bash
+npx @skyf0xx/hedgehog graph
+```
+
+Starts a small local server and opens a live, read-only diagram of every
+task, status and its dependencies.
 
 ## Why Hedgehog