speckit-companion-classify
Classify the change size (simple | normal | oversized) so the Companion workflow can right-size the pipeline
- License 许可
- MIT
- 所属仓库
- mictlanix/mbe-ui
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- speckit-companion-classify
- metadata
- { "author": "github-spec-kit", "source": "companion:commands/speckit.companion.classify.md" }
- description
- Classify the change size (simple | normal | oversized) so the Companion workflow can right-size the pipeline
- compatibility
- Requires spec-kit project structure with .specify/ directory
03 SKILL.md 正文
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:
[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).simpleis the verdict every reader of the recorded size expects;smallnames 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 -->
04 同仓库更多 Skills
speckit-wireframes-draft
Draw low-fi wireframes for every screen and state the spec describes
speckit-wireframes-draft
暂无简介
speckit-taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
speckit-tasks
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
speckit-specify
Create or update the feature specification from a natural language feature description.
speckit-plan
Execute the implementation planning workflow using the plan template to generate design artifacts.