菜单
Prepends relevant project decisions to docs/decisions/YYYY-MM-DD.json (newest first in entries). Use when scope, stack, security, architecture, versions or acceptance criteria change.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | update-decisions-log |
| description | Prepends relevant project decisions to docs/decisions/YYYY-MM-DD.json (newest first in entries). Use when scope, stack, security, architecture, versions or acceptance criteria change. |
| allowed-tools | Read, Glob, Grep, Bash, Edit, Write |
| File | When to read |
|---|---|
references/decision-template.md | When registering each new entry |
references/decision-schema.md | When creating daily file or validating fields |
Change in: scope, stack, security, users, epics, versions, architecture, database, API, environments, acceptance, agent governance.
YYYY-MM-DD) — run date +"%Y-%m-%d" at project root (never guess from chat or training cutoff).date +"%H:%M" (24h, local). Use that value for entries[].time. Do not round to :00/:15/:30/:45 or invent a time.docs/decisions/YYYY-MM-DD.json.entries using references/decision-template.md.date in JSON matches filename.approved doc was changed → status: review on that doc + mention in impact.Old days remain as immutable JSON files in docs/decisions/.
Do not compact or move old entries — history is append-only by prepend.
Decision logged:
File: docs/decisions/YYYY-MM-DD.json
Affected document:
Docs moved to review:
Follow-up:
Closes a Meridian sprint after sprint review — fills Retrospective, sets status complete, logs decisions. Use with /complete-sprint vX-SY.
Closes a Meridian user story after implementation — fills Record, acceptance, status and board. Use when marking US done, completing US-XXXX, or after implementing a user story.
Creates a Meridian epic file in docs/epics after architecture is approved. Use when defining a new product capability block before user stories.
Creates a Meridian sprint file in docs/sprints linked to a version. Use when planning execution slices within a release.
Creates a valid Meridian user story after epics and versions are approved. Use when adding work to docs/us and keeping acceptance criteria concrete.
Creates a Meridian release file in docs/versions. Use when defining a new product version before user stories.