sparring

Examine plans and decisions to expose assumptions and test evidence.

10|5|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/JHostalek/dotclaude --skill sparring-jhostalek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sparring
Source: https://github.com/JHostalek/dotclaude/tree/main/skills/sparring
Command: npx skills add https://github.com/JHostalek/dotclaude --skill sparring-jhostalek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents premature decisions by systematically examining plans, beliefs, requirements, and problems before action, exposing hidden assumptions, weak evidence, contradictions, and unresolved uncertainty.

Core Features & Use Cases

  • Socratic Inquiry: Lead a cooperative, question-driven examination without steering the user toward a preferred conclusion.
  • Claim and Evidence Tracking: Track prerequisites, evidence, confidence, dependencies, falsifiers, and outcomes across open, provisional, settled, rejected, and uncertain claims.
  • Repository-Aware Analysis: Cross-check claims against code, documentation, context files, ADRs, authoritative sources, alternatives, and operational consequences.
  • Decision Documentation: Update context language and propose ADRs when conclusions are durable, surprising, and based on meaningful trade-offs.
  • Use Case: Before implementing a major architectural change, use this Skill to clarify goals and constraints, test competing approaches, identify edge cases, and produce a shared understanding of the selected direction and remaining uncertainty.

Quick Start

Use the sparring skill to examine whether the proposed migration plan is justified, identify its assumptions and alternatives, and document the conclusions before implementation.

Frequently Asked Questions about sparring

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

FAQPage Schema
How do I challenge assumptions before committing to an architecture decision?

Before an architecture review, use Socratic inquiry to expose hidden assumptions, test evidence, and resolve uncertainty. This process tracks claim states and cross-checks prerequisites against repository context and authoritative sources before action.

What is assumption testing in software engineering decision analysis?

Assumption testing in decision analysis is a Socratic inquiry process that examines plans and beliefs to expose weak evidence and contradictions. It tracks prerequisites, confidence levels, and dependencies across open, provisional, settled, rejected, and uncertain claim states.

How do I clarify requirements and test competing implementation plans?

To clarify requirements and test competing implementation plans, conduct a cooperative question-driven examination of goals and constraints. This identifies edge cases, tracks falsifiers, and produces a shared understanding of the selected direction and remaining bounded uncertainty.

When do I need ADR documentation for architectural decisions?

You need ADR documentation when architectural decisions are durable, surprising, and based on meaningful trade-offs. This Skill proposes ADRs to record settled conclusions after examining alternatives and resolving uncertainty during the decision analysis process.

What are the limitations of Socratic inquiry for repository changes?

The limitation of Socratic inquiry for repository changes is that conclusions remain bounded by uncertainty if evidence is weak or contradictory. It requires tracking open and provisional claims until falsifiers are identified and outcomes are settled or rejected.