메뉴
Use when starting spec work and unsure which loom-spec skill applies. Family entry router — routes to spec-expansion (draft/expand a spec from a seed) or completeness-critic (critique an existing draft for omissions).
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | using-loom-spec |
| description | Use when starting spec work and unsure which loom-spec skill applies. Family entry router — routes to spec-expansion (draft/expand a spec from a seed) or completeness-critic (critique an existing draft for omissions). |
| version | 0.1.0 |
Brief before you ask a complex spec fork. Before you ask the user a spec fork this complex — ≥3 trade-offs, ≥2 implementation paths, or architectural blast radius — run dev-workflow:brief-before-asking first instead of improvising the question.
All user-facing narration in this router — briefs, critique summaries,
decision asks — follows loom-pipeline/hooks/family-relay.md §Family relay discipline
(pointer, never copy).
Step 1 — 前站檢查 (upstream check). Check the target repo against the
loom family's on-ramp criteria table (loom-pipeline/hooks/family-reception.md
— the reception SSOT; reference it, don't copy its rows here). Two rows are
most relevant to spec work: if the work touches a user-facing surface and no
DESIGN.md/ui-flows.md exists yet, recommend using-loom-interface-design
first — specifying before the surface is designed re-derives it and drifts.
If no docs/loom/PRINCIPLES.md exists and the work is product-shaped (a new
product/feature idea, not an increment), recommend using-loom-product-principles
first. Recommend once, record the user's choice, then proceed either way
— the negative guard still applies (bug fix / refactor / test-covered
increment → do not interrupt).
Step 2 — 對站檢查 (peer check). If the ask isn't spec work at all — it's
a UI/UX design ask, a product-constitution ask, or an implementation/code
ask — redirect to the matching family entry (using-loom-interface-design,
using-loom-product-principles, using-loom-code) rather than forcing it
through loom-spec.
Step 3 — family routing (disambiguation). Once the ask is confirmed spec work, route between loom-spec's two members by the specific verb — this distinction is load-bearing, not cosmetic:
ui-flows.md, that needs fan-out into objects/states/paths/edge cases →
spec-expansion.completeness-critic.This closes the #456-documented adjacent mis-route: a critique-an-existing-
spec ask getting sent to spec-expansion (which would silently re-draft
instead of auditing) instead of completeness-critic. When in doubt, ask
"does a draft already exist to critique, or am I starting from a seed?" — the
answer picks the member.
spec-expansion — GENERATE-layer writer. Fans a sparse seed out into a
high-recall spec draft (OpenSpec change-folder shape).completeness-critic — GENERATE-layer critic. Adversarially hunts
omissions in an existing spec-expansion draft via a fresh-context lens
panel; never touches code.Both stop at GENERATE — loom-code:writing-plans reads the emitted
#### Scenario: criteria downstream; that is the one-directional spec→code
handoff, not this router's job.
| Harness | Mechanism |
|---|---|
| Claude Code | Use the Skill tool, e.g. Skill(skill: "spec-expansion"). |
| Codex CLI | Use the skill tool (Codex shape). |
If the user types /skill-name, that is an explicit invocation — load it via
the Skill tool. Do not guess names that are not listed above.
spec-expansion.completeness-critic.Append-only bitemporal store for validated operational-KPI series-points (US SEC primary-source layer). Persists file-per-series JSON keyed by company+kpi_id under a durable DATA dir, keeping full history so a restatement appends a superseding record and a point-in-time query sees only what was known then. 営業 KPI 二時制追加専用ストア。營運 KPI 雙時態 唯附加儲存層。
Layer-1 unified data fetch across US/JP/TW/KR/CN equities + macro — one pack.py facade, auto market detection from ticker suffix (.TW/.KS/.SS/.T/ bare-4-digit), 7 pack types (snapshot / memo-fetch / comps-multiples / screener-batch / regime-pack / kpi-quarterly / kpi-topline-backfill). Emits a raw data pack（原始資料包，非渲染卡片）— structured JSON straight from source clients including SEC EDGAR, EDINET, TWSE, and FRED (+14 more) through a shared cache layer; use this for a 資料層 health check, verifying cache writes/hits (快取), or fetching by source name (EDINET/EDGAR/TWSE/etc). Pure I/O, no analysis — for regime classification/判斷 (e.g. an Investment Clock verdict), use analysis-macro-regime instead. Consolidates the per-country data-{us,jp,tw,kr,cn} client scripts behind one CLI + shared cache layer.
Deliver a Mental-Model-first briefing before asking the user to decide a non-trivial engineering fork — the default, not optional. Also fires reactively when they're lost on the question, the explanation, or the stakes — including a 2nd consecutive check-question, which trips the repeated-confusion guard back to the Mental Model.
Family entry router for loom-discovery, the loom problem-space station. Use when unsure which discovery skill applies, or when a product idea's target users are still unclear (說不清是給誰用的 / not sure who this is for / 誰のためかまだ不明) — comes BEFORE product-principles. Routes worth-doing asks (值不值得做 / worth my time budget) to business-value, and user-needs asks (需求研究 / user research / ユーザーインサイト) to user-insights. Non-discovery asks redirect to their family entries. Members share no artifact and no agent.
Router for loom-interface-design — design a product's interface/interaction/UX in any modality (GUI/TUI/CLI). Routes to design-system (→ DESIGN.md) + interaction-flows (→ ui-flows.md). Use for 'design the UI/UX', screen flow, TUI/CLI layout.
The loom-product-principles family entry: intake + routing. Start here on a new product/feature idea when 不確定從哪開始 / 'where do I start' — checks the on-ramp criteria, then hands off to the member skill.