apply
Implement tasks from an OpenSpec change (Experimental)
If the user's task is using Signum init command syntax instead of a feature request - for example: - exactly `init` - `init --force` - `init --harness` - `init --project-root <path>`
> /plugin marketplace add heurema/signum > /plugin install signum@signum
How it fires
How this command gets triggered: by you, by Claude, or both.
/10-init-command-redirectContext preview
What this command does when you run it.
If the user's task is using Signum init command syntax instead of a feature request - for example: - exactly `init` - `init --force` - `init --harness` - `init --project-root <path>`
If the user's task is using Signum init command syntax instead of a feature request - for example:
do NOT run the CONTRACT → EXECUTE → AUDIT → PACK pipeline.
Instead, tell the user:
Use `/signum:init [--force] [--harness] [--project-root <path>]`.
For Claude Code plugin usage, `/signum:init` is the canonical form. `--harness` requires Signum `>= v4.18.0`.
Then stop.
Signum is a contract-first proof gate for agentic software changes: it turns a task into a reviewed contract, executes against that contract, audits the result, and packages evidence that humans and CI can inspect.
Repo: heurema/signum
Implement tasks from an OpenSpec change (Experimental)
Archive a completed change in the experimental workflow
Enter explore mode - think through ideas, investigate problems, clarify requirements
Propose a new change - create it and generate all artifacts in one step