一键导入
concept-draft-review
Review upstream ConceptSpec drafts, issue notes promoted toward ConceptSpec, or early design memos before they are treated as stable grounding.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Review upstream ConceptSpec drafts, issue notes promoted toward ConceptSpec, or early design memos before they are treated as stable grounding.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Assess and dispatch rawsql-ts developer tasks by tracing repository impact, concept and package boundaries, verification cost, difficulty, risk, model and reasoning effort, and Codex worktree requirements. Use when a new rawsql-ts issue, bug, feature, refactor, investigation, CI failure, review request, migration, or documentation change must be analyzed before action or handed to a new Codex task.
Report per-item attainment for completed rawsql-ts developer work.
Review tracked rawsql-ts package-level Scope, Test Policy, Authority Model, Technology Policy, review-plan, and generated review views before package implementation or documentation changes. Use only when those package-owned artifacts exist in the checked-out base.
Prepare rawsql-ts pull requests with the repository PR template and local readiness gate so required merge, CLI migration, and scaffold proof sections are not missed.
Check tmp/RETRO.md before PR or human review so unresolved retro items do not slip through rawsql-ts developer workflow.
Capture meaningful recognition mismatches, false completion claims, and verification misses into tmp/RETRO.md for rawsql-ts developer work.
| name | concept-draft-review |
| description | Review upstream ConceptSpec drafts, issue notes promoted toward ConceptSpec, or early design memos before they are treated as stable grounding. |
Use this skill when an upstream ConceptSpec draft, issue note promoted toward ConceptSpec, or early design memo needs concept-level review before DFD, Process Map, DDL, RFBA, or implementation work.
This skill reviews upstream drafts. It does not replace existing ConceptSpec, package-spec, or logical-model review skills for approved or structured specs.
Use this structure and omit empty sections:
# Concept Draft Review
## Status
ready-to-propose-promotion | draft-can-continue | needs-revision | needs-human-decision | blocked
## Existing Context Checked
- scope:
- concepts:
- DFDs:
- processes:
- relationship metadata:
## Findings
### Contradictions
- finding:
why it matters:
suggested direction:
### Missing Definitions
- finding:
why it matters:
suggested direction:
### Boundary Risks
- finding:
why it matters:
suggested direction:
### Relationship Gaps
- finding:
why it matters:
suggested direction:
### Process Connection Gaps
- finding:
why it matters:
suggested direction:
### Implementation Leaks
- finding:
why it matters:
suggested direction:
## Unresolved Register
### Decision Required Now
- decision:
why it blocks:
### Decision Can Wait
- decision:
why it can wait:
revisit trigger:
### Acceptable Unknowns
- unknown:
why it is acceptable:
## Suggested Next Artifact
- none | ConceptSpec update | concept-relationship metadata update | DFD draft | Process Map draft | feature-local spec | scope decision
The review may organize, classify, and propose.
It must not approve the draft as authoritative ConceptSpec meaning by itself.
ready-to-propose-promotion means ready for human promotion review, not AI approval.