Skip to main content
skillspec sensemake reads a skill.spec.yml file and returns a structured map of the spec’s collections and handles without dumping the entire YAML into the context. It is the recommended first step before running decide, query, or refs because it reveals what routes, rules, commands, phases, and tests the spec contains at whatever detail level the agent or user needs. The default --view index output is compact and safe for repeated use inside a run. It intentionally hides exhaustive handle lists — move to --view summary or --view full only when you need exact identifiers.

Synopsis

Options

Examples

Print a compact spec map before routing a task:
Inspect collection members when you need specific handles:
Emit JSON so the agent can parse collection names and counts programmatically:

skillspec query retrieves one collection, item, or field path from the spec using a handle string. Use handles produced by sensemake to drill progressively into the spec rather than re-reading the full YAML.

Synopsis

Options

Examples

List the routes collection at summary depth:
Inspect the requirements declared for a specific command:
Read the full content of a test’s expected outcome:

skillspec refs shows outgoing references for an item handle — for example, a rule’s preferred route, a route’s checks, a command’s dependencies, or a test’s expected route and rules. Use it to understand the dependency graph of a spec item before running decide or act.

Synopsis

Options

Examples

See what a routing rule refers to:
Inspect a test’s expected route, rules, and elicitations:
Emit JSON for a command’s full reference graph: