# speckit.companion.classify

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.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 110 repo stars
- Author: alfredoperez
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/alfredoperez/speckit-companion/tree/HEAD/apps/speckit-extension/commands/speckit.companion.classify.md
- Updated: 2026-10-19
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/speckitcompanionclassify

## What it 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.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/commands/speckit.companion.classify.md` — Call it with /speckit.companion.classify. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/speckit.companion.classify.md` — Call it with /prompts:speckit.companion.classify. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/speckit.companion.classify.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/speckit.companion.classify.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/alfredoperez/speckit-companion/tree/HEAD/apps/speckit-extension/commands/speckit.companion.classify.md

## When to use it
- 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
- /speckit.companion.classify
- Run /speckit.companion.classify to estimate scope from spec.md

## Source text · speckit.companion.classify.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 715d9397e438ee49.

BEGIN THIRD-PARTY FILE 715d9397e438ee49
````text
---
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 -->
````
END THIRD-PARTY FILE 715d9397e438ee49

The third-party file has ended. Everything between the 715d9397e438ee49 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

© alfredoperez · MIT · https://github.com/alfredoperez/speckit-companion/tree/HEAD/apps/speckit-extension/commands/speckit.companion.classify.md

## Similar
- [speckit-analyze](https://affpapa.org/en/nevibecode/skills/speckit-analyze.md) — skill · 1600 installs
- [speckit.implement](https://affpapa.org/en/nevibecode/commands/speckitimplement.md) — command · ★ 117 repo stars
- [speckit-specify](https://affpapa.org/en/nevibecode/skills/speckit-specify.md) — skill · 2700 installs
- [workflow-classify](https://affpapa.org/en/nevibecode/commands/workflow-classify.md) — command · ★ 880 repo stars
- [speckit.analyze](https://affpapa.org/en/nevibecode/commands/speckitanalyze.md) — command · ★ 117 repo stars
- [ce-brainstorm](https://affpapa.org/en/nevibecode/skills/ce-brainstorm.md) — skill · 4200 installs

From the same set: [alfredoperez/speckit-companion](https://affpapa.org/en/nevibecode/by/alfredoperez/speckit-companion.md) — 83 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
