메뉴
Overview of the loom engineering framework: pipeline stages, skills catalog, and review dimensions. Load when the user asks about loom capabilities or how to use it. Use when: the user asks how loom works, what skills exist, or how to run the engineering pipeline.
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-using-loom |
| description | Overview of the loom engineering framework: pipeline stages, skills catalog, and review dimensions. Load when the user asks about loom capabilities or how to use it. Use when: the user asks how loom works, what skills exist, or how to run the engineering pipeline. |
| when_to_use | Explain Loom concepts, pipeline stages, skill catalog, or framework usage. |
| argument-hint | <question about Loom> |
| user-invocable | true |
loom 是一个 AI 工程化框架，把需求、规范、上下文、执行过程"织"成一套稳定工程流程。流水线由 .loom/workflow.yaml 集中定义。
严令禁止跳步
严令禁止跳过任何步骤。每个步骤完成后必须显式触发下一步，不可自行终止。
所有 skills 通过 / 命令或 Skill 工具调用。详见 .loom/skills/ 目录（完整定义）
核心流水线 Skills：
| Skill | 输出 | 说明 |
|---|---|---|
| loom-brainstorming | specs/<date+feature>/spec.md | 需求头脑风暴, +可视化伴侣、设计自检、用户审查 Gate |
| loom-detail-expansion | specs/<date+feature>/requirements.json | 按 15 维度展开 Behavior Obligation，补齐 test_plan 与 applicability |
| loom-writing-plans | specs/<date+feature>/plan.md | 分层拆解 task, +模型选择、类型一致性检查 |
| loom-analyze-artifacts | specs/<date+feature>/artifact-analysis.json | planning 后审批前跨产物一致性只读分析 |
| loom-using-git-worktrees | feature 分支 | 创建隔离分支, +测试基线验证 |
| loom-subagent-driven-development | 源码 + 测试报告 | Subagent 派发 + 双重审查,独立模板文件、4种状态处理 |
| loom-converge | specs/<date+feature>/convergence-report.json | executing 后 verification 前对照意图清单，missing/partial 回流 executing |
| loom-omission-hunter | specs/<date+feature>/findings/omission-hunter.json | 只读对抗式审查，负空间检查（应存在但不存在） |
| loom-verification-before-completion | 验证报告 | 完成前验证, +Spec覆盖、类型一致性、编译测试 |
| loom-index-update | codegraph 同步 + 结构化记忆 | codegraph 同步 |
辅助 Skills：
| Skill | 说明 |
|---|---|
| loom-init-project | 项目初始化（扫描 + 生成宪章/记忆/入口） |
| loom-router | 轻量入口路由（分流到 skill 或 pipeline selector，不写流水线状态） |
| loom-pipeline-selector | 开发流水线步骤选择（确认后写入 dynamic_steps） |
| loom-using-loom | loom 框架使用指南（本 skill） |
通用 Skills：
| Skill | 说明 |
|---|---|
| loom-test-driven-development | TDD 测试驱动开发，+流程图、好/坏示例、常见借口表 |
| loom-systematic-debugging | 系统化调试, +4阶段流程图、条件等待、纵深防御 |
| loom-requesting-code-review | 请求代码审查, +预审查清单、审查模板 |
| loom-receiving-code-review | 接受代码审查, +响应模板、流程图 |
| loom-dispatching-parallel-agents | 并行 agent 派发, +模型选择、并发工作流图 |
| loom-writing-skills | 编写自定义 skills, +方法论深度、流程图 |
| loom-finishing-a-development-branch | 分支完成流程 , +选项展示（Merge/PR/Keep/Discard） |
测试 Skills：
| Skill | 输出 | 说明 |
|---|---|---|
| loom-qa | qa/<date+target>/qa-report.md | QA 验收流水线，测试人员使用：新功能验证 + 回归 + 集成测试 + 持久化用例库 |
| 维度 | 关键检查项 |
|---|---|
| 架构合规 | 是否遵循项目架构分层（从 constitution.md 读取）、是否存在跨层调用 |
| 代码质量 | 是否使用了项目禁止的调试函数、SQL 是否参数化（防注入） |
| 安全风险 | SQL 注入检查、认证/授权是否正确 |
| 性能隐患 | N+1 查询检查、分页查询是否使用框架分页组件 |
| 规范一致性 | 命名是否符合项目规范、响应格式是否统一 |
| 变更影响范围 | 本次变更的函数、接口、类型是否被其他模块引用（codegraph 可用时查 codegraph_impact/codegraph_callers，否则用源码搜索补充判断）、公开接口的参数签名是否变化（新增必填参数、删除字段、类型变更） |
