product-principles
Ratify PRINCIPLES.md. Use when a product needs principles or someone asks what should govern product, design, or engineering trade-offs.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- product-principles
- version
- 1.0.0
- description
- Ratify PRINCIPLES.md. Use when a product needs principles or someone asks what should govern product, design, or engineering trade-offs.
02 资源文件 1
- 参考文档README.md1.4 KB
03 SKILL.md 正文
What this tool does
When an outcome priority depends on a consequential evidence gap, identify
that decision and use loom-design:design-research as needed. Reuse adequate
evidence directly; return findings or uncertainty to this task while preserving
the user's preferences, authorization and authority to confirm principles.
Relative paths in this document are relative to this skill's own directory.
Deliver local documents with actual absolute paths from the active worktree or
external location, including in copyable instructions. For known local Markdown
support, use the document's project-relative path as link text (external files:
basename) and absolute targets; otherwise show full absolute paths. Enclose
targets with spaces in angle brackets: [doc.md](</worktree name/doc.md>). Preserve bundled references, stored
relative paths, quoted examples and incidental filenames.
The user names a product idea. You run one short interview, write
PRINCIPLES.md at the consumer project's root, restate it, and — on
"yes" — write the ratified-by: line that makes it the repo's standing
constitution. You never invent a principle the user did not confirm, and
you never ask them to judge anything but their own answers.
Most of the time you are not invoked directly: capture-intent (or, when
loom-design is absent, loom-code's write-plan) runs this same
interview inline, in the same conversation as decision point ①, the first
time a kind: product change meets a repo with no ratified
PRINCIPLES.md. The interview is the same one loom-code's
write-plan runs when loom-design is absent — this tool exists so a
user can also run it stand-alone, on request, before any change is in
flight.
Step 1 — Run the interview
Read ../capture-intent/templates/PRINCIPLES-interview.md and ask
exactly its five questions, in the user's own words, until each answer is
clear. One line each on their intent:
- Who it is for, and how they solve this today without it.
- The one thing that cannot be compromised (fast, accurate, cheap, private, offline, good-looking) — ranked.
- What it explicitly will not do.
- The worst failure, and who it hurts.
- What is already fixed and cannot change (platform, language, a paid service, a data format).
Push until each answer is falsifiable — a later decision can be checked against it, not just admired.
Step 2 — Write PRINCIPLES.md
Emit PRINCIPLES.md at the consumer project's root (not per-feature),
with exactly these five ## sections, in this order:
# Product principles
## Who
## Non-negotiables (ordered)
## Won't do
## Failure we must avoid
## Fixed choices
## Non-negotiables is an ordered list of at least three entries,
each falsifiable: state the choice and a concrete pair that would
tell a stranger it held or broke. For example — good: "offline-first: the
app must complete a save with the network off (bad: 'the app should feel
fast')." A non-negotiable with no such pair is a slogan, not a principle;
push back and ask again rather than write it down.
Step 3 — Restate and ratify
Read the whole file back to the user in their own words — not a diff, the actual sections. On a correction, fix it and read back again; there is no round limit. On "yes", write one line at the top of the file, directly under the title:
ratified-by: <name> <date>
<name> is the user's own name or handle; <date> is today,
YYYY-MM-DD. A file with no ratified-by: line, or one whose
## Non-negotiables has fewer than three entries, is not ratified —
capture-intent checks both conditions itself and runs the interview
before a kind: product change goes on against an unratified file;
nothing here can talk it out of that.
Step 4 — Commit
git add PRINCIPLES.md
git commit -m "docs(loom): PRINCIPLES.md ratified"
Downstream — how the rest of the flow uses it
PRINCIPLES.md is the standing, always-on constraint every later station
reads: write-spec loads it before drafting Requirements; a product
change with no ratified copy is refused there
(standing.product-principles-reject), never silently allowed through.
At closing-review, the principles-conformance dimension scores the diff
against these Non-negotiables; when nothing in the file speaks to a given
finding, the dimension is scored N/A with a one-line reason, never
forced to a number it cannot support. Engineering-only changes are never
blocked by a missing or unratified file — the reject rule fires only on
kind: product.
<!-- gate: product-principles.ratified-requires-user-yes -->
No ratified-by: line is ever written without the user having said
yes to the restatement in Step 3. Writing it on an assumed confirmation
makes a constitution nobody actually agreed to.
04 同仓库更多 Skills
using-loom-workflow
Route broad Loom workflow-tool requests to the right skill. Use when the request spans tools or the right workflow skill is unclear.
skill-retro
Review selected past or current Claude Code or Codex sessions against readable target skill sources and related integration. Produce source-linked proposals without applying changes.
recap-state
Give an in-session recap of current progress for 'where were we', '我們剛剛在幹嘛', '剛剛講到哪', '我跟丟了', 'ちょっと振り返って', '今どこだっけ', or '振り返り'. The built-in /recap is an away-summary.
project-retro
Review one current or specified coding session for source-backed project development improvements. Use for a requested retrospective, including 振り返り seeking improvements; not for current-progress recaps or recurring skill mining.
loom-visualization
Show comparisons, flows, decisions, states or reasoning chains as tables, ASCII or Mermaid in coding chat, including when a Loom station reports to the user (intent restatement, choices, acceptance test results); not Obsidian notes.
loom-memory
Record repo-wide lessons when saving to your own memory or asked to remember; recall, reconcile, or forget them when a task needs it.