using-loom-product-principles

name	using-loom-product-principles
description	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.
version	0.1.0

If you are a subagent already dispatched with an explicit role prompt, **do not** re-route through this skill. Follow the prompt you were dispatched with directly. This router is for the parent orchestrator only.

This is the loom-product-principles family entry — a thin router, not the skill that writes the constitution. It does intake + routing, then hands off.

§Intake

User-facing narration in this intake follows loom-pipeline/hooks/family-relay.md §Family relay discipline — reference it, do not copy its rules here.

Step 1 — 前站檢查 (upstream check)

Check the target repo against the loom family reception's on-ramp criteria table — the single source of truth lives in loom-pipeline/hooks/family-reception.md. Reference it, do not copy its rows here. If docs/loom/PRINCIPLES.md already exists in the target repo, confirm with the user whether this station's work is already done before proceeding.

Step 2 — 對站檢查 (sibling-station redirect)

If the user's actual ask belongs to a different family entry, redirect instead of proceeding here:

• A design-surface ask (UI/UX, screens, interaction flows) → using-loom-interface-design
• A spec / requirement fan-out ask (multi-state behavior, edge cases, acceptance criteria) → using-loom-spec
• A coding ask (write, change, review, or ship code) → using-loom-code
• The problem/users are unarticulated (no evidence for who needs what) → using-loom-discovery first; resume here with its output as seed

Brief before you ask a complex product/principle fork. Before you ask the user a product/principle 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.

Step 3 — Hand off

Once intake confirms this is the right station, hand off to product-principles — the member skill that elicits the idea, drafts the ## North Star, and derives the 3–7 falsifiable principles into PRINCIPLES.md. This entry does not do that work itself.

What this router does NOT do

• Does not author PRINCIPLES.md itself — that is product-principles's job.
• Does not duplicate the on-ramp criteria table — it references loom-pipeline/hooks/family-reception.md as the single source of truth.
• Does not auto-invoke product-principles — the harness invokes it once intake and routing confirm this is the right station.