Slash Command

/spec

Create or edit a spec for a source file or directory

Install

Run in your terminal

npx claudepluginhub lewdwig-v/unslop --plugin unslop

Details

Argument<file-or-directory-path>

Command Content

Other plugins with /spec

/spec

commands/

Starts spec-driven development: asks clarifying questions on objectives, features, tech stack, and boundaries; generates structured SPEC.md covering six core areas; confirms before proceeding.

agent-skills

3.3k

/spec

commands/

Authors structured NLSpec from natural language description using multi-AI research, with adversarial completeness validation, scoring, and saved spec file.

octo

2.3k

/spec

kiro/

Generates complete feature specifications from a feature name or rough idea, spanning requirements to implementation plan.

kiro-skill

1.4k

/spec

Generates spec docs from feature description: requirements.md (EARS notation), design.md (Mermaid diagrams, TS interfaces), tasks.md (implementation plan).

cook-es

889

/spec

Generates detailed feature specs via 3-phase interactive dialogue from minimal input, producing requirements.md (EARS), design.md (diagrams/TS), and tasks.md.

cook

889

/spec

Generates feature specs via step-by-step dialogue: requirements.md (EARS notation), design.md (diagrams/TS interfaces), tasks.md (tasks/best practices).

cook-en

889

Stats

Parent Repo Stars4

Parent Repo Forks0

Last CommitMar 28, 2026

Actions

View Source View Plugin View on GitHub View README

The argument $ARGUMENTS is the path to the source file or directory (e.g., src/retry.py for a file spec, src/widgets/ for a unit spec).

Use the unslop/spec-language skill for guidance on spec writing voice throughout this command.

Check initialization: Check that .unslop/ exists. If not, warn the user that unslop is not initialized and suggest running /unslop:init first. You may still proceed with creating the spec file (spec creation works without init), but note that /unslop:generate will require initialization.

Derive the spec path:

For files: append .spec.md to the filename (e.g., src/retry.py -> src/retry.py.spec.md).
For directories: use <dirname>.unit.spec.md inside the directory (e.g., src/widgets/ -> src/widgets/widgets.unit.spec.md).

If the spec file already exists:

Read it and present its contents to the user for editing. Stop here — no further steps are needed.

If the source file exists but no spec exists yet:

Read the source file.
Draft a spec that captures intent, not implementation — describe what the file does, what constraints it satisfies, and what behavior it exhibits. Do not describe data structures, algorithms, or internal control flow. When creating a spec for a file that imports from other managed files, suggest depends-on frontmatter. Analyze the source file's imports — if any imported module has a corresponding *.spec.md file in the project, include it in the depends-on list. Present the suggested dependencies to the user for confirmation before writing the spec.
Write the draft to the spec path.
Present the draft to the user for review and editing.

If neither the source file nor the spec exists:

Create a skeleton spec using the template from the unslop/spec-language skill.
Write it to the spec path.
Present it to the user for editing.

After the user is satisfied with the spec:

Inform them to run /unslop:generate to produce the managed file from the spec.

Do NOT archive, regenerate, or run tests. Those are handled by /unslop:takeover and /unslop:generate.