Gives a coding agent's changes a reviewed plan first, then checks the finished work against that plan and packages evidence a reviewer or CI can inspect. Helps you confirm an AI-made change does what was asked before merging.
@heuremaImplement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through…
@heuremaArchive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after…
@heuremaEnter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the…
@heuremaPropose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to…
@heuremaSync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec,…
@heuremaUpdate an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the…
@heuremaParses a user feature request into a structured contract.json. Scans codebase for scope signals and risk assessment. Read-only --…
@heuremaImplements code changes according to a contract.json specification. The ONLY agent in Signum that writes code. Includes a repair…
@heuremaSynthesizes project.intent.md and project.glossary.json from deterministic scan signals. Uses ranked source hierarchy and…
@heuremaSemantic code reviewer using Claude Opus. Part of the multi-model audit panel. Analyzes diff against contract for bugs, security…
@heuremaCombines multi-model review results into a consensus verdict. Reads review outputs from Claude, Codex, and Gemini, plus mechanic…
@heuremaPath to the target project (auto-detected if omitted)
@heuremaIf the user's task is using Signum init command syntax instead of a feature request - for example: - exactly `init` - `init…
@heurema**Goal:** Bundle all artifacts into a self-contained, verifiable proof package (schema v4.8) with embedded artifact contents.
@heurema**Goal:** Resolve post-implementation obligations and update project state. Runs only when `cleanupObligations` is present and…
@heurema- If any phase fails catastrophically (agent error, required file missing after agent run), **STOP** immediately and report: what…
@heuremaIf the user's task is exactly `explain` (case-insensitive), do NOT run the pipeline. Instead, output this JSON and stop:
@heuremaIf the user's task starts with `archive` (case-insensitive), do NOT run the pipeline. Instead, archive a completed contract.
@heuremaIf the user's task starts with `close` (case-insensitive), do NOT run the pipeline. Instead, mark a contract as closed…
@heuremaBefore setup, determine the correct project directory. The pipeline MUST run in the target project's root, not an unrelated…
@heuremaUse the Bash tool to prepare the workspace (in PROJECT_ROOT):
@heuremaIs this you? Claim your profilePut a plugin at the top of Plugins, from $9
