debate

Evaluates work plans, design changes, and bug fixes for implementation challenges.

1|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/bildzeitung/lode --skill debate-bildzeitung
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debate
Source: https://github.com/bildzeitung/lode/tree/main/.claude/skills/debate
Command: npx skills add https://github.com/bildzeitung/lode --skill debate-bildzeitung

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you stress-test your plans, design changes, and work items to uncover potential issues before they become problems.

Core Features & Use Cases

  • Stress Test Work Plans: Analyze the feasibility of a work plan by identifying sequencing gaps, hidden assumptions, and risky approaches.
  • Assess Bug-Fix Approaches: Evaluate bug fixes to ensure they address the root cause and won't introduce new issues.
  • Review Design Proposals: Scrutinize proposed design changes for consistency and practicality before they are implemented.

Quick Start

Run the 'debate' skill to analyze a plan or proposal, e.g., 'debate this feature request'.

Frequently Asked Questions about debate

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

FAQPage Schema
How do I stress test a work plan for implementation pitfalls?

To review a design change, you scrutinize the proposed design for consistency and practicality before it is implemented. This design review process evaluates proposed changes to prevent future implementation challenges.

How do I evaluate bug fixes to ensure they address the root cause?

You evaluate bug fixes by analyzing the proposed approach to ensure it addresses the root cause and will not introduce new issues. This assessment verifies the acceptability and sequencing of your bug fixes.

Can I use this to review a project management plan without external dependencies?

Yes, you can review a project management plan without external dependencies. The analysis operates independently, focusing entirely on in-depth review of the content presented to uncover ambiguity and assumptions.

What is the best way to uncover hidden assumptions in a software development plan?

The best way to uncover hidden assumptions is by pushing back on the plan to evaluate its ambiguity, sequencing, and acceptability. This reveals risky approaches and implementation challenges in your software development workflow.