gpd-branch-hypothesis

Create a hypothesis branch with HYPOTHESIS.md and log decisions in the GPD state store.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/MichaelsEngineering/get-physics-done-test --skill gpd-branch-hypothesis-michaelsengineering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gpd-branch-hypothesis
Source: https://github.com/MichaelsEngineering/get-physics-done-test/tree/main/.agents/skills/gpd-branch-hypothesis
Command: npx skills add https://github.com/MichaelsEngineering/get-physics-done-test --skill gpd-branch-hypothesis-michaelsengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create isolated hypothesis branches to enable parallel exploration of alternative approaches while preserving the main research state.

Core Features & Use Cases

  • Isolated branching: fork the current STATE/ROADMAP into a dedicated hypothesis branch with its own STATE.md and HYPOTHESIS.md for side-by-side comparison.
  • Documentation and tracing: automatically generate a structured HYPOTHESIS.md and log the decision in the GPD state store for reproducibility.
  • Safe collaboration: stash and manage branches, keep the main lineage pristine while researchers test different algorithms or parameterizations.

Quick Start

Run the branch-hypothesis command with a concise description of the alternative approach to generate a slug, create the branch, fork state, and scaffold documentation

Frequently Asked Questions about gpd-branch-hypothesis

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

FAQPage Schema
How do I create isolated git branches to compare alternative research approaches?

Creating isolated git branches to compare alternative research approaches involves forking your current state into a dedicated hypothesis branch with its own HYPOTHESIS.md, preserving the main lineage while you explore different derivations side-by-side.

What is the best way to explore multiple physics derivations without contaminating the main research state?

Exploring multiple physics derivations without contaminating the main research state requires creating a dedicated hypothesis branch under hypothesis/, which isolates changes and keeps your primary STATE.md and ROADMAP.md pristine for reproducibility.

Can I scaffold a structured HYPOTHESIS.md automatically when branching a new research hypothesis?

Yes, you can scaffold a structured HYPOTHESIS.md automatically when branching a new research hypothesis, as the process generates AI-drafted sections and records the decision in the GPD state store for full traceability.

How do I manage parallel algorithm investigations while keeping a clean git state?

Managing parallel algorithm investigations while keeping a clean git state requires strict checks before branching, ensuring the working directory is clean before creating isolated hypothesis branches to test different parameterizations.

Does branching a hypothesis alter the primary STATE.md and ROADMAP.md files?

No, branching a hypothesis does not alter the primary STATE.md and ROADMAP.md files; it forks these files into an isolated branch, keeping the main research lineage safe from untested alternative approaches.

When should I use dedicated hypothesis branches in my research workflow?

You should use dedicated hypothesis branches when you need to concurrently explore multiple algorithms or derivations, allowing side-by-side comparison and safe collaboration without risking the integrity of your primary research state.