القائمة
Memory-only planner report mode: sender routing, AUTO reports, and goal-drift recall.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | memory-report-mode |
| description | Memory-only planner report mode: sender routing, AUTO reports, and goal-drift recall. |
| version | 1.0 |
| status | stable |
Memory loads this skill in addition to clawseat-intake. It is only for
messages that come from planner or project-control channels, not for direct user
intake.
Route by sender metadata before interpreting content:
sender == "user" -> Clarify mode
sender == "planner" -> Report mode
sender unknown -> Clarify mode
Channel only changes rendering. Claude/Codex/Gemini TUI uses concise Markdown; Feishu recall cards may use native card controls through Koder.
Planner updates become an AUTO decision report:
[Action] [Reason 1 sentence]
Do not add preamble, ask approval, or write "I suggest". Memory acts as the user's proxy and reports the current best action with the shortest defensible reason.
Reference: references/report-mode.md
Interrupt AUTO reporting only when one of the four goal-drift signal families crosses threshold:
Recall cards have at most 3 options. Plain AUTO reports do not ask for approval.
References:
references/drift-signals.mdreferences/tui-card-format.mdreferences/north-star-schema.tomlclawseat-intake
for direct user intake.Generic solo TUI architecture/spec skill. Use this skill whenever the user asks an agent to act as a warden, professional code/architecture advisor, root-cause investigator, AI-friendly spec author, product test pilot, prompt translator, or lightweight coordinator for another TUI, SDK, memory seat, or coding agent. Also use it for concise task relay, Cartooner/product testing, issue investigation, and implementation-ready briefs. Do not use it for canonical project memory, planner fan-out, queue ownership, or thick seat protocol execution.
L3 project-memory hub for patrol, KB maintenance, queue/state tracking, faithful dispatch of operator/warden briefs, and E2E verification. Use when handling operator requests, context queries, decisions, deliveries, queue-drained receipts, or review/latest integration. Do not use for code, review, product-intent rewriting, direct specialist work, or seat lifecycle.
Federated memory oracle: synthesizes facts from ~/.agents/memory KB and preserves operator/warden brief intent during project-memory handoffs. Use when remembered facts, project-history synthesis, cross-seat evidence, queue-state context, or closeout recall are needed. Do not use for implementation, direct specialist work, or guessed facts.
Workflow author and dispatch orchestrator for ClawSeat tasks that need routing across specialist seats. Use when memory provides a brief, when workflow.md must be authored, when assigning owners, fan-out, liveness checks, SWALLOW fallback, or delivery consumption is required. Also use when coordinating review and next-step notifications. Covers workflow decomposition, schema validation, dispatch receipts, and planner summaries. Do NOT use for code implementation, independent review verdicts, visual QA, or project memory authority.
Multi-seat harness: bootstrap roster, start seats, dispatch tasks, complete handoffs with durable ACKs, provision frontstage heartbeat, render CLI operator console for a project profile.
Installer playbook for bootstrapping ClawSeat projects from the repository install flow. Use when the user asks to install ClawSeat, initialize a project, understand install.sh flags, recover an install, or follow docs/INSTALL.md setup steps. Also use when validating installer prerequisites or CLI-first onboarding. Covers install command discovery, environment assumptions, and resume guidance. Do NOT use for post-install task dispatch, normal /cs re-entry, code implementation, or modifying machine profiles without the install procedure.