From scientific-method
Deepen a hypothesis with targeted literature research. Use whenever a hypothesis file needs supporting evidence, counterexamples, or a sharpened claim — including after generating-hypotheses or when a user asks to refine, strengthen, or research a specific hypothesis.
npx claudepluginhub pipemind-com/pipemind-marketplace --plugin scientific-methodThis skill is limited to using the following tools:
Takes a hypothesis stub and expands it through targeted literature research. Searches for supporting evidence, counterexamples, and related work, then sharpens the hypothesis into a precise, research-grounded claim ready for experimentation.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Takes a hypothesis stub and expands it through targeted literature research. Searches for supporting evidence, counterexamples, and related work, then sharpens the hypothesis into a precise, research-grounded claim ready for experimentation.
The orchestrator runs this skill in parallel across all hypotheses in the current iteration. Each invocation is independent and works on a single hypothesis file.
hypothesis-NN.mdRead the hypothesis file. If it already contains a ## Literature section, this hypothesis has already been refined -- report "Already refined: " and stop. The file itself is the checkpoint, so re-running is safe.
Identify the problem directory from the file path (its parent directory). Read problem.md to understand the broader research context. Read references.md if it exists to know which sources are already in the bibliography -- this prevents the literature agents from re-searching known material.
Derive 3 targeted search queries from the hypothesis statement and rationale. Each query targets a different angle because a single search would only surface one facet of the literature:
Spawn 3 Task agents in a single response (one per query). Each Task runs /researching-literature targeting the problem directory.
Task prompt format for each:
Run /researching-literature with:
- Topic: "<search query>"
- Problem directory: "<absolute path to problem directory>"
Wait for all three to complete. Then read the updated references.md to identify which new REF IDs were added. Note the relevant ones for this hypothesis.
Read the updated references.md. Assess coverage along two dimensions:
Run one full /researching-literature invocation to fill gaps. Always run this step — the three parallel searches in Step 2 are targeted and narrow; this invocation provides broad dual-track coverage.
Task prompt format:
Run /researching-literature with:
- Topic: "<broader query derived from the hypothesis topic, not the specific claim>"
- Problem directory: "<absolute path to problem directory>"
Wait for the invocation to complete, then read references.md again to identify additional REF IDs added.
With the literature findings in hand, assess the hypothesis through these lenses:
Append to the hypothesis file after the existing content. Preserve the original ## Statement and ## Rationale sections unchanged -- they serve as a historical record of the initial thinking.
Use Edit to append the following sections:
Literature section:
## Literature
Relevant sources: REF-NNN, REF-NNN, ...
### Supporting evidence
- <finding> (REF-NNN)
- <finding> (REF-NNN)
### Challenges and counterexamples
- <finding that complicates or contradicts this hypothesis> (REF-NNN)
Refined statement section:
## Refined Statement
<Updated hypothesis if the original needed adjustment. If unchanged, write "Unchanged -- original statement holds.">
If the hypothesis is already resolved by literature (definitively confirmed or refuted by prior work), add a note explaining this and update ## Status from pending to confirmed or refuted accordingly. Use Edit to change the status line.