name: new description: Create a new change folder with metadata argument-hint: "<slug> [--domain <domain>] [--no-spec]" disable-model-invocation: false model: haiku

New Change

Create a change folder scaffold with metadata. This is the entry point for the change lifecycle.

Setup

Parse $ARGUMENTS:

• slug (required) — kebab-case change identifier
• --domain <domain> — target domain for behavioral changes
• --no-spec — non-behavioral change (sets behavioral to false, skips specs and design)

Process

1. Validate the slug is kebab-case and doesn't already exist
2. Create the change folder:

   .venv/bin/python -m agents.lib.spec_state create {slug} [--domain {domain}] [--no-spec]
   

3. Show artifact status:

   .venv/bin/python -m agents.lib.spec_state status {slug}
   

4. Print which artifacts are ready (proposal should be "ready", rest "blocked")

Next Steps

Suggest:

• /propose {slug} — create all planning artifacts in one pass
• /continue {slug} — create the next ready artifact (proposal first)

Classification Hint

Slugs containing governance terms (tooling, skill, hook, pre-commit, spec-state, commit, review, auth, security, platform) almost always describe behavioral changes — even when nothing under packages/ is touched. Modifying a skill's behavior, a hook, or any governance-domain spec (tooling, code-quality, testing, platform, security) requires behavioral: true and a delta spec under specs/{domain}/. Defaulting to --no-spec for these slugs is usually wrong; /archive will reject them once a delta is drafted (REQ-TL-018).