From respit
A three-question pause that keeps creative momentum from accidentally turning into scope sprawl. Run this any time a new idea lands while you are mid-task.
How this skill is triggered — by the user, by Claude, or both
Slash command
/respit:scope-brakeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A three-question pause that keeps creative momentum from accidentally turning into scope sprawl. Run this any time a new idea lands while you are mid-task.
A three-question pause that keeps creative momentum from accidentally turning into scope sprawl. Run this any time a new idea lands while you are mid-task.
Invoke manually whenever a new idea, distraction, or "while I'm in here…" impulse arrives during an active work session. This is a personal check-in, not a gate — no other skill reads or acts on its output.
Answer the following three questions out loud or in writing before deciding what to do with the new idea:
What is the current issue scope? Describe in one or two sentences what you are working on right now and what "done" looks like for this task.
What does this new idea add? Describe the new idea and how it relates (or does not relate) to the current scope.
Can it wait?
If the new idea is unrelated or expands the scope, consider whether it can be captured in ideas.md and revisited later. A "yes, it can wait" is not a rejection — it is a deliberate protection of your current focus.
Inline conversation text only. Reflect on your three answers and decide: continue with the current scope, or capture the idea and return. No file is written. No subagent is spawned.
npx claudepluginhub foculoom/plugins --plugin respitGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.