skills.rest
pr-pm
pr-pmOFFICIAL
Explore all skills by this author →
GitHub

thoroughness

Enforce a three-phase workflow of analysis, implementation, and verification for complex tasks.

121|16|Updated Oct 10, 2025
Search Tags:#quality assurance#code review#debugging#methodology#problem solving#software development#completeness
One-click install
npx skills add https://github.com/pr-pm/prpm --skill thoroughness
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: thoroughness
Source: https://github.com/pr-pm/prpm/tree/main/.claude/skills/thoroughness
Command: npx skills add https://github.com/pr-pm/prpm --skill thoroughness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents shortcuts and incomplete work on critical tasks, ensuring comprehensive analysis, systematic implementation, and rigorous verification for high-quality outcomes. It helps you avoid recurring issues by focusing on root causes, not just symptoms.

Core Features & Use Cases

  • Systematic Problem Solving: Guides you through distinct phases of comprehensive analysis, systematic implementation, and thorough verification for any complex task.
  • Root Cause Focus: Emphasizes finding and fixing the underlying root causes of problems rather than merely addressing symptoms, preventing future recurrences.
  • Quality Checkpoints: Provides a clear checklist to ensure every fix is verified, potential side effects are considered, and all relevant documentation is updated.
  • Use Case: When debugging a critical production bug, this skill ensures you don't just patch the symptom but systematically identify the root cause, test the fix rigorously, and verify no new issues are introduced, saving significant future debugging time and stress.

Quick Start

Good Approach (Thoroughness-Driven)

  1. List all 24 errors systematically
  2. Group by error type
  3. Find root causes
  4. Fix by category
  5. Test after each category
  6. Run full test suite
  7. Document what was learned

Frequently Asked Questions about thoroughness

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

FAQPage Schema
How do I systematically debug complex issues instead of just patching symptoms?▼

Systematic debugging addresses root causes through three phases: comprehensive analysis to understand the full problem scope, systematic implementation to fix underlying issues, and rigorous verification to ensure no side effects. This prevents recurring problems and saves future debugging time.

What's the best way to handle multi-step feature development to ensure nothing is missed?▼

Break development into distinct phases: analyze dependencies and requirements thoroughly, implement changes atomically with clear planning, then verify through testing and documentation. This structured approach catches incomplete work and prevents integration failures.

How do I verify a production deployment is truly complete and correct?▼

Comprehensive verification requires testing after each change category, running the full test suite, checking for side effects, and documenting outcomes. This three-phase workflow ensures deployments are correct before going live.

When should I prioritize thoroughness over speed in software development?▼

Prioritize thoroughness for critical tasks like production deployments, complex refactoring, and high-stakes debugging where correctness is essential. Skipping verification phases on these tasks creates technical debt and future incidents.

Can code review catch incomplete implementations before they cause problems?▼

Code review combined with systematic analysis and verification prevents incomplete work. By enforcing root-cause analysis, detailed planning, and rigorous testing, you avoid shipping flawed implementations that create downstream issues.

How do I document lessons learned from solving complex problems?▼

Document what was discovered during comprehensive analysis, how root causes were fixed, and verification results. This documentation prevents recurring issues and helps teammates understand problem-solving decisions.

Related Skills

Explore More Software Engineering Skills→
brandonburrusbrandonburrus
1

feature-spec

Generates structured PRDs with goals, user stories, requirements, and metrics.

Community
Advanced
DojoGenesisDojoGenesis
2

debugging

Generate markdown debug reports documenting root cause, fix, and lessons learned.

Community
Intermediate
BurburtonBurburton

bugfix-workflow

Guide developers through end-to-end bugfix workflows from discovery to verification.

Community
Advanced
mcevoyinitmcevoyinit

speedrun

Automate rapid code construction with minimal planning and enforced security rules.

Community
Intermediate