AI Agent Workflow Collection

Maintainer-only. Use when re-vendoring skills/BMAD/ against a newer BMAD-METHOD commit — "update BMAD", "re-vendor BMAD", "bump the BMAD pin". Not part of the Hedgehog discipline a consuming project copies; this only applies to the Hedgehog repo itself.

Use for every unit of work on an authored core (.hedgehog/core.yaml present) once bootstrap has closed — building one layer per hedgehog next packet, gated by hedgehog verify and committed one layer at a time. Triggers on "next step", "what's next", "build this", or the start of any work session on a bootstrapped authored-core project. Also covers the Correction Protocol and the Stop Condition for this core.

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 (.hedgehog/addons.yaml). 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.

Use once, at the start of a new Hedgehog project on an authored core (hedgehog-core-design wrote .hedgehog/core.yaml), to generate a verified workspace for the stack hedgehog-core-design chose. Runs as the bootstrap agent's only move on this core, and closes Bootstrap.

Use once, at the start of a new Hedgehog project on the full-stack-app core, before hedgehog-bootstrap's add-on steps, to land the full-stack-app 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.

Use once, at the start of a new Hedgehog project on the landing-page core, to land the pre-verified Astro + Tailwind v4 workspace and verify it's green. Runs as the only move of the bootstrap agent on this core — there are no add-on steps, unlike full-stack-app. Invoked automatically by planner after Confirm & Lock.

Use when the user wants to contribute a fix or ROADMAP.md item back to the Hedgehog project itself (skyf0xx/hedgehog) rather than their own project. Triggers on "let's fix that in Hedgehog", "I want to contribute", "let's pick up a roadmap item", or when tweaker offers this at the end of a build and the user says yes. Covers forking/branching, making the change under Hedgehog's own repo rules, committing with Conventional Commits, and opening the PR.

Use on full-stack-app and landing-page alike only when neither shipped Golden Core fits a project that is still building something real — picks the stack and designs the layer sequence for it, and writes .hedgehog/core.yaml. Invoked by the planner agent as Phase 0's third outcome, after the vendored BMAD shelf has run; don't run standalone and don't run when a shipped core fits.

Use for every unit of work on the landing-page core, from planning intake through the final build phase — the Chain Method's brief → feeling → tokens/element → sequence → artifact pipeline, gated by hedgehog verify and committed one phase at a time. Triggers on "next step", "next phase", "what's next", or the start of any work session on a bootstrapped landing-page project. Also covers this core's own planning intake and Correction Protocol.

Use for every unit of work once a Hedgehog project is bootstrapped — building one layer (schema, contract, repository, service, controller, hook, screen) per module, gated by hedgehog verify and committed one layer at a time. Triggers on "next step", "build this module", "what's next", or the start of any work session on a bootstrapped project. Also covers the Correction Protocol for fixing a wrong upstream step.

Use once per project, at the start, on any core — Phase 0 (running the vendored BMAD-METHOD planning shelf) is shared by every core; Phase 1 (mining 04-prd.md into intent records plus the Add-ons decision) is full-stack-app's own procedure, run again on a scoped pass when new domain scope enters play. Invoked by the planner agent after Phase 0 core selection; don't run standalone. landing-page runs this skill's Phase 0, then mines the same archive through hedgehog-landing-loop's own planning-intake section, that core's counterpart to this skill's Phase 1. An authored core runs this skill's Phase 0, then hedgehog-core-design, then this skill's Phase 1 mining against the designed layer sequence.

Maintainer-only. Use when triaging inbound GitHub issues and pull requests on skyf0xx/hedgehog — "triage the issues", "check the PRs", "review inbound", "what's in the queue". Reads each item read-only, judges it for security and for whether it is real, then fixes and closes or comments and closes. Not part of the Hedgehog discipline a consuming project copies; this only applies to the Hedgehog repo itself.

Use whenever landing-copywriter drafts the CTA/close — the final ask, or any mid-page section landing-sequencer assigned the CTA. Trigger when a section carries the token system's CTA styling intent, distinct from every other archetype (which build the case, not make the ask).

Use whenever landing-headline-writer drafts the page headline (Chain Method step 9). Gives the 8 named rhetorical mechanisms, the outcome-subject test, and the selection procedure for generating 3 distinct-mechanism candidates and presenting them for the user's lock. Trigger on "write the headline", "headline candidates", or the start of landing-headline-writer's own workflow.

Use whenever landing-copywriter drafts the section directly beneath the locked headline — the subhead/lede that makes the headline's claim credible. Trigger when the section's role is "hero support" in landing-sequencer's list, distinct from the headline itself (landing-copy-headline) or the problem/agitation section (landing-copy-problem).

Use whenever landing-copywriter drafts a mechanism/how-it-works section — the section that resolves the problem section's tension by explaining how the product changes the situation. Trigger when the section's role in landing-sequencer's list is to earn the headline's claim through explanation, distinct from proof (evidence the claim is true) or pricing (tiers and plans).

Use whenever landing-copywriter drafts an objection-handling section — FAQ, risk-reversal, or direct address of the reader's stated hesitation. Trigger when the section's role in landing-sequencer's list is to remove a specific, nameable doubt before the CTA, distinct from proof (backs up a claim already made) or the CTA section itself (the ask).

Use whenever landing-copywriter drafts a problem/agitation section — the section that names what currently prevents the reader from having the headline's outcome. Trigger when the section's role in landing-sequencer's list is to establish stakes or friction before the mechanism section resolves it.

Use whenever landing-copywriter drafts a proof/evidence section — social proof, numbers, case studies, benchmarks, testimonials. Trigger when the section's role in landing-sequencer's list is to make an already-explained claim believable, distinct from the mechanism section (explains the how) or the objection section (handles doubt directly).

Use whenever landing-systems names the signature element's geometry personality and family (Chain Method step 6), landing-sequencer picks a concrete transition/divider technique for it, or landing-builder implements any section shape, divider, or icon. Trigger on "implement the signature element", "write the divider", "section transition CSS", "src/shapes/", or an icon/illustration sourcing question. Gives the concrete construction techniques — curved and angular alike — and the one pinned icon source, so shapes come from a formula or a sourced icon instead of hand-typed or hand-measured geometry.

Apply whenever writing or updating a project-facing document — root CLAUDE.md, .hedgehog/core-design.md, specs, READMEs, or similar. Ensures the file reads as a clean, current, as-is snapshot rather than a log of edits or decisions. Applies on first generation and on every later revision, including "update," "rewrite," or "clean up" requests.