hedgehog-core-designlisted

# Hedgehog Core Design Designs a core definition for a project no shipped core fits. Hedgehog decides the architecture here — the stack, the layers, their order, their file scope, their verification — and shows it back for confirmation. The user is asked about their product, never asked to pick a stack or design layers; a person who could name the right stack and layer sequence unprompted wouldn't need a build discipline to enforce it. The output is one file, `.hedgehog/core.yaml`, in the exact format shipped cores use (spec: "Core definitions"). Everything else this skill produces is rationale, and rationale goes to `.hedgehog/core-design.md`, not into `core.yaml` — the loader (`src/db/core.mjs`) parses a narrow YAML subset and throws on anything outside it. ## When this runs After `hedgehog-planning-intake`'s Phase 0, not before. An architecture can't be designed from a one-line project description: the drivers that decide it — persistence, concurrency, deployment target, integration surface — are exactly what BMAD's brief and PRD elicit. So `planner`'s Phase 0 reaches its third outcome ("neither shipped core fits, but something is being built"), runs the BMAD shelf in full, then opens this skill against that archive. Intent mining follows this skill, not the other way round — the layer sequence has to exist before `hedgehog plan` can compile anything against it. ## Step 1 — name the system shape Say what the project fundamentally is, in one line, before deriving anyt