question-loop

Generate critical, contrarian, and steelman questions about repository design.

30|12|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/anthony-chaudhary/fak --skill question-loop
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: question-loop
Source: https://github.com/anthony-chaudhary/fak/tree/main/.claude/skills/question-loop
Command: npx skills add https://github.com/anthony-chaudhary/fak --skill question-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill addresses the tendency of agents to fall into echo chambers or solution-oriented bias by forcing a dedicated, detached process to generate honest, contrarian, and steelman questions about the repository's current direction.

Core Features & Use Cases

  • Detached Question Generation: Launches independent workers to append hard questions to a durable ledger without attempting to solve them.
  • Context Separation: Maintains strict separation between the questioning loop and the ticketing loop to prevent premature solution-seeking.
  • Use Case: Use this when you need to identify blind spots, challenge design assumptions, or uncover "elephants in the room" that are being ignored by standard issue-draining workflows.

Quick Start

Run the question loop to generate a batch of critical provocations regarding the current repository state.

Frequently Asked Questions about question-loop

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

FAQPage Schema
How do I generate critical questions to identify blind spots in my repository design?▼

A detached questioning loop prevents AI agents from falling into echo chambers or solution-oriented bias. It forces a dedicated process to generate honest, contrarian inquiries about repository strategy without attempting to immediately solve or ticket them.

How do I use a ledger to track critical thinking questions in an automated workflow?▼

To automate critical self-inquiry, launch independent workers that append hard questions to a durable ledger without attempting to fix them. This maintains strict separation between the questioning loop and the ticketing loop to prevent premature solution-seeking.

What is the best way to challenge design assumptions in an automated agent workflow?▼

The best way to challenge design assumptions is using a detached multi-agent loop system. It generates steelman questions about repository strategy while maintaining strict context separation from the ticketing loop to prevent premature solution-seeking.

Does this critical questioning agent modify code or access PII?▼

No, the detached questioning loop does not modify code or access PII. It adheres to strict safety boundaries by operating exclusively as a questioning mechanism that logs inquiries to a structured ledger without executing fixes.

When do I need a separate questioning loop versus a standard issue-draining workflow?▼

You need a separate questioning loop when standard issue-draining workflows ignore elephants in the room. It provides a dedicated, detached process to generate honest, contrarian questions about repository direction without prematurely seeking solutions.