skillspec decide evaluates the routing rules declared in a skill.spec.yml against a user task string and returns the full decision as JSON. It is the canonical way to determine which route a task should follow, which rules fired, what substitutions are forbidden, what elicitations are required, and what after-success closures were scheduled.
Run decide before act when you want the raw routing decision without the full OODA action checklist, or use it in scripts that need to branch on a selected route. If you want a human-readable explanation of the same decision, use skillspec explain instead.
Strip skill invocation prefixes from the user task before passing it as --input. The decision engine matches against the raw task intent, not the invocation form.
Synopsis
Options
Examples
Evaluate a task without recording a trace:Output
decide always emits JSON. The top-level fields mirror the internal Decision struct:
When
--trace-dir is supplied, the command also prints the path of the written trace run directory before the JSON output.
Related
skillspec explain <path> --input <text>— same decision in human-readable prose; useful for debugging rule logic.skillspec act <path> --input <text>— expands the decision into a full OODA action checklist.skillspec plan <path> --input <text>— lists the execution phases in order without the full action checklist.