Skip to main content
command CX Codex

speckit.companion.classify — Claude Code command

speckit.companion.classify evaluates task scope from spec.md to classify changes as simple, normal, or oversized. Companion workflows use this signal to adapt the execution pipeline.

MIT ★ 110 updated 2026-10-19

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/speckit.companion.classify.md
Open on GitHub

What speckit.companion.classify does

This command functions as a read-only sizing step. It inspects spec.md, alongside plan.md and tasks.md when present, without writing to .spec-context.json or modifying any spec documents. It prints a single [companion] size=<simple|normal|oversized> log entry and exposes the value as structured output for workflow switch logic.

A task qualifies as simple only when it touches 5 or fewer files, decomposes into at most 10 tasks, and remains trivial to test and revert. If the work involves database migrations, deleted records, or public interfaces, the step refuses the simple classification regardless of file count. Ambiguous changes default to normal, while broad multi-subsystem work triggers an oversized warning without skipping phases.

What it helps with

  • evaluate task scope directly from spec.md
  • route Companion pipelines based on implementation size
  • prevent skipping verification steps during database migrations
  • detect oversized refactorings before starting code generation

Example prompts for the agent

  • /speckit.companion.classify
  • Run /speckit.companion.classify to estimate scope from spec.md

How to install speckit.companion.classify

Manually: put the files in place

.claude/commands/speckit.companion.classify.md

Call it with /speckit.companion.classify. For all projects use ~/.claude/commands/

Questions about speckit.companion.classify

How to install speckit.companion.classify in Claude Code?

Place the command file at .claude/commands/speckit.companion.classify.md.

What does speckit.companion.classify do?

It parses spec.md and task files to report change complexity as simple, normal, or oversized. The command is read-only and leaves workspace files unchanged.

Why would a two-file change avoid the simple status?

Irreversible or hard-to-verify edits, such as database migrations or API contract updates, automatically disqualify a task from being marked simple.

Source text

speckit.companion.classify.md · MIT
---
description: "Classify the change size (simple | normal | oversized) so the Companion workflow can right-size the pipeline"
---

# Classify Change Size

Emit a single complexity signal — `simple`, `normal`, or `oversized` — that the Companion
workflow's routing step reads to right-size the pipeline. On the workflow path there is no
`complexityFastPath` on/off setting: the thresholds live here, in the workflow, not in a
VS Code toggle.

This is a **thin, read-only** step. It does not write `.spec-context.json` and does not create or
edit any spec files; it only reports a size.

## Heuristic (thresholds live here, not in a setting)

Estimate the scope of the change from `spec.md` (and `plan.md`/`tasks.md` if they already exist):

<!-- speckit-companion:part sizing -->
- **small**: the change plausibly touches **≤ 5 files** and decomposes into **≤ 10 tasks**, and is easy to undo and easy to check. A change that is hard to reverse (a migration, deleted stored data, a published contract) or hard to verify is never small, whatever its file count.
- **oversized**: the change clearly exceeds the small bar by a wide margin (broad multi-subsystem
  work, many new files, or a long task list).
- **normal**: anything in between (the default).
<!-- /speckit-companion:part sizing -->
When unsure, prefer `normal` — the routing step's safe default is the full pipeline, so an
ambiguous estimate never skips a phase.

## Output

Print exactly one line so the size is visible in the run log:

```text
[companion] size=<simple|normal|oversized>
```

Expose the same value as structured output `size` (so a `switch` node can read
`steps.classify.output.size`). Routing contract:

<!-- speckit-companion:part routing -->
- `simple` → the workflow folds toward implement (less ceremony). `simple` is the verdict
  every reader of the recorded size expects; `small` names the *bar*, never the verdict.
- `oversized` → the workflow prints a visible warning and still runs the **full** pipeline. It
  never silently skips a phase.
- `normal` (and any unresolved value) → the full pipeline.
<!-- /speckit-companion:part routing -->

© alfredoperez · MIT · alfredoperez/speckit-companion

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

From the same set83

The whole set →
speckit.git.validate speckit.git.validate — a command that checks whether your current Git branch follows project naming conventions for feature branches. Install it if your team uses structured branch prefixes and wants to automate validation. CX Codex +1 ★ 110repo stars cleanup-implementer cleanup-implementer executes a single repository cleanup work packet. It edits assigned files, runs target checks, and never touches git write operations. CX Codex ★ 110repo stars bench-prep bench-prep is a command for Claude Code and Codex that resets three test cells to baseline and assigns them one task size before an agent works through the SpecKit Companion workflow. CX Codex +1 ★ 110repo stars speckit.companion.before-converge speckit.companion.before-converge is a Claude Code command that records the start of converge in .spec-context.json for the Companion GUI. Run it from the repository root before that step. CX Codex +1 ★ 110repo stars speckit-git-validate speckit-git-validate is a Claude Code skill that checks the current Git branch name and searches specs/ for its matching spec folder in spec-kit projects. CX Codex +1 ★ 110repo stars speckit.companion.after-plan speckit.companion.after-plan writes a plan finish marker to .spec-context.json for the Companion GUI to track agent workflow stages. CX Codex +1 ★ 110repo stars speckit.companion.after-converge speckit.companion.after-converge logs converge completion into .spec-context.json for Companion GUI. It tells the companion interface that the step finished. CX Codex +1 ★ 110repo stars speckit.companion.after-specify speckit.companion.after-specify — a command for Claude Code and Codex that writes the current spec-kit step to .spec-context.json for the Companion GUI. Runs from the repository root after the specify stage completes. CX Codex +1 ★ 110repo stars

Project sponsors

Companies that keep this analytics open