@skyf0xx/hedgehog 0.1.15 → 0.1.17

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@skyf0xx/hedgehog",
-  "version": "0.1.15",
+  "version": "0.1.17",
   "description": "Install the Hedgehog build discipline (agents + skills) into a repo.",
   "type": "module",
   "repository": {

package/src/agents/planner.md

@@ -118,11 +118,16 @@ did in your own interview before BMAD existed.
    an add-on that's off) is its only state.
 8. **File `docs/design/<module>-notes.md` per module**, sourced from the
    UX spec.
-9. **On first run only, hand off to the `bootstrap` agent** once Confirm
-   & Lock holds — it scaffolds the core workspace and whichever add-ons
-   are on, before any module's Phase A starts. Skip this on a later run
-   (new scope entering play); the workspace already exists.
-10. **Return a summary**: scope boundary, Add-ons decision, module list,
+9. **Commit planning intake's output as one commit**,
+   `chore(planning): intake` — `TODO.md`, `.hedgehog/BMAD/`,
+   `docs/design/`, and root `CLAUDE.md`'s filled placeholders. This is
+   planning intake's own unit of work, landed before `bootstrap` touches
+   anything.
+10. **On first run only, hand off to the `bootstrap` agent** once the
+    commit lands — it scaffolds the core workspace and whichever add-ons
+    are on, before any module's Phase A starts. Skip this on a later run
+    (new scope entering play); the workspace already exists.
+11. **Return a summary**: scope boundary, Add-ons decision, module list,
     any open questions.
 
 ## Constraints

package/src/agents/ux-planner.md

@@ -32,7 +32,11 @@ mid-implementation.
 Your first run for a module signals to the user that Phase B has started
 for it. Check for `docs/design/<module>-notes.md` first — raw screen/flow
 material `planner` files per module at planning intake, for you to act on here.
-Read it if present, then say so plainly and ask for anything further
+If it's thin, or a specific detail you need (information architecture, a
+named flow, visual identity) isn't in it, read the full source directly:
+`.hedgehog/BMAD/05-ux-spec/DESIGN.md` and `EXPERIENCE.md`, the un-mined
+UX spec `planner`'s notes were drawn from. Read the notes file if present,
+then say so plainly and ask for anything further
 before producing the rationale: "Phase A is closed for `<module>` — this
 is the UX planning step before the screen gets built. [If notes exist:
 "I've got what was noted at planning intake for this module — here's a quick
@@ -64,8 +68,9 @@ mockup, not a design system, not code:
    too small to hit reliably, a state change with no visible feedback).
 5. **Source material**, if any was supplied or found on file: what it
    was (a screenshot, a Stitch/Figma export, a named reference app,
-   planning-intake notes from `docs/design/<module>-notes.md`) and what was drawn
-   from it versus decided independently.
+   planning-intake notes from `docs/design/<module>-notes.md`, or the
+   raw UX spec at `.hedgehog/BMAD/05-ux-spec/`) and what was drawn from
+   it versus decided independently.
 
 Keep it short — a few bullets per screen, not a document. This is a
 rationale `ui-builder` reads once before starting, and `reviewer` can
@@ -104,7 +109,10 @@ conclusion.
 
 1. Confirm the module's hook step is committed (`feat(<module>): hooks`)
    — if not, stop, this is being asked for too early.
-2. Check for `docs/design/<module>-notes.md` and read it if present.
+2. Check for `docs/design/<module>-notes.md` and read it if present. If
+   it's thin or missing a detail you need, read
+   `.hedgehog/BMAD/05-ux-spec/DESIGN.md` and `EXPERIENCE.md` directly for
+   the full material it was drawn from.
 3. Announce the Phase B transition and ask for visual input, per "When
    you run," above.
 4. Read the contract (`packages/contracts`) for the module: what
@@ -126,7 +134,8 @@ conclusion.
 
 - Write only `docs/design/<module>.md` — never application code. Same
   read-only-against-the-codebase posture as `planner`, scoped to this one
-  file type.
+  file type. Read-only against `.hedgehog/BMAD/` too — archival record,
+  never edited.
 - Never design visual style, color, typography, or branding — that's
   `ui-builder`'s call against the project's ShadCN/Tailwind setup, or a
   design tool's output if one is wired into the project.

package/src/skills/hedgehog-bootstrap/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: hedgehog-bootstrap
-description: Use once, at the start of a new Hedgehog project, to land the core workspace and scaffold whichever add-ons (Auth, Queue, Mobile) planning intake turned on (TODO.md's Add-ons block). Triggers on "bootstrap this project", "set up the hedgehog stack", "scaffold the workspace". Not for per-module work — that's the `hedgehog-loop` skill, one step at a time.
+description: Use once, at the start of a new Hedgehog project, to land the core workspace and scaffold whichever add-ons (Auth, Queue, Mobile) planning intake turned on (TODO.md's Add-ons block). Runs when the `bootstrap` agent runs, which `planner` invokes automatically after Confirm & Lock. Scoped to project scaffolding; per-module work runs through the `hedgehog-loop` skill, one step at a time.
 ---
 
 # Hedgehog Bootstrap

package/src/skills/hedgehog-bootstrap-core/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: hedgehog-bootstrap-core
-description: Use once, at the start of a new Hedgehog project, before hedgehog-bootstrap's add-on steps, to land the golden-core workspace (Nx, packages/config, packages/db, apps/api, apps/web, and every enforcement file) and verify it's green. Triggers as the first move of "bootstrap this project" — not invoked directly by name. No per-project decisions, no add-on awareness.
+description: Use once, at the start of a new Hedgehog project, before hedgehog-bootstrap's add-on steps, to land the golden-core workspace (Nx, packages/config, packages/db, apps/api, apps/web, and every enforcement file) and verify it's green. Runs as the first move of the `bootstrap` agent, which `planner` invokes automatically after Confirm & Lock. No per-project decisions, no add-on awareness.
 ---
 
 # Hedgehog Bootstrap — Core

package/src/skills/hedgehog-planning-intake/SKILL.md

@@ -160,12 +160,13 @@ stops being true, so it's a hard stop, not a recap in passing.
 Then state plainly what happens on confirmation, before it happens:
 
 > This locks in `TODO.md` (with the `## Add-ons` block) and
-> `docs/design/<module>-notes.md` per module, and hands off to the
-> `bootstrap` agent to scaffold the workspace and whichever add-ons are
-> on. Phase A build (schema first) starts on the first module once that
-> closes. Anything wrong or missing — say so now; it's a normal edit
-> before this point, and a Correction Protocol entry after. Confirm to
-> proceed, or tell me what to change.
+> `docs/design/<module>-notes.md` per module, commits them in one pass
+> (`chore(planning): intake`), and hands off to the `bootstrap` agent to
+> scaffold the workspace and whichever add-ons are on. Phase A build
+> (schema first) starts on the first module once that closes. Anything
+> wrong or missing — say so now; it's a normal edit before this point,
+> and a Correction Protocol entry after. Confirm to proceed, or tell me
+> what to change.
 
 Wait for an explicit go-ahead. A revision here is just another mining
 pass — update the draft, re-run this stage, don't write anything until