reorient

Reloads charter, checkpoint, and task state to restore working context after compaction.

150|10|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/swingerman/engineer --skill reorient-swingerman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reorient
Source: https://github.com/swingerman/engineer/tree/main/engineer/skills/reorient
Command: npx skills add https://github.com/swingerman/engineer --skill reorient-swingerman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a context compaction, a long agent run, or an interruption, an AI agent loses its role identity, invents constraints, skips required steps, and loses track of the current task. This Skill restores the durable working contract mid-task so the agent re-anchors on the real state instead of guessing. ## Core Features & Use Cases - Contract Reload: Reads the project charter, autonomy level, current checkpoint exit criteria, and feature contract in a fixed order to rebuild the discipline context. - Orientation Block Output: Emits a single concise block stating role, autonomy, checkpoint progress, unmet exit criteria, current task, next action, and non-negotiables. - Stuck-Loop Detection: Scans recent handoffs for three or more consecutive identical failures and escalates to the human with a decision handoff instead of silently retrying. - Use Case: After a session compaction mid-feature, run the reorient command to recover which checkpoint is in progress, which exit criteria remain unmet, and what the next action is, without modifying any files. ## Quick Start Ask the agent to reorient on the current feature after a context compaction so it reloads the charter, checkpoint status, and next action.

Frequently Asked Questions about reorient

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I recover AI agent context after a compaction?▼

Invoke the reorient command mid-task to reload the discipline contract. It reads the charter, current checkpoint exit criteria, progress tracker, and feature contract, then emits one orientation block with your role, unmet criteria, and next action.

What is the difference between reorient and a session-start next command?▼

Reorient is mid-task and feature-scoped, restoring the working contract for a feature already in progress. The next command is project-scoped and session-start, answering what to pick up across the whole project.

Does reorient modify files or produce artifacts?▼

No, reorient is read-only and advisory. It changes nothing and emits no handoff, except when it detects a stuck loop, in which case it writes a single escalation handoff requesting human review.

How does stuck-loop detection work in agent workflows?▼

It scans recent handoffs for three or more consecutive entries from the same skill with the same status, recommended next step, and failure signature. When detected, it stops and escalates to the human instead of retrying the same failing operation.

When should I not use reorient?▼

Do not use it for session-start project planning, loading a feature that has not started, or validating artifacts. Those cases belong to the next, prime-context, and consistency-check skills respectively.