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
vibe-handoffPrepare compact factual project context for another session or coding tool without copying transcripts or secrets.
Independent GitHub snapshot · Automated classification · Original documentation governs
Inspect the current branch/revision, working-tree changes, MEMORY.md, manifest, decisions, and available check results. Write a compact handoff with objective, current state, changed files, decisions and rationale, blockers, actual checks with date/results, unperformed checks, recovery checkpoint, and the next bounded action.
Reference product documents instead of duplicating them. Exclude secrets, credentials, personal data unnecessary for continuation, and full transcripts. Do not infer successful checks or commit uncommitted changes. Keep stable rules in AGENTS.md and replace stale progress in MEMORY.md rather than appending an unlimited log.