菜单
Use when the user wants to develop a plan, settle an architectural or product decision, or stress-test a proposal against the existing criv vault before writing anything down.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/TudorAndrei/criv --skill criv-me命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | criv-me |
| description | Use when the user wants to develop a plan, settle an architectural or product decision, or stress-test a proposal against the existing criv vault before writing anything down. |
criv-me is an interview: settle one decision at a time with the user, then write the settled rationale into the vault.
The existing documents, ADRs, wiki-links, governed scopes, and source code are
the decision context. Find the relevant ones first with rg, criv query, or
a direct read from docs/. Read the source whenever it answers a factual
question, and spend the user's attention only on intent, tradeoffs,
constraints, and choices the repository cannot settle.
The vault already carries the project language, rationale, and governance. Take those from the vault rather than from conventions of other workflows.
Ask one question at a time, and give your recommended answer with its reasoning inside the question.
Walk the dependencies in order: terms and constraints, then irreversible architecture, then implementation boundaries, enforcement, tests, rollout, and documentation.
Challenge a fuzzy or overloaded term by proposing a precise project term. Challenge a claim that conflicts with the code, a document, an ADR, or a governed scope. Use a concrete scenario or an edge case to expose an unclear boundary.
This part is done when every settled answer is stated in the user's own accepted words, and each open question has an owner or a stated assumption.
Write a settled explanation into the document it belongs to. Reach for a new ADR only when the decision is hard to reverse, surprising without its context, and the result of a real tradeoff; otherwise update or supersede the ADR that already covers the ground.
The writing-decisions skill owns the ADR format, governs scopes, and policy
patterns. The referencing-code skill owns the wiki-link forms that connect
the decision to source.
The session is complete when every settled decision is written down and the
vault is green, as the checking-drift skill defines it.
