skills.rest
whw23
whw23COMMUNITY
Explore all skills by this author →
GitHub

speckit-companion-classify

Classifies change size as small, normal, or oversized for spec-kit workflow routing.

Updated May 28, 2026
Search Tags:#classification#spec-driven development#spec-kit#workflow routing#complexity estimation#change size
One-click install
npx skills add https://github.com/whw23/PingoGate --skill speckit-companion-classify-whw23
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-companion-classify
Source: https://github.com/whw23/PingoGate/tree/main/.claude/skills/speckit-companion-classify
Command: npx skills add https://github.com/whw23/PingoGate --skill speckit-companion-classify-whw23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Spec-driven development workflows need to right-size their pipeline based on how large a change is, but estimating scope manually is inconsistent. This Skill provides a single, deterministic complexity signal so the Companion workflow can route each change through the appropriate pipeline depth. ## Core Features & Use Cases - Size Classification: Emits exactly one of small, normal, or oversized based on spec.md, plan.md, and tasks.md content. - Fixed Thresholds: Uses a 5-file / 10-task heuristic guardrail, with normal as the safe default when estimates are ambiguous. - Structured Output: Prints [companion] size=<value> and exposes a structured size field that workflow switch nodes can read for routing. - Use Case: In a spec-kit project, run classification before planning so small changes fold toward implement with less ceremony, while oversized changes trigger a visible warning but still run the full pipeline. ## Quick Start Ask the assistant to classify the size of the current change described in spec.md so the Companion workflow can route it.

Frequently Asked Questions about speckit-companion-classify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I classify change size in a spec-kit workflow?▼

Run the classify step, which reads spec.md and any existing plan.md or tasks.md to estimate scope. It emits one line like [companion] size=small and exposes a structured size field that routing nodes consume.

What thresholds determine small versus oversized changes?▼

A change is small when it plausibly touches 5 or fewer files and decomposes into 10 or fewer tasks. Oversized means it clearly exceeds that bar with broad multi-subsystem work, and everything in between defaults to normal.

Does the classify step modify spec files or .spec-context.json?▼

No. The classify step is thin and read-only. It does not write .spec-context.json and does not create or edit any spec files; it only reports a size signal for the routing step.

What happens when a change is classified as oversized?▼

The workflow prints a visible warning but still runs the full pipeline. Oversized classification never silently skips a phase, and unresolved or ambiguous values also fall back to the full pipeline.

What project structure is required for spec-kit classification?▼

The skill requires a spec-kit project structure with a .specify directory containing spec.md, and optionally plan.md and tasks.md for more accurate estimates. Without these files, classification cannot estimate scope.

Related Skills

Explore More Software Engineering Skills→
pradeepmoulipradeepmouli
2

speckit-specify

Generate spec.md files with user stories and acceptance criteria from natural language.

Community
Advanced
travelinman1013travelinman1013

writing-plans

Generate bite-sized implementation plans with file paths, test targets, and commit guidance.

Community
Advanced
AndurilCodeAndurilCode
7

context-debugging

Diagnose agent failures by classifying context issues and applying remediation steps.

Official
Intermediate
saschadudkin-sketchsaschadudkin-sketch

code-review

Automate code review for rezidence4/DomHub repository changes.

Community
Advanced