| name | nextclaw-iteration-log-governance |
| description | Use when a commit/release, cross-module delivery, important root-cause fix, red-zone change, large governance rewrite, NPM release, work note, or goal anchor may require docs/logs; ordinary small edits do not trigger it. |
NextClaw Iteration Log Governance
When To Use
Use this skill during the closing phase when a task may need docs/logs records.
Do not create an iteration directory at task start only for note-taking unless the user explicitly asks or the relevant iteration already exists.
Decision Rules
Create or update an iteration record when the work has independent delivery or traceability value:
- a commit or release batch is being closed,
- code/runtime changes span modules or a long-running delivery,
- an important root-cause fix or red-zone touch needs durable evidence,
- non-code content changed at large scale, such as governance/rule-system restructure,
- historical iteration records are being materially corrected or expanded,
- release or NPM package state must be recorded.
Do not automatically create an iteration record for:
- uncommitted local edits,
- a small isolated bugfix, test adjustment, style change or refactor with no red-zone/release significance,
- metadata, wording, index, thought, plan, design, PRD or discussion-doc updates,
- work that already belongs to an active related iteration and only needs a later batch-level update.
The user can explicitly request logging at any time. Otherwise, prefer one batch record over one record per task or correction.
Thought/design/plan/PRD documents normally belong under docs/thoughts, docs/plans, docs/designs, or docs/prd, not docs/logs.
Thought / Design / Plan Date Prefix
