executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
chronicle-skysightUse when recent Linux desktop activity memory would help answer a question or when the user asks to inspect or control Chronicle or Skysight.
Independent GitHub snapshot · Automated classification · Original documentation governs
Call skysight_status first. Status and doctor calls are passive and must not
start capture. Call skysight_snapshot for one bounded activity snapshot.
Start continuous capture with skysight_start only after the user explicitly
requests it. Honor exclusions and use skysight_pause, skysight_resume, or
skysight_stop as requested. Chronicle-compatible resources stay local under
${CODEX_HOME:-$HOME/.codex}/memories/extensions/chronicle/resources.