looper

Document blockers, analyze root causes, and generate at least three alternatives.

1|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/spenceriam/impulse --skill looper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: looper
Source: https://github.com/spenceriam/impulse/tree/main/.opencode/skills/looper
Command: npx skills add https://github.com/spenceriam/impulse --skill looper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Blockers in complex tasks can stall progress; Looper provides a disciplined pattern to document the blocker, analyze root causes, generate multiple alternatives, and iteratively attempt the next best option until resolution.

Core Features & Use Cases

  • Blocker documentation: Record what happened, when, and why it blocked progress to preserve context.
  • Root-cause analysis: Systematically identify the underlying reasons for the blocker.
  • Alternative generation: Propose at least three viable approaches and compare their feasibility.
  • Iterative execution: Switch to the next best approach after each attempt and track outcomes.
  • Integration readiness: Works with debugging workflows, planning sessions, and cross-team collaboration.

Quick Start

Describe the blocker and the goal, then ask for a structured looper run to generate and evaluate alternate paths.

Frequently Asked Questions about looper

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

FAQPage Schema
How do I resolve blockers when progress stalls on a complex engineering task?

To resolve blockers on complex engineering tasks, document the failure context, analyze root causes, generate three viable alternatives, and iteratively attempt the next best approach until resolved.

What is iterative problem solving for environment and integration issues?

Iterative problem solving for environment and integration issues involves documenting the blocker, analyzing root causes, comparing at least three alternative approaches, and switching execution paths until progress resumes.

How do I perform root-cause analysis when a software engineering task is blocked?

Perform root-cause analysis for blocked software engineering tasks by systematically recording what happened and why it stalled, then evaluating multiple alternative routes to identify the underlying issue.

Can I use structured blocker analysis for cross-team debugging workflows?

Yes, structured blocker analysis works with cross-team debugging workflows, planning sessions, and integration issues by preserving context and tracking outcomes across iterative attempts.

What's the best way to generate alternative approaches when a debug pattern fails?

The best way to generate alternative approaches when a debug pattern fails is to document the blocker, compare the feasibility of at least three viable options, and iteratively execute the next best choice.

Why does iterative problem solving require generating at least three alternatives?

Iterative problem solving requires generating at least three alternatives to ensure structured blocker analysis provides viable fallback routes, enabling systematic root-cause identification and iterative execution until resolution.