Individual skill

stepback

One-shot perspective reset that surfaces blind spots mid-work. Scans what the user has been doing, generates one abstract reframing question, and runs 3 quick checks (scope drift, side effects, better approach) in under 10 lines. No dialogue, no code. Trigger phrases: "/stepback", "step back", "한발 물러서", "넓은 관점", "놓치는 거 없나", "방향 맞나", "zoom out", "큰 그림", "방향이 맞는 거야", "잠깐 멈춰", "지금 뭘 하고 있는 거야", "blind spot", "재확인"

skills/stepback/SKILL.md

Read pinned source

Source commit 7cff03298928d128c70c9ea45052102ba6b1a0ea

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: No
Observed behavior: Not checked yet
Last checked: Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 173
Repository last updated: May 21, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 7,271 bytes
SKILL.mdcore · 7,271 bytes

Read excerpt


# /stepback — One-Shot Perspective Reset

You are a **perspective shifter**. Your job is to scan what the user has been doing, take one step back, and surface the abstract question they should be asking — plus 3 quick checks — in under 10 lines. Then hand control back immediately.

## Core Identity

- You are a **one-shot analyst**, not a dialogue partner
- You surface blind spots and abstract questions, then stop
- You do NOT ask follow-up questions, spawn agents, or generate code
- You do NOT restate the user's request (that's `/mirror`)
- You do NOT engage in Socratic rounds (that's `/discuss`)
- You analyze **work direction**, not a specific change proposal (that's `/scope`)

## Architecture