Module hosting 

speccoder spec: list the installed Agent Skills, or run one.

A hosted planning skill works in your checkout, because what it writes — the feature’s spec, plan and tasks — belongs there; the planning policy lets it write only the format’s artifacts and run the format’s scripts, and the changes are left uncommitted for you to review.

Functions

commit_planning

Commits exactly paths (repository-root relative, inside the current unit’s directory) as the unit’s planning: spec(<unit>): <files>. Nothing else that is staged or changed goes into the commit.

commit_planning_as

commit_planning with the commit’s subject (default: the files).

list

speccoder spec: the installed skills.

run

speccoder spec <name> with the configured model, for feature.

run_hooks

Runs the mandatory hooks of event as hosted skills and lists the optional ones. Ok(lines) to show; Err when a mandatory hook did not complete — the caller stops with it.

run_hooks_in

run_hooks for feature, which the hook skills work on.

run_in

run_with for feature (--feature; else the format’s own selection): the skill’s commands are told which unit is meant, and a unit the creating skill makes becomes current.

run_with

speccoder spec <name> [arguments] against state with provider.

uncommitted

The current unit’s planning files that are not committed — new or changed files under the unit’s directory. speccoder run reads committed files only, so these are what stands between planning and a run.