freeshard-research-methodology

Standardize evidence-backed research and decision-making for Freeshard technical changes.

47|2|Updated Feb 11, 2025
One-click install
npx skills add https://github.com/FreeshardBase/freeshard --skill freeshard-research-methodology
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeshard-research-methodology
Source: https://github.com/FreeshardBase/freeshard/tree/main/.claude/skills/freeshard-research-methodology
Command: npx skills add https://github.com/FreeshardBase/freeshard --skill freeshard-research-methodology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured framework for the Freeshard project to transform hunches into verified results, preventing the loss of good ideas and ensuring that root-cause analyses are backed by evidence rather than assumptions.

Core Features & Use Cases

  • Evidence-Based Triage: Enforces strict rules for root-cause analysis, requiring that every observation—including negative results—is explained by a single mechanism.
  • Idea Lifecycle Management: Standardizes the progression of ideas from initial hunches to spikes, decisions, and final implementation, ensuring no work is orphaned.
  • Documented Retirement: Ensures that abandoned ideas are never closed silently, providing a clear paper trail of why a direction was rejected and what supersedes it.

Quick Start

Use the freeshard-research-methodology skill to evaluate if my current hypothesis for the recent system outage meets the project evidence bar.

Frequently Asked Questions about freeshard-research-methodology

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

FAQPage Schema
How do I standardize root-cause analysis to ensure findings are evidence-backed?

Standardize root-cause analysis by enforcing evidence-based triage rules that require every observation, including negative results, to be explained by a single mechanism. This prevents unverified assumptions from driving technical changes.

What is the best way to manage the lifecycle of a development task from a hunch to implementation?

Manage the development task lifecycle by standardizing the progression of ideas from initial hunches to spikes, decisions, and final implementation. This ensures no work is orphaned and maintains a clear paper trail.

How should I document the retirement of technical debt and abandoned ideas?

Document the retirement of technical debt by ensuring abandoned ideas are never closed silently. Provide a clear paper trail of why a direction was rejected and what specific solution supersedes it.

How do I evaluate if a feature proposal meets the evidence bar for a system outage hypothesis?

Evaluate a feature proposal or outage hypothesis by applying rigorous hypothesis testing and solution-neutral design briefs. This verifies if the root-cause analysis meets the project evidence bar before implementation.

Can I use this research methodology for evaluating technical changes outside of the Freeshard project?

The research methodology is designed for the Freeshard project and Shard Core ecosystem to ensure technical changes are evidence-backed. Its principles of hypothesis testing and documented retirement can apply to similar software engineering environments.

Why does my development process lose good ideas before they reach a final decision?

Development processes lose good ideas when hunches are not transformed into verified results through a structured framework. Enforcing idea lifecycle management standardizes progression from spikes to decisions, preventing orphaned work.