Skip to content
AssureSwarm Docs

Agent Operating Guide

/coach-substeps-split

Split a long workflow step packed with many procedures into sub-steps on the same workflow, each with its own pass/fail status and evidence slot: submitted as suggestions to approve.

Break a long workflow step, one with a dozen procedures crammed under a single pass/fail conclusion, into sub-steps on the same workflow, each carrying its own pass/fail status and evidence slot. The skill reads the parent step, parses its instructions into distinct procedures, and submits the change as suggestions for a human to approve: an update to the parent plus one create per sub-step. Reviewers get field-level review targets instead of one giant reviewed boolean, and testers get visible partial progress.

When to use

Section titled “When to use”

When a workflow step has grown into a checklist of separate procedures under one conclusion and you want each procedure signed off on its own. The skill only splits steps with three or more distinct procedures: a genuinely single-procedure step is left whole. To author a fresh multi-step workflow instead of splitting one step, use /coach-workflow-build.

Inputs

Section titled “Inputs”
Flag Required Notes
--step <step-id> Yes The parent step to split.
--dry-run No Preview the proposed split without submitting any suggestions.

Example

Section titled “Example”

/coach-substeps-split --step step_abc reads the step’s instructions, finds six numbered procedures, and proposes six sub-steps, each inheriting the parent’s linked risk, control, and issue, each with a blank result and evidence slot, submitting an update to the parent plus one create per sub-step for you to approve. If the step has fewer than three procedures, it halts with “This Step is already atomic; nothing to split.”

Good to know

Section titled “Good to know”
  • The split threshold is three. Steps with fewer than three distinct procedures are treated as atomic and left alone, so the skill won’t fragment work that’s already the right size.
  • The parent step keeps its overview and scope; its status becomes the aggregate of its sub-steps: it passes when all of them pass.
  • Sub-steps inherit the parent’s linked risk, control, and issue, so traceability carries down without re-linking.
  • Attached documents stay on the parent step. After approval you re-attach each to the right sub-step by hand: the split is structural, not evidence-moving.
Section titled “Related”