Module hooks 

Spec Kit extension hooks around what speccoder runs.

Extensions register hooks in .specify/extensions.yml (hooks.<event>: command, enabled, optional, priority, condition, prompt). Spec Kit’s agents execute them; Spec Kit’s engine only describes them. speccoder replaces the agent for implement and converge (and hosts planning skills), so it owns that step, deterministically: mandatory hooks (optional: false) run as hosted skills under the planning policy; optional ones are listed for the person; hooks with a condition are skipped (evaluating it is Spec Kit’s executor’s job).

Structs

Hook

One hook entry.

Plan

What to do for one event.

Constants

FILE

The hooks file, relative to the project root.

Functions

offer_line

The line a person sees for an optional hook.

plan

The plan for event in the project at root. A missing file is no hooks; an unreadable one is an error (it would silently skip mandatory hooks otherwise).

plan_from

plan from the file’s text.