メニュー
Author or modify a loom skill file. Provides SKILL.md structure, frontmatter format, and quality checklist. Use when: creating or updating loom skills, their frontmatter, triggers, or quality checklist.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Read-only cross-artifact consistency analysis after planning and before approval. Verifies that spec.md, requirements.json, plan.md, tasks/Tn.md, traceability.json are mutually consistent: no duplicate/ambiguous requirements, every behavior mapped to a task, no orphan tasks, no coverage gaps, no contradictions. Outputs artifact-analysis.json with coverage% and severity. CRITICAL/HIGH findings block the approval gate. Use when: planning produced plan.md + tasks + traceability.json, before the user approves the plan.
Explore 2-3 implementation options with trade-offs when the user describes a new feature or requirement. Use when: the user asks for a new feature design, implementation options, or technical trade-off analysis.
After implementation and before final verification, compare current code/tests against the intent inventory (requirements.json + traceability.json). Classify each requirement/behavior as covered, missing, partial, contradicts, or unrequested. Append missing/partial/contradicts as new tasks back to executing. Repeat until converged: zero blocker findings. Outputs convergence-report.json. Use when: executing produced test-report.md but before loom-verification-before-completion.
Expand each requirement into verifiable Behavior Obligations across 15 fixed dimensions (happy-path, boundary, invalid-input, authorization, state-transition, idempotency, concurrency, atomicity, external-failure, compatibility, security, performance, observability, recovery, forbidden-behavior) before planning. Use when: brainstorming produced requirements.json and spec is approved, but behaviors are still placeholders or only happy-path; before loom-writing-plans.
Read-only adversarial reviewer that looks for what SHOULD exist but doesn't, by cross-checking Behavior Obligations against code, tests, expected side effects, forbidden side effects, failure scenarios, and public API changes. Focuses on negative space: events that should not repeat, permissions that should not be bypassed, partial writes that should not happen, old APIs that should not change, swallowed exceptions, leaked secrets. Outputs findings.json. Use when: executing or converge needs an independent omission sweep.
Analyze user request + collect signals (file scope, keywords, worktree state, spec existence), then select pipeline steps via rule short-circuit / AI fallback / rule-based fallback. Select steps first, expose the choice to the user, and persist selected dynamic_steps only after explicit user confirmation; pipeline-plan.md is optional for manual review. Use when: user is unsure which pipeline type to pick, or wants AI to choose steps automatically.
| name | loom-writing-skills |
| description | Author or modify a loom skill file. Provides SKILL.md structure, frontmatter format, and quality checklist. Use when: creating or updating loom skills, their frontmatter, triggers, or quality checklist. |
| when_to_use | Create or update a Loom skill, including its metadata, trigger boundaries, and quality checks. |
| argument-hint | <skill name or change request> |
| user-invocable | true |
skills/
<skill-name>/
SKILL.md # 必需：skill 主文件
references/ # 可选：参考文件
*.md
scripts/ # 可选：可执行检查、生成器、转换器
assets/ # 可选：模板、prompt 片段、示例输入输出
evals/ # 可选：触发边界样例
---
name: loom-<skill-name>
description: >
简短描述。说明何时使用此 skill。
Use when: <触发条件描述>.
Trigger keywords: <关键词列表>.
---
# <Skill 标题>
## 触发条件
- 用户说 xxx 时触发
- 在 xxx 流程中自动触发
## 执行流程
### Step 1: ...
### Step 2: ...
## 约束
- 规则 1
- 规则 2
## 完成条件与下一步
完成后继续。
| 字段 | 必需 | 说明 |
|---|---|---|
| name | 是 | skill 名称，必须与目录名一致 |
| description | 是 | 简短描述，用于 Skill 工具选择 |
| 正确做法 | 反模式 |
|---|---|
| 单一职责 | 一个 skill 做多件事 |
| 清晰触发条件 | 触发太宽或太窄 |
| 完整执行流程 | 步骤描述模糊 |
| 可中断、可链式 | 缺少完成条件或不串联 |
| 有必要的自检清单 | 输出质量不可验证 |
dynamic_steps 或推进 pipeline.state.json。description 必须说明 Use when:，并保持短而精确。SKILL.md 只放必须执行的步骤；长解释、示例、模板放 references/ 或 assets/。修改 skill 时逐段做 no-op test：如果删除某句话不会改变 agent 行为，就删除或移入 reference。
常见沉积信号：
详细的 references 结构、scripts/evals 写法、测试方法和常见反模式见 references/detailed-guide.md。