القائمة
Document architectural decisions as engraph ADRs. Store context, options considered, rationale, and consequences for queryable decision history.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Every commit must reference a valid engram task UUID. Covers format, validation, and why --no-verify is prohibited.
Orchestrator agent loop. Coordinates work across subagents using engram as shared state. Search before acting, dispatch by UUID, validate before finishing.
Plan feature implementation by creating an engram task hierarchy. Not a markdown plan — a queryable task tree any agent can retrieve.
Universal session end protocol. Run at the end of every agent session — closes open tasks, generates a handoff summary, syncs to remote, and validates state.
Universal session start protocol. Run at the beginning of every agent session — syncs from remote, opens a session, loads prior context, and surfaces the next action.
Subagent registration protocol. Use when assigned a task UUID by an orchestrator — claim the task, pull context from engram, store all findings, and report results back.
| name | engram-adr |
| description | Document architectural decisions as engraph ADRs. Store context, options considered, rationale, and consequences for queryable decision history. |
Use ADRs for significant technical choices with lasting impact. Store in engram so future agents can query why decisions were made.
Per-turn write rule:
engram_adr_createcounts as an engram write and resets theengram-write-firstcounter. Always follow withengram_relationship_createto link the ADR to its task. If you do research (bash/read) before writing the ADR, store interim findings asengram_context_create— don't let the research turns accumulate without writes.
engram_adr_create title="<Short Decision Title>" number=<N> context="<Situation, options considered, what was decided and why>" agent="<name>"
# ADR_UUID
The context field should include:
engram_relationship_create source_id=<TASK_UUID> source_type=task target_id=<ADR_UUID> target_type=adr relationship_type=relates_to agent="<name>"
# This ADR supersedes a previous one
engram_relationship_create source_id=<NEW_ADR_UUID> source_type=adr target_id=<OLD_ADR_UUID> target_type=adr relationship_type=explains agent="<name>"