aped-zoom-out

Review state files and commits to detect drift from the original problem framing.

2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/yabafre/aped-claude --skill aped-zoom-out
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aped-zoom-out
Source: https://github.com/yabafre/aped-claude/tree/main/src/templates/skills/aped-zoom-out
Command: npx skills add https://github.com/yabafre/aped-claude --skill aped-zoom-out

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

APED-zoom-out prevents teams from drifting into implementation details by quickly restoring the original problem framing so you can decide whether to continue, re-anchor, or stop.

Core Features & Use Cases

  • Broader context re-check: Compares the original goal against what’s currently being implemented to detect drift.
  • Read-from-state awareness: Reviews state.yaml, lessons.md, recent decisions, and recent commits (plus the original PRD/brief/ticket or the first user message) to ground the re-orientation.
  • Decision-ready output: Produces a concise 4-bullet orientation message with a drift-aware recommendation, while making no state changes.
  • Use when context fades: Ideal when you hear prompts like “zoom out”, “step back”, “lost the thread”, or you suspect the work is no longer aligned with the intended outcome.

Quick Start

Use aped-zoom-out when you want a broader view of whether the current work still matches the original goal.

Frequently Asked Questions about aped-zoom-out

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

FAQPage Schema
How do I check if my code commits are drifting from the original product requirements?

Goal alignment drift detection compares your original product requirements against recent commits and decisions. It reviews your project state to identify when implementation work no longer matches the intended outcome, providing a concise orientation message.

What is the best way to re-anchor developer workflow when context is lost?

Re-anchoring a developer workflow involves reviewing recent state files and decisions to restore the original problem framing. This process correlates implementation drift with commit pointers, producing a short orientation message to help you decide whether to continue, re-anchor, or stop.

How does decision traceability work when stepping back to review architecture decisions?

Decision traceability works by correlating recent architecture decisioning pointers with current state changes. It reads available state files and lessons logs to trace how and when implementation drifted from the original goal, ensuring you can validate the current trajectory.

Can I get a broader view of my project state without modifying any existing files?

Yes, you can get a broader view without modifying files. The process reads state and lessons files to analyze decision traceability, then produces a read-only, four-bullet orientation message with a drift-aware recommendation, making no state changes or writing any artefacts.

When should I use a zoom out approach to review product requirements?

You should use a zoom out approach whenever you request a broader view, lose context, or doubt that current changes solve the right problem. It is ideal for detecting drift across any project phase when you suspect work is no longer aligned with the intended outcome.