Menü
Plan the change as OpenSpec artifacts — proposal, delta specs, design, tasks
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Answer the owner's questions about a running or finished loop from its records — read-only, in a separate session
Hours-long (3-12h) multi-agent code-architecture optimization — cross-examines antipatterns into consensus, then applies only the highest-ROI refactors. Not for routine refactors.
Hours-long (3-12h) multi-agent documentation-architecture optimization — verifies every claim in every non-executable text (markdown, spec systems, comments) against the code, cross-examines discrepancies into consensus, then applies only the highest-ROI fixes. Code is never modified — defects are reported, not fixed. Not for touching up a single file.
Hours-long (3-12h) multi-agent integrity-boundary optimization — hunts every reachable state the boundary (types, invariants, error definitions, tests) fails to contain, then absorbs only the highest-ROI set into it — code and docs both, pinned by tests. Not for fixing a known bug.
Implement the planned change task by task, then spawn the independent verify stage until it passes
Archive the completed change — task gate, delta sync into main specs, revalidate
| name | plan |
| description | Plan the change as OpenSpec artifacts — proposal, delta specs, design, tasks |
| argument-hint | [change intent] |
| effort | max |
변경의 intent·design을 change artifact로 기록한다. squash merge는 branch history를 지운다 — 이 artifact의 archive만이 그 과정을 보존한다.
change-id를 정한다 — 보통 tx branch의 slug와 같다.
"${CLAUDE_PLUGIN_ROOT}/bin/tx-hook" openspec new change <change-id>
artifact를 dependency 순서로 작성한다. artifact마다 instructions·format·template을 engine에서 받는다 — format의 정본은 engine이다:
"${CLAUDE_PLUGIN_ROOT}/bin/tx-hook" openspec instructions <artifact> --change <change-id> --json
task에는 close 전에 done이 되는 작업만 적는다 — transaction의 종결(close·archive·merge)과 merge 이후의 행동(deploy·production 검증)은 task가 될 수 없다. 후자는 후속 change다.
validate한다:
"${CLAUDE_PLUGIN_ROOT}/bin/tx-hook" openspec validate <change-id> --strict --no-interactive --json
delta 없는 change(tooling·infra·docs 변경)에서는 validate가 class 전체로 no deltas
ERROR를 낸다 — 이 ERROR는 fix 대상이 아니고, 그 class의 gate는 task 완료와
archive의 --skip-specs, 사후 CI다. 그 외의 지적은 전부 green까지 수정한다.
즉시 tx:apply로 이어간다 — plan은 구현의 시작이지 정지점이 아니다.
계획 중 만나는 모든 unknown은 셋 중 하나로 처리한다: