Results for “event-id-13”

Creates a new Google Calendar event with optional location, description, attendees, and Google Meet link.

Incident response mode — diagnose a production issue, write a postmortem, add follow-up tasks to TODO.md. Use when user says "/incident [description]".

Manage Google Calendar resources and events via the gws CLI, including ACLs, calendars, events, free/busy queries, and settings.

In-session iterative loop — keeps Claude running in the current session until a task is done. Unlike /loop (which spawns background workers), /iloop stays in the current session and re-prompts each iteration via Stop hook. Use for: 'keep fixing until tests pass', 'iterate until this feature works', autonomous debugging. Triggers on: '/iloop', 'in-session loop', 'keep iterating', 'loop until done'.

Creates or resumes a HANDOFF.md so a fresh Claude Code session can continue work without repeating dead ends, with strict anti-hallucination verification.

Insert urgent work as decimal phase (e.g., 72.1) between existing phases

OI-3 spike harness — heavy consumer skill, INLINE arm. Builds an incident post-mortem and sources the readability standard mid-workflow via an inline (non-forked) guidance skill. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.

Capture idea or task as todo from current conversation context

OI-3 spike harness — heavy consumer skill, FORKED arm. Builds an incident post-mortem and sources the readability standard mid-workflow via a forked (context fork) guidance skill. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.

Reconciles project documentation, agent memory, and rule files against the actual codebase after a development session, ensuring accuracy and consistency across all knowledge layers.