القائمة
Use when the current run should persist a durable decision, checkpoint, or summary into the vault.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use as the canonical first-stage Agmo workflow when the user wants idea exploration, design tradeoffs, or requirement shaping before planning or implementation.
Run a Codex-native structured code review using agmo-critic and agmo-verifier where evidence is needed.
Harvest `debt:` markers across the repo into a read-only ledger without modifying code.
Audit and maintain the vault-backed llm-wiki knowledge base, including stale pages, low-confidence or contested captures, superseded captures, missing frontmatter, and broken wikilinks.
Use when prior notes, durable project knowledge, or vault-backed context should influence the current task.
Use when one execution lane is no longer enough and work should escalate to the durable `agmo team ...` runtime.
| name | save-note |
| description | Use when the current run should persist a durable decision, checkpoint, or summary into the vault. |
| argument-hint | [summary, decision, or note purpose] |
Use this when the result should survive outside transient chat.
The main session should delegate durable note preparation to agmo-wisdom, then persist the resulting summary through Agmo's vault path.
After the delegated result is integrated or persisted, call close_agent for the agmo-wisdom lane so the completed native subagent session releases its thread slot.
Use this for:
Do not save a raw transcript dump when a cleaner artifact summary is possible.
Default expectation:
design, plan, implementation, research, memo)Normalize obvious low-quality inputs such as:
응 진행해줘Before ending this workflow, make the final response or delegated result save-ready: