Cycle tools
Incident intake, bug handling, delegation and the steps of the delivery cycle. This group has 14 tools, 13 of them available only with spec-editor Pro.
| Tool | Edition | Summary |
|---|---|---|
accept_result |
Pro | Accept or reject a delegated result (from a DelegationService.delegate call) by its child_run_id; checks output_schema/acceptance and records the outcome in… |
check_analysis_doc |
Pro | Check an analysis document BEFORE you answer with it: runs exactly the deterministic checks the host runs on your answer (schema, candidate ids, parents,… |
cleanup_deprecated_sources |
Open core | Select deprecated, or confirmed and released, sources of any kind whose linked elements are all confirmed or deprecated. |
cleanup_fixed_bugs |
Pro | Delete bug source elements with status=‘deprecated’ (analyst-approved for deletion). |
escalate |
Pro | Escalate a conflict. |
fix_bugs_parallel |
Pro | Push all active bug source elements to the coding agent Redis queue for parallel processing by multiple workers. |
ingest_incidents |
Pro | Pull events from every enabled ‘log’ channel (or one named channel), analyse them into BugReports, and ingest each as a new-or-updated bug source incident… |
notify_analysts_confirmed |
Pro | Push confirmed bug source elements to analyst-manager for spec review. |
report_complete |
Pro | Declare requirements completeness. |
select_assignee |
Pro | Score registry candidates for a subtask (skills match, cost, delegation history); returns the top-3 with reasons. |
set_log_config |
Pro | Update runtime logging configuration. |
source_cost_get |
Pro | Every source’s cost and failure account: money spent, number of failed attempts and number of waiting tasks per source, ordered by spend. |
sync_external_channels |
Pro | Pull every enabled channel from local.yaml (publish each item to the event bridge; mirror chat/tracker items into sources_raw/) and/or push buffered lifecycle… |
trace_incident |
Pro | Reverse traceability: trace a bug source incident back to the requirement(s) it violates, and record the result as a ‘violates’ relationship (or tag… |
accept_result
Pro tool. Available with the spec-editor Pro plugin.
Accept or reject a delegated result (from a DelegationService.delegate call) by its child_run_id; checks output_schema/acceptance and records the outcome in memory.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
child_run_id |
string | yes | child_run_id from the delegation result |
note |
string | no | One-line justification |
ok |
boolean | no | Manager’s own judgment (advisory — the acceptance check is deterministic) |
check_analysis_doc
Pro tool. Available with the spec-editor Pro plugin.
Check an analysis document BEFORE you answer with it: runs exactly the deterministic checks the host runs on your answer (schema, candidate ids, parents, sizes, judge criteria, verbatim quotations/paths/identifiers, source coverage, module binding and the estimate of every requirement change) against the context of the running analysis of source_id, and returns every violation plus doc_ref, the ref the checked document is stored under. First call: the complete document in analysis_doc. To fix violations call again with base_ref + patch (only the changed fields), not the whole document. Once violations is empty, answer with exactly {“checked_doc_ref”: “<doc_ref>”}. Read-only for the model.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
analysis_doc |
object | no | The complete AnalysisDoc JSON object you are about to answer with (a JSON string is accepted too). Required unless base_ref is given |
base_ref |
string | no | Instead of analysis_doc: the doc_ref an earlier call returned for this source; patch is applied to that document and the result is checked |
patch |
array of object | no | With base_ref: JSON Patch operations (RFC 6902, only add/replace/remove) changing only the fields the violations name, e.g. [{“op”: “replace”, “path”: “/acceptance/1/command”, “value”: “…”}, {“op”: “remove”, “path”: “/requirement_changes/0/relationships/2”}]; ‘-’ as the last path token appends to a list |
project_path |
string | no | Path to the spec-editor project (optional) |
read_ids |
array of string | no | Every element id you opened this run with read_element or find_related – such ids count as candidates, as they do for the host |
source_id |
string | yes | Id of the source being analysed |
cleanup_deprecated_sources
Select deprecated, or confirmed and released, sources of any kind whose linked elements are all confirmed or deprecated. Dry-run by default; approved=true (owner approval, once per batch) deletes them.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
approved |
boolean | no | Owner approval: delete the selected batch |
cleanup_fixed_bugs
Pro tool. Available with the spec-editor Pro plugin.
Delete bug source elements with status=‘deprecated’ (analyst-approved for deletion). Only deprecated bugs are safe to delete — their implementation knowledge has been recorded in the spec.
Parameters
This tool takes no parameters.
escalate
Pro tool. Available with the spec-editor Pro plugin.
Escalate a conflict.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
reason |
string | yes |
fix_bugs_parallel
Pro tool. Available with the spec-editor Pro plugin.
Push all active bug source elements to the coding agent Redis queue for parallel processing by multiple workers.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
max_parallel |
integer | no | Max concurrent tasks |
model |
string | no | LLM model for coding |
ingest_incidents
Pro tool. Available with the spec-editor Pro plugin.
Pull events from every enabled ‘log’ channel (or one named channel), analyse them into BugReports, and ingest each as a new-or-updated bug source incident (env + dedup signature attributes, occurrence count, first/last-seen window). When trace=true (default), newly opened bugs are immediately traced back to the requirement(s) they violate via IncidentTracer.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
channel_name |
string | no | Optional channel type, instance name, or ‘type:name’ to restrict to a single log channel. Omit to pull from every enabled log channel. |
dry_run |
boolean | no | Pull and analyse but write nothing — no bug source elements created/updated, no relationships traced, and file_log channel state files are not advanced. Default false. |
project_path |
string | no | Path to the spec-editor project |
trace |
boolean | no | Trace newly opened bugs via IncidentTracer.trace(apply=True). Default true. |
notify_analysts_confirmed
Pro tool. Available with the spec-editor Pro plugin.
Push confirmed bug source elements to analyst-manager for spec review. Analysts verify the fix is reflected in requirements, then deprecate the bug.
Parameters
This tool takes no parameters.
report_complete
Pro tool. Available with the spec-editor Pro plugin.
Declare requirements completeness.
Parameters
This tool takes no parameters.
select_assignee
Pro tool. Available with the spec-editor Pro plugin.
Score registry candidates for a subtask (skills match, cost, delegation history); returns the top-3 with reasons.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
goal |
string | yes | Subtask goal |
skills |
array of string | no | Skills the subtask needs (optional) |
tags |
array of string | no | Tags (optional, informational) |
set_log_config
Pro tool. Available with the spec-editor Pro plugin.
Update runtime logging configuration. Control which modules/elements are logged during a debug cycle. Changes take effect within 5 seconds.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
elements |
array of string | no | Only log for these element IDs (empty list = log all, null = no change) |
level |
string | no | Minimum severity: debug, info, warning, error (empty = no change) |
modules |
array of string | no | Only log these module element ids (empty list = log all, null = no change). |
silenced |
array of string | no | Never log these module element ids (empty list = none silenced, null = no change). |
source_cost_get
Pro tool. Available with the spec-editor Pro plugin.
Every source’s cost and failure account: money spent, number of failed attempts and number of waiting tasks per source, ordered by spend. Read-only, built from the same stored task records and plans as the delivery board.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
project_path |
string | yes | Path to spec-editor project (directory with methodology.yaml) |
sync_external_channels
Pro tool. Available with the spec-editor Pro plugin.
Pull every enabled channel from local.yaml (publish each item to the event bridge; mirror chat/tracker items into sources_raw/) and/or push buffered lifecycle events (bug opened, IMP formulated, verification failed, promotion recorded,…) to the channels that accept them. Same tool the sync_channels_in / sync_channels_out workflow steps call.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
direction |
string, one of both, in, out |
no | ‘both’ (default): pull + push. ‘in’: pull only. ‘out’: push buffered lifecycle events only. |
project_path |
string | yes | Path to the spec-editor project |
trace_incident
Pro tool. Available with the spec-editor Pro plugin.
Reverse traceability: trace a bug source incident back to the requirement(s) it violates, and record the result as a ‘violates’ relationship (or tag ‘needs_clarification’ when no confident match is found). Without bug_id, traces every open bug source incident.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
apply |
boolean | no | Apply results (write relationships/tags). Default true; false = read-only dry run. |
bug_id |
string | no | Specific bug source id to trace (optional — omit to trace all open bugs) |
project_path |
string | no | Path to the spec-editor project |
semantic |
boolean | no | Also run the semantic-search signal (may build a code embedding index). Default false. |