ds-decision

Records evidence-backed go, stop, branch, and finalize decisions for research quests.

1.1k|116|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/OpenLAIR/dr-claw --skill ds-decision
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ds-decision
Source: https://github.com/OpenLAIR/dr-claw/tree/main/skills/ds-decision
Command: npx skills add https://github.com/OpenLAIR/dr-claw --skill ds-decision

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Long-running research quests often stall or drift when the next step is unclear. This Skill enforces a disciplined decision process so every continuation, branch, baseline reuse, or stop is backed by durable evidence rather than momentum.

Core Features & Use Cases

  • Structured decision records: Captures verdict, action, reason, evidence paths, and next stage for every consequential choice using canonical actions like continue, branch, reuse_baseline, write, finalize, reset, and stop.
  • Candidate selection discipline: When choosing among idea branches, experiment packages, or paper outlines, it records selection criteria, the winner, and why alternatives were rejected.
  • User-gated and autonomous modes: Supports blocking decision requests when user preference matters, and autonomous routing when the runtime contract allows it.
  • Use Case: After an experiment run finishes with mixed results, use this Skill to weigh the evidence, decide whether to iterate, branch, or move to writing, and durably record the decision with its justification.

Quick Start

Ask the agent to evaluate the current experiment evidence and record a decision on whether to continue, branch, or stop the research line.

Frequently Asked Questions about ds-decision

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

FAQPage Schema
How do I decide whether to continue or stop a research experiment?

State the question explicitly, collect decision-relevant evidence such as run artifacts and baseline state, then choose a verdict (good, bad, neutral, blocked) mapped to an action like continue, iterate, or stop. Record the decision durably with reasons and evidence paths.

How to choose between multiple experiment or idea branches?

Compare candidates against explicit criteria such as evidence quality, feasibility, and expected information gain. Record the winner, the rejected alternatives, implementation priority, and what you expect to learn from the chosen package.

When should a decision request block on user input?

Block only when multiple options are plausible and the choice depends on user preference, cost, or scope, and the runtime decision policy is not autonomous. Otherwise decide from durable evidence, record the reasoning, and continue.

What evidence sources should research decisions rely on?

Decisions should rely on durable sources: recent run artifacts, report artifacts, baseline state, and quest documents. Memory serves only as supporting context, and major decisions should never be made from vibe or momentum.

When should baseline reuse be chosen over a new experiment?

Choose baseline reuse when blocked states or existing results make a new run redundant. The decision is complete only after the baseline is attached and confirmed, or an explicit blocker or waiver is recorded.