Skip to content
Development
Command

/new

Start a new change using the experimental artifact workflow

From plugin
scaffolding
1621 skills13 agents21 commands25 hooks
> /plugin marketplace add komluk/scaffolding
> /plugin install scaffolding@komluk-scaffolding

Command definition

new.md
name: "Specs: New"
description: Start a new change using the experimental artifact workflow
category: Workflow
tags: [workflow, artifacts, experimental]

Start a new change using the experimental artifact-driven approach.

**Input**: The argument after `/specs:new` is a description of what the user wants to build.

UUID Enforcement

**CRITICAL**: The `conversation_id` MUST be a UUID (format: `xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`). NEVER use descriptive names, slugs, or human-readable strings as the conversation_id. If no UUID is available in the prompt context, generate one with `uuidgen` or `node -p 'require("crypto").randomUUID()'`.

**Steps**

1. **If no input provided, ask what they want to build**

Use the **AskUserQuestion tool** (open-ended, no preset options) to ask: > "What change do you want to work on? Describe what you want to build or fix."

**IMPORTANT**: Do NOT proceed without understanding what the user wants to build.

2. **Create the specs directory**

Obtain the conversation_id UUID (from prompt context or generate one). Verify it matches UUID format (8-4-4-4-12 hex characters) before proceeding.

Create the specs directory for this conversation:

   mkdir -p .scaffolding/conversations/{conversation_id}/specs/

Where `{conversation_id}` is the UUID. NEVER substitute a descriptive name here.

3. **Show the artifact structure**

Display the 3-file structure that will be created:

   .scaffolding/conversations/{conversation_id}/specs/
   ├── proposal.md    <- Why we're doing this (to be created)
   ├── design.md      <- How we'll build it (to be created)
   └── tasks.md       <- Implementation checklist (to be created)

4. **STOP and wait for user direction**

**Output**

After completing the steps, summarize:

  • Specs directory location
  • The 3-file artifact structure (proposal.md, design.md, tasks.md)
  • Current status (0/3 artifacts created)
  • Prompt: "Ready to create the first artifact? Run `/specs:continue` or just describe what this change is about and I'll draft the proposal."

**Guardrails**

  • Do NOT create any artifacts yet - just show the structure
  • Do NOT advance beyond showing the artifact template
  • If a specs directory already exists for this conversation, suggest using `/specs:continue` instead
  • The conversation_id MUST be a UUID -- reject or regenerate if it looks like a descriptive name
Read more
@komluk
Ships withscaffolding

Spec-driven multi-agent orchestration for Claude Code — pure markdown, zero backend, runs on the stock runtime. 13 agents, 39 skills, 21 commands, 20 hooks, per-phase model tiers, opt-in lifecycle hooks, optional cross-device semantic memory.

1639 skills13 agents
Get the whole plugin

Stars on GitHub

Momentum

stars in total
16
Star history of komluk/scaffolding on GitHub, a chart by star-history.com

Other commands on scaffolding.

context

context

Command

Analyze and optimize Claude Code's context configuration (analyze, optimize, or reset).

@komluk@komlukInstall Command
create-skill

create-skill

Command

Scaffold a new scaffolding-compatible skill: an interactive flow that creates `skills/<name>/SKILL.md` from the canonical…

@komluk@komlukInstall Command
doctor

doctor

Command

Health-check the scaffolding install and report install problems plus exact fixes (diagnose-only, never mutates).

@komluk@komlukInstall Command
init-rules

init-rules

Command

Scaffold opt-in path-scoped nested CLAUDE.md rule files into the project to lazy-load per-area conventions while keeping routing…

@komluk@komlukInstall Command
init-scaffolding

init-scaffolding

Command

Bootstrap a new project with the scaffolding CLAUDE.md, settings.json, and `.scaffolding/` directory structure.

@komluk@komlukInstall Command

More commands from other plugins.

build
Auto-invoked

build

Command

Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.

@addyosmani@addyosmaniInstall Command