@skyf0xx/hedgehog 2.0.13 → 3.0.0

package/src/templates/CLAUDE.core.landing-page.md

@@ -19,11 +19,13 @@ pinned icon source. Neither restates the other's decision.
 ### The skills — invoke these, don't improvise
 
 - **`hedgehog-landing-loop`** — every unit of work once bootstrapped:
-  pick the next step from `TODO.md`, run exactly one Chain Method phase
-  through its owning agent, gate it, commit it, check it off. Also holds
-  the Correction Protocol for fixing a wrong upstream phase (e.g. a
-  signature element that doesn't trace back to the subject statement).
-  Invoke it at the start of any build session and for "what's next".
+  `hedgehog next` emits the packet for one ready compiled layer, run the
+  fine-grained Chain Method phases it bundles through their owning
+  agents, gate the layer via `hedgehog verify`, which commits it on a
+  pass. Also holds the Correction Protocol for fixing a wrong upstream
+  phase (e.g. a signature element that doesn't trace back to the subject
+  statement). Invoke it at the start of any build session and for
+  "what's next".
 - **`hedgehog-bootstrap-landing-page-core`** — run **once**, at project
   start, to land the pre-verified Astro + Tailwind workspace. Skip if
   `astro.config.mjs` already exists.
@@ -47,8 +49,9 @@ pinned icon source. Neither restates the other's decision.
 
 - **`planner`** — planning intake (which core applies, then this core's
   own brief intake: the vendored BMAD-METHOD shelf, run in full and
-  mined into subject, audience, single page job) at project start.
-  Writes `TODO.md`, `.hedgehog/BMAD/`, and `.hedgehog/chain/00-brief.md`.
+  mined into subject, audience, single page job) at project start. Writes
+  the `landing` intent (`hedgehog intent add`, one call — this core has
+  no module axis), `.hedgehog/BMAD/`, and `.hedgehog/chain/00-brief.md`.
   On first run, hands off to the `bootstrap` agent once Confirm & Lock
   holds.
 - **`bootstrap`** — runs `hedgehog-bootstrap-landing-page-core`'s steps.
@@ -145,6 +148,7 @@ src/
   assets/             raster images, imported as modules and rendered through astro:assets `<Image />`
   styles/             global.css — @fontsource-variable imports + Tailwind v4 CSS-first import + the `@theme` token layer (hex values, font families, `--text-*` scale, spacing unit, easing family from Step 5)
 .hedgehog/
+  hedgehog.db         the build graph — the landing intent, its five compiled tasks, verifications, committed to git
   BMAD/               vendored BMAD-METHOD shelf's raw output (brief, PR-FAQ, PRD, UX spec, research) —
                        write-once, from planner
   chain/              this core's own archival planning intake output — subject statement, adjective tables,

package/src/templates/CLAUDE.md

@@ -17,7 +17,7 @@
 {{PROJECT_SUMMARY — 2–4 sentences the `planner` writes at planning
 intake: what this project is, who it's for, and what it does. State
 current intent, not history. Keep it tight — the full product narrative
-lives in this core's own planning-intake output and `TODO.md`, not
+lives in this core's own planning-intake output and the build graph, not
 here.}}
 
 This project is built with **Hedgehog**: a one-step-at-a-time build
@@ -33,17 +33,16 @@ then hand straight to `planner`, which decides which Hedgehog core
 applies and runs that core's planning intake. Don't re-explain the
 discipline or summarize this file; the greeting is one line, not a tour.
 Skip this entirely once the placeholder is filled in — every later
-session starts with `TODO.md`, not a greeting.
+session starts with `hedgehog status`, not a greeting.
 
 ## How to work here
 
 The build is a loop of small, gated, committed steps. You never hold the
 whole plan in context — the plan lives in the structure:
 
-- **`TODO.md`** is the live checklist and the source of truth for what's
-  next. Read it at the start of every session. Its only state is
-  checked/unchecked (or skipped-and-confirmed, wherever this core's own
-  optional steps allow it).
+- **The build graph** (`.hedgehog/hedgehog.db`) is the live source of
+  truth for what's next. Query it via `hedgehog status`/`hedgehog next`
+  at the start of every session — never re-derive state from prose.
 - **The commit log** is the record of what's built and why. Conventional
   commits are how progress is read, not a conversation summary.
 - **The architecture is fixed and opinionated for this project's core**
@@ -63,32 +62,41 @@ context** below).
 
 {{CORE_SECTION}}
 
-## Consuming TODO.md
-
-`TODO.md` at repo root is a thin checklist mirroring this core's phase/
-step structure. To work from it:
-
-1. Read it. Find the first unchecked step whose gate (the step before it)
-   is satisfied.
-2. Build that one step via this core's loop skill (named in the section
-   above).
-3. Check the line off after the commit lands. Checked/unchecked is the
-   only state — no notes, no rationale (that's the commit log's job).
-
-`planner` owns writing and extending `TODO.md`; the loop only checks
-boxes off. Keep it thin.
-
-**When the build is done:** once every item in scope is checked, the
-build session is complete. Before deleting `TODO.md`, offer the user a
-fresh-context handoff to the `tweaker` agent — it starts clean, reviews
-`.hedgehog/friction.md` once for a possible discipline-improvement
-suggestion (filed as a GitHub issue against the Hedgehog repo itself,
-never this project's repo, and only after showing the exact content and
-getting explicit approval), then takes any tweak requests one at a time.
-Once that handoff is offered (taken or declined), **delete `TODO.md`** —
-a finished checklist is noise, and the commit log is the durable record
-of what was built. Any archival planning-intake output this core
-produces stays — it's historical record, not a checklist.
+## Consuming the graph
+
+`.hedgehog/hedgehog.db`, committed to git, is the source of truth for
+what's next — never re-derive build state from prose. To work from it:
+
+1. Run `hedgehog next`. It emits the task packet for one ready task
+   (STATUS/WHY NOW/BLOCKED DOWNSTREAM/ALLOWED SCOPE/VERIFICATION) —
+   trust it: a task is never emitted unless every dependency is
+   `complete`.
+2. Delegate the full packet to this core's loop skill (named in the
+   section above), which hands it to the owning agent.
+3. Once the agent reports the work done, run `hedgehog verify
+   <task-id>`. It checks the touched files against the packet's ALLOWED
+   SCOPE, runs the verification command, and on a pass writes the commit
+   and unlocks whatever the task was blocking. An agent reporting success
+   never moves the task — only a passing `hedgehog verify` exit code
+   does.
+
+`planner` owns writing intents (`hedgehog intent add`) at planning
+intake; `hedgehog plan` compiles them into the task graph the loop
+consumes. Nothing checks a box — there is no checklist, only queryable
+state.
+
+**When the build is done:** once `hedgehog status` shows every task
+`complete`, the build session is complete. Offer the user a
+fresh-context handoff to the `tweaker` agent — it starts clean, once
+reviews the friction log (`hedgehog friction list`) for possible
+discipline-improvement issues and separately asks the user directly for
+feedback on the build, filing each real pattern or piece of feedback as
+its own GitHub issue against the Hedgehog repo itself, never this
+project's repo (friction as `bug`/`help wanted`, feedback as
+`suggestion`, each only after showing the exact content and getting
+explicit approval), then takes any tweak requests one at a time. Nothing
+to delete once that handoff is offered — the build graph and the commit
+log are the permanent record, not a checklist to clean up.
 
 ## Managing context
 
@@ -97,12 +105,12 @@ context small:
 
 - **Clear context at natural boundaries** — a module's Phase A, a
   landing page section, whatever this core's own unit boundary is — once
-  that unit is done and committed. `/clear` and start fresh, then
-  re-read `TODO.md` and continue. Nothing is lost, because the
-  checklist, commits, and code hold all the state. Prefer this over
-  letting one session accumulate the entire project.
-- **A cleared or new session recovers by reading `TODO.md` and the
-  commit log**, never by needing the prior conversation.
+  that unit is done and committed. `/clear` and start fresh, then run
+  `hedgehog status`/`hedgehog next` and continue. Nothing is lost,
+  because the build graph, commits, and code hold all the state. Prefer
+  this over letting one session accumulate the entire project.
+- **A cleared or new session recovers by running `hedgehog status` and
+  reading the commit log**, never by needing the prior conversation.
 - **Delegate heavy work to agents.** Planning intake, scaffolding, and
   every build step each run in their own isolated context — so that work
   doesn't pile up in the main thread.

package/src/templates/TODO.core.full-stack-app.md

@@ -1,51 +0,0 @@
-## Add-ons
-
-<!-- Written by planner at planning intake. Each line: on/off + the
-one-line reason. An absent block reads as "never decided," not "off". -->
-
-- Auth: (fill in: on/off — reason)
-- Queue: (fill in: on/off — reason)
-- Mobile: (fill in: on/off — reason)
- 
-## Bootstrap
-
-<!-- Add-on steps (planner marks each on/skipped at planning intake, per
-the ## Add-ons block above) run live, one at a time, after core. A
-skipped add-on gets checked off as skipped, not left unchecked. -->
-
-- [x] Nx workspace + `packages/config` (incl. `docker-compose.yml` for local Postgres) — core, landed via `hedgehog init`, verified via `hedgehog-bootstrap-full-stack-app-core`
-- [x] `packages/db` — Drizzle client — core, landed via `hedgehog init`, verified via `hedgehog-bootstrap-full-stack-app-core`
-- [x] `apps/api` — Nest shell, Pino — core, landed via `hedgehog init`, verified via `hedgehog-bootstrap-full-stack-app-core`
-- [x] `apps/web` — Next shell, TanStack Query provider — core, landed via `hedgehog init`, verified via `hedgehog-bootstrap-full-stack-app-core`
-- [ ] `packages/auth` — Better Auth config + global guard on `apps/api` — Auth add-on (fill in: on / skipped, not in scope)
-- [ ] `apps/worker` — BullMQ seam, Redis (no consumers yet) — Queue add-on (fill in: on / skipped, not in scope)
-- [ ] `apps/mobile` — Expo shell — Mobile add-on (fill in: on / skipped, not in scope)
-## Phase A — Backend
- 
-<!-- One subsection per module in scope. Do not add hooks/screens here —
-that's Phase B, and doesn't start until every module below is checked. -->
- 
-### <module-name>
- 
-- [ ] schema
-- [ ] contract
-- [ ] repository
-- [ ] service
-- [ ] api (controller)
-- [ ] queue (only if this operation genuinely needs async)
-## Phase B — Frontend
- 
-<!-- Do not touch this section until every module above has "api" checked. -->
- 
-### <module-name>
- 
-- [ ] hooks
-- [ ] ux-planner — writes docs/design/<module-name>.md; ask for a
-      mockup/screenshot/Stitch or Figma export here if one exists
-- [ ] screen-web
-- [ ] screen-mobile (only if building for mobile)
-
-<!-- STOP before deleting this file: every box above checked means the
-build is complete. Offer the user a fresh-context handoff to `tweaker`
-first — see hedgehog-loop's Stop Condition. Only delete this file after
-that offer has been made (taken or declined). -->

package/src/templates/TODO.core.landing-page.md

@@ -1,31 +0,0 @@
-## Brief
-
-<!-- Written by planner at planning intake: the subject statement,
-audience, and the page's single job — full detail in
-.hedgehog/chain/00-brief.md. -->
-
-- Subject: (fill in)
-- Audience: (fill in)
-- Page job: (fill in)
-
-## Bootstrap
-
-- [x] Astro workspace + Tailwind token layer — core, landed via `hedgehog init`, verified via `hedgehog-bootstrap-landing-page-core`
-
-## Chain
-
-<!-- The Chain Method, one phase at a time, in strict order except where
-noted. Do not start a phase until the one above it is checked. -->
-
-- [ ] strategy — subject/audience/job + adjective pairs + visceral/behavioral/reflective sort + note timing — `landing-strategist`
-- [ ] systems — dial table + voice spec (parallel) → token system → signature element — `landing-systems`
-- [ ] sequence — per-section transitions, weight, spacing, beat structure — `landing-sequencer`
-- [ ] headline — headline + 2 backups, from distinct mechanisms, reviewed and locked by the user — `landing-headline-writer`
-- [ ] copy — one section at a time, per the paragraph algorithm, each section reviewed and locked by the user before the next starts — `landing-copywriter`
-- [ ] audit — traceability/distinctiveness + usability, reconciled to a pass — `landing-critic`
-- [ ] build — the artifact, in Astro — `landing-builder`
-
-<!-- STOP before deleting this file: every box above checked means the
-build is complete. Offer the user a fresh-context handoff to `tweaker`
-first — see hedgehog-landing-loop's Stop Condition. Only delete this
-file after that offer has been made (taken or declined). -->

package/src/templates/TODO.md

@@ -1,12 +0,0 @@
-# TODO
- 
-<!-- 2-3 sentences: what is this project. Full detail lives in this
-core's own archival planning-intake output — see CLAUDE.md's core
-section for where. -->
- 
-## Context
- 
-(fill in per project — see this core's archival planning output for the
-full picture)
-
-{{CORE_SECTION}}