القائمة
Prepends a project decision to SQLite (.meridian/meridian.db decisions table). Use when scope, stack, security, architecture, versions or acceptance criteria change.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | update-decisions-log |
| description | Prepends a project decision to SQLite (.meridian/meridian.db decisions table). Use when scope, stack, security, architecture, versions or acceptance criteria change. |
| allowed-tools | Read, Glob, Grep, Bash, Edit |
| File | When to read |
|---|---|
references/decision-template.md | Field checklist for each entry |
references/decision-schema.md | Validation rules |
Change in: scope, stack, security, users, epics, versions, architecture, database, API, environments, acceptance, agent governance.
meridian.db exists — run python3 .agent/scripts/meridian_delivery.py bootstrap if missing.Write on docs/decisions/*.json when SQLite delivery is active.YYYY-MM-DD) — run date +"%Y-%m-%d" at project root (never guess).date +"%H:%M" (24h, local). Use for --time. Do not round or invent.entry_index 0 for that date):python3 .agent/scripts/meridian_delivery.py prepend-decision \
--date "$(date +"%Y-%m-%d")" \
--time "$(date +"%H:%M")" \
--title "Objective decision title" \
--affected-document "docs/05_architecture.md" \
--what-changed "factual description of delta" \
--why-changed "context and motivation" \
--impact "affected docs; mark review" \
--responsible "manager or role"
Alternative: single entry JSON file → --from-json /tmp/decision-entry.json.
approved phase doc changed → set that doc status: review + mention in --impact.python3 .agent/scripts/meridian_delivery.py list decisions
python3 .agent/scripts/meridian_delivery.py show-decisions --date YYYY-MM-DD
python3 .agent/scripts/meridian_delivery.py show-decisions --date YYYY-MM-DD --json
History lives in SQLite (decisions table). Do not compact or rewrite old entry_index values except via prepend-decision (which shifts indices for the same day).
Decision logged:
Store: .meridian/meridian.db (decisions)
Date: YYYY-MM-DD
Clock used: HH:MM (from date command)
Affected document:
Docs moved to review:
Follow-up:
Creates a Meridian user story in SQLite after epics and versions exist. Use when adding work to the backlog with concrete acceptance criteria.
Refines a Meridian user story in SQLite for implementation — deepens Approach, architecture refs and tests. Use between /create-us and coding.
Gates implementation of a Meridian user story — verifies ready true, Plan, deps and architecture refs before product code. Use with /implement-us US-XXXX.
Maintainer procedure to add or change Meridian kit artifacts — skill, agent, workflow, routing, and every registry surface. Use when extending the harness, creating /investigate, or onboarding a new slash command.
Closes a Meridian sprint in SQLite after sprint review — fills Retrospective, sets status complete, logs decisions. Use with /complete-sprint vX-SY.
Closes a Meridian user story in SQLite after implementation — fills Record, acceptance, status. Use when marking US done or after /implement-us.