skills.rest
richardthe3rd
richardthe3rdCOMMUNITY
Explore all skills by this author →
GitHub

research-methodology

Validate root causes and plan fixes for the Cambridge Beer Festival Flutter app.

2|3|Updated Nov 28, 2025
Search Tags:#root cause analysis#ADR#issue triage#confirmation bias#idea lifecycle#resilience review#data census
One-click install
npx skills add https://github.com/richardthe3rd/cambridge-beer-festival-app --skill research-methodology-richardthe3rd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: research-methodology
Source: https://github.com/richardthe3rd/cambridge-beer-festival-app/tree/main/.claude/skills/research-methodology
Command: npx skills add https://github.com/richardthe3rd/cambridge-beer-festival-app --skill research-methodology-richardthe3rd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of unvalidated hunches leading to redundant fixes, re-litigated decisions, and unresolved edge cases in the Cambridge Beer Festival app, ensuring every proposed change is rigorously tested before shipping.

Core Features & Use Cases

  • Evidence Bar Enforcement: Requires root causes to explain all observed cases (including edge cases like empty state or festival switching) and survive adversarial refutation to avoid incomplete fixes.
  • Pre-Experiment Prediction: Mandates stating expected outcomes before running data censuses or code checks to eliminate confirmation bias.
  • Structured Idea Lifecycle: Guides ideas from initial hunch through planning docs, resilience reviews, ADRs, and archived retirement for rejected proposals to preserve institutional knowledge.
  • Use Case: When investigating a stale drink cache bug, use this Skill to validate your root cause covers all festival switching scenarios, predict census results before checking live data, and follow the repo's standard lifecycle to avoid redundant work.

Quick Start

Apply the research-methodology skill to validate your proposed root cause for the recent drink list loading issue, ensuring it explains all observed edge cases before you draft a fix.

Frequently Asked Questions about research-methodology

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

FAQPage Schema
How do I validate a root cause analysis to ensure it covers all edge cases?▼

To validate root cause analysis, enforce an evidence bar requiring the proposed cause to explain all observed cases, including empty states or festival switching, and survive adversarial refutation before drafting a fix.

How do I prevent confirmation bias when running a live data census?▼

Prevent confirmation bias during a data census by mandating pre-experiment prediction, which requires stating expected outcomes before checking live data or running code checks.

What is the structured idea lifecycle for issue triage and planning documents?▼

The structured idea lifecycle guides proposed fixes from initial hunch through planning documents, resilience reviews, ADR decisions, and archived retirement for rejected proposals to preserve institutional knowledge and prevent re-litigation.

Does this research methodology work for Flutter app issue triage and resilience reviews?▼

Yes, this methodology applies to Flutter app issue triage and resilience reviews, enforcing rigorous validation to transform unvalidated hunches into accepted, production-ready fixes while preventing redundant work.

Why should I document the retirement of rejected ideas during issue triage?▼

Documenting the retirement of rejected ideas prevents redundant work and re-litigated decisions by preserving institutional knowledge, ensuring rejected proposals are archived rather than reconsidered.

What is the best way to draft an ADR for a production-ready app fix?▼

Drafting an ADR for a production-ready fix requires following a structured idea lifecycle, applying evidence bars, pre-experiment prediction, and cheap reversible experiment mechanisms to ensure the decision is rigorously tested.

Related Skills

Explore More Software Engineering Skills→
cc01cccc01cc
4

bug-root-cause-structurer

Produces structured bug root-cause analyses with actionable repair plans and verification steps.

Community
Advanced
cescraflicescrafli

architecture-decision-records

Capture architectural decisions as structured ADR documents with context and alternatives.

Community
Advanced
cdalsoniiicdalsoniii

Chaos Engineering

Designs and executes controlled failure experiments to validate system resilience via fault injection scenarios.

Community
Advanced
richardthe3rdrichardthe3rd
2

failure-archaeology

Record past investigation outcomes to prevent re-proposing rejected fixes.

Community
Advanced