methodical

Enforce step-by-step execution with evidence receipts and explicit completeness statements.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/jacob-balslev/skill-graph --skill methodical
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: methodical
Source: https://github.com/jacob-balslev/skill-graph/tree/main/marketplace/skills/methodical
Command: npx skills add https://github.com/jacob-balslev/skill-graph --skill methodical

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Methodical execution prevents agents from silently skipping steps, filtering negative findings, and replacing complete reporting with summaries that hide omissions.

Core Features & Use Cases

  • Step-by-step completeness discipline: forces enumeration, counting, and step-level evidence receipts instead of end-only summaries.
  • Generation/criticism separation: runs a structured self-critique after generation to catch what was omitted or softened.
  • Anti-pattern detection for intellectual honesty: blocks common failure modes like summary-first fabrication, assumed verification, and “deferral as completion”.
  • Use cases: audits, diagnostic/health reports, verification of acceptance criteria, and creating task items from findings where completeness matters more than brevity.

Quick Start

Use the methodical skill when producing an audit report of your current workspace so every step includes observable evidence and the final output states an explicit completeness coverage claim.

Frequently Asked Questions about methodical

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

FAQPage Schema
How do I prevent AI from skipping evidence during an audit report?

To prevent AI from skipping evidence during an audit report, enforce step-by-step completeness discipline requiring explicit scope counting, step-level evidence receipts, and an explicit completeness statement rather than relying on end-only summaries.

Why does my AI agent replace complete findings with summaries that hide omissions?

AI agents replace complete findings with summaries that hide omissions due to common failure modes like summary-first fabrication and assumed verification. Applying anti-pattern detection for intellectual honesty blocks these silent scope reductions.

What is generation and criticism separation for agent reliability?

Generation and criticism separation for agent reliability is a structured self-critique process that runs after initial output generation to catch what was omitted or softened, ensuring intellectual honesty in completeness verification.

How do I verify acceptance criteria without assumed verification?

To verify acceptance criteria without assumed verification, apply methodical execution that requires observable evidence for each step, blocks deferral as completion, and mandates an explicit completeness statement naming covered items and exclusions.

When do I need step-level evidence receipts for diagnostic health checks?

You need step-level evidence receipts for diagnostic health checks when completeness and intellectual honesty are required over brevity, ensuring every step includes observable evidence instead of filtered or assumed verification.

Can I use intellectual honesty techniques for tasks where brevity matters more than completeness?

Intellectual honesty techniques are designed for audits, health checks, and verification against acceptance criteria where completeness matters more than brevity, making them unsuitable for tasks prioritizing concise summaries over exhaustive findings.