ds-finalize

Consolidates final claims, limitations, and recommendations to close or pause research quests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Long-running research quests often end ambiguously, with unclear claim statuses, lost negative results, and no clean stopping point. This Skill turns a sprawling research graph into a durable closure state with explicit claim ledgers, limitations, and resume packets.

Core Features & Use Cases

  • Claim Ledger Construction: Classifies every major outcome as supported, partially supported, unsupported, or deferred, with evidence paths and caveats.
  • Closure Decision Recording: Produces a final recommendation (stop, archive, publish, or continue later) with explicit reasoning and reopen conditions.
  • Resume Packet Generation: Builds compact handoff packets capturing the accepted baseline, strongest evidence, blockers, and do-not-repeat notes for future continuation.
  • Use Case: After weeks of experiments and paper drafting, a researcher asks the agent to wrap up. The Skill refreshes SUMMARY.md and status.md, verifies the paper bundle manifest, records a final decision artifact, and leaves a resume packet so the quest can be cleanly archived or resumed later.

Quick Start

Finalize the current research quest by consolidating all evidence, claims, and limitations into a final report with a clear stop-or-continue recommendation.

Frequently Asked Questions about ds-finalize

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

FAQPage Schema
How do I properly close a long-running research quest?

Use the finalize stage to consolidate accepted evidence, build a claim ledger classifying each outcome as supported or partial, record limitations, and produce an explicit stop, archive, publish, or continue-later recommendation with reopen conditions.

What should a research finalization report include?

A strong final report includes the executive state, strongest supported findings, negative results worth preserving, limitations, package or bundle inventory, a clear recommendation, and explicit reopen conditions for future work.

When should I not finalize a research quest?

Do not finalize when major evidence gaps remain unresolved, required outline items are unfinished, completed analysis is unmapped into the paper contract, or the quest is still in exploratory ideation. Route back through the decision stage instead.

How do I create a handoff packet for pausing a research project?

Build a resume packet covering the current state, accepted baseline, strongest evidence with artifact paths, open blockers, the single best next action, and do-not-repeat notes about failed branches and misleading metrics.

What happens if finalization is premature?

Premature finalization is recorded explicitly with blocked states such as unresolved major claims, missing proofing checks, or stale summaries. The quest routes back to the appropriate stage through the decision flow rather than forcing closure.