dx-new

dx-new — the entry point and router

Every piece of work starts here. Your one job is to pick the container level, create its identity file, and print the next command. You do not research, frame, or plan — you route.

Guard. If context/ isn't scaffolded (no changes/ or efforts/), stop and tell the user to run /dx-init. Never auto-create the parent tree.

Slice of an existing effort — read the id, don't invent one

If invoked as dx-new <effort-id> <slice-n>, this is a child change — a different path from everything below. Read context/efforts/<effort-id>/roadmap.md and find ### Slice <slice-n>: its - change: <slug> line is the id dx-roadmap already assigned, and the slice name is the title. Use them as-is — do not derive a new slug from scratch, that would orphan the roadmap's link. Missing effort or slice → tell the user to run /dx-roadmap <effort-id> first.

Create context/changes/<slug>/change.md with effort: <effort-id>, slice: <slice-n>, status: new. Default type: feature unless effort.md's ## Notes carries the marker line Refactor effort — findings promoted from /dx-refactor-discover. (written once at effort creation — see Promoted entries), then type: refactor. Fill every other frontmatter field the schema defines — invoke dx-references with topic change-md for the exact shape. The child inherits the effort's research/ and frame.md in place (nothing is copied); it does not get its own. Skip straight to /dx-plan <slug> — upstream is already settled.

Name it (change or effort, not a slice)

Derive a kebab-case slug from the idea (Add Google sign-in → oauth-login). If foundation/glossary.md exists, read it first and prefer its terms so the id matches the project's language. Reject a slug that collides with an existing change/effort/archive folder — ask for another.

Pick the level

Infer from size and clarity; when it's a coin-flip, ask one question and stop.

• Small / clear → a change. A single shippable unit. Create context/changes/<id>/change.md. Set type (feature | defect | refactor | migration — default feature), effort: null, slice: null, status: new, plus every other field the schema defines. Invoke dx-references with topic change-md for the exact shape.
• Large / decomposes into slices → an effort. Work that produces changes. Create context/efforts/<id>/effort.md with a one-paragraph ## Goal, status: new, plus every other field the schema defines. Invoke dx-references with topic effort-md for the exact shape.