context-restore

To resume engineering context, read the latest checkpoint file in .context/sessions/ alongside repository artifacts like feature-spec and dev-log to assemble a structured briefing. This process surfaces project status and gaps without modifying source code.

A read-only engineering briefing is a structured summary of project status, gaps, and verification signals derived from checkpoints and repository artifacts. You need it before starting implementation to review where you left off without accidentally modifying source code.

You can restore a software engineering session across multiple branches by loading the most recent checkpoint and reading header-level artifacts. This supports multi-branch resumes by surfacing status, next actions, and verification gaps for each branch.

No, the context restore process is a hard gate that never edits source code or starts implementation. It reads feature README, feature-spec, tdd-spec, and test-scenarios strictly as read-only inputs to generate a briefing.

Check for stale artifacts and verification gaps by loading a context-save checkpoint and reading repository artifacts. The resulting briefing explicitly flags outdated artifacts and missing verification signals for timely re-checks.

Yes, you can use checkpoint files in .context/sessions/ to pick up where you left off. The skill reads these checkpoints plus the latest dev-log section to present a structured briefing of your current engineering status.