classify-size
Use to classify a feature into XS/S/M/L/XL and write docs/features/{slug}/.size plus the pipeline route docs/features/{slug}/.route (quick|standard|full) so later skills know how much of each artifact to produce and how handoffs resolve skips. Triggers on "classify size", "feature size", "is this XS or M for {slug}", "size {slug}", "change route", "/sdd:classify-size {slug}", "класифікуй розмір {slug}", "який розмір фічі", "XS чи M". Asks four AskUserQuestion (PR count / time / new module-API-migration / breaking changes), maps to a size class via the shared size matrix, derives the default route (XS/S→quick, M→standard, L/XL→full), confirms size + route in ONE question, and writes the one-line .size and .route files — the source of truth; the feature_size: frontmatter mirrors in spec.md and sad.md are re-synced to it on every (re)classification.
genkovich · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add genkovich/sdd --skill classify-size技能说明
name: classify-size model: haiku effort: low agents: [] description: > Use to classify a feature into XS/S/M/L/XL and write docs/features/{slug}/.size plus the pipeline route docs/features/{slug}/.route (quick|standard|full) so later skills know how much of each artifact to produce and how handoffs resolve skips. Triggers on "classify size", "feature size", "is this XS or M for {slug}", "size {slug}", "change route", "/sdd:classify-size {slug}", "класифікуй розмір {slug}", "який розмір фічі", "XS чи M". Asks four AskUserQuestion (PR count / time / new module-API-migration / breaking changes), maps to a size class via the shared size matrix, derives the default route (XS/S→quick, M→standard, L/XL→full), confirms size + route in ONE question, and writes the one-line .size and .route files — the source of truth; the feature_size: frontmatter mirrors in spec.md and sad.md are re-synced to it on every (re)classification.
Skill: classify-size
Atomic skill — classifies a feature into XS/S/M/L/XL and fixes the result in
docs/features/<slug>/.size, plus the pipeline route (quick / standard / full) in
docs/features/<slug>/.route. This is the single source of size- and route-aware behaviour for
the rest of the pipeline: later skills read .size to decide MVP vs Full output depth, and
their handoffs read .route to decide how optional-stage skips resolve (auto-skip / offered /
never — the Routes table in ../_shared/size-matrix.md).
This skill is the canonical owner of the size matrix → ../_shared/size-matrix.md. The classification rules, the MVP-vs-Full table, and the one-sentence rule all live there; this skill only runs the dialogue and writes the file.
Called inline by specify. When .size is absent at the start of the backbone, specify step 1 runs this protocol inline (same signals, same file, folded into one bundled question) — this skill stays the standalone utility for classifying up front or re-classifying when scope changes; the protocol is never duplicated elsewhere.
Owner
PM or Tech Lead (driver of the intake phase). An architect may escalate S → M on spotting a new subsystem.
Inputs
<slug>— feature slug.- (Optional) the idea / intake note — for a rough starting hint. The skill works without it.
Protocol
- Check existing.
test -f docs/features/<slug>/.size(and.route). If.sizeexists, read both values and ask «.sizeis currently<X>(route<Y>). Reclassify?». On «no» — STOP (suggest editing, don't overwrite silently). Re-running just to switch the route is a legal, common case — mid-flight override per the Routes table. - Ask the four signals — one
AskUserQuestioneach, phrased per../_shared/ask-style.md:- PR count —
1/2–5/5–15/15+. - Time to merge the main part —
≤1 day/~1 week/1–2 sprints/>1 month. - New module / new API / DB migration —
none/one of three/two of three/all three. - Breaking changes for consumers —
no/internal only/public clients.
- PR count —
- Map to a class using the table in
../_shared/size-matrix.md. On an edge case, name the dominant signal aloud («M because it adds a new API + 1–2 sprints, even though PR count is on the S/M border»). For an all-maximums answer, ask explicitly «needs a separate roadmap?» → yes = XL. - Confirm size + route — ONE question. Derive the default route from the size (XS/S →
quick, M →standard, L/XL →full— the Routes table in../_shared/size-matrix.md). Then oneAskUserQuestion: «Classifying as<size>() → route<route>(). Lock both in?» — options:Yes/Yes, but route <other>/No, I want size <X>/Reclassify. Never a second question just for the route. - Write
.size+.route. Each one line, plain text —.sizeonlyXS/S/M/L/XL;.routeonlyquick/standard/full— no comments, no frontmatter.docs/features/<slug>/.size,docs/features/<slug>/.route. - Re-sync the frontmatter mirrors (
.sizeis the source of truth).feature_size:lives in up to three places: the.sizefile (canonical) plus thespec.mdandsad.mdfrontmatter (human-readable mirrors). For each of the two files that exists: same value → OK; different (a reclassification, or a hand-edited mirror) → update the frontmatter to the new.sizevalue and say so — never leave a mirror stale; missing field → suggest addingfeature_size: <size>. If the user insists a mirror is the right value, that's a reclassification — loop back to step 4 and re-confirm, then re-sync. - Structural self-check — per
../_shared/self-check.md: re-read the written files from disk and verify 3 items: (1).sizeholds exactly one of {XS, S, M, L, XL} (one bare word, no trailing content); (2).routeholds exactly one of {quick, standard, full}; (3) both frontmatter mirrors (feature_size:inspec.mdandsad.md, for whichever exists) match.size. Fix + re-check ≤2 cycles; surface anything unresolved. - Propose commit + handoff.
size: <slug> classified as <size> (route <route>)(or fold into the intake commit if a wrapper called this). Then emit the stage-handoff block per../_shared/handoff.md(utility variant) — What I did (incl. «self-check: 3/3 pass») + Review (.size,.route) + Run next: resume your backbone stage (e.g./sdd:specify <slug>);/clearoptional.
Definition of Done
docs/features/<slug>/.sizeholds exactly one of XS/S/M/L/XL;docs/features/<slug>/.routeholds exactly one of quick/standard/full.- The user confirmed the classification — size AND route in one question (never silent, never two questions).
- If
spec.md/ `