ds-lite-iterate

Executes one bounded research iteration with receipts, graph updates, and a terminal report.

2|Updated Jun 18, 2026
One-click install
npx skills add https://github.com/AlexenderSokolov/deepscientist-lite-codex-plugin --skill ds-lite-iterate-alexendersokolov
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ds-lite-iterate
Source: https://github.com/AlexenderSokolov/deepscientist-lite-codex-plugin/tree/main/plugins/deepscientist-lite-core/skills/ds-lite-iterate
Command: npx skills add https://github.com/AlexenderSokolov/deepscientist-lite-codex-plugin --skill ds-lite-iterate-alexendersokolov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long research sessions lose context across threads: goals, routes, experiment evidence, and review results disappear, making it impossible to resume work safely. This Skill runs exactly one visible, auditable worker iteration so progress is recorded and the next session can pick up where things stopped. ## Core Features & Use Cases - Bounded single-iteration execution: Chooses exactly one action (scout, idea, execute, debug, review, analysis, write, branch, rollback, stop, ask-human, or status-check) with a stated prediction, falsification condition, budget, and stop condition. - Receipt-based state management: Registers, finalizes, and verifies iterations via ds_lite_iteration.py, updates the research graph through ds_lite_state.py with expected revisions, and renders STATUS.md. - Evidence and safety gates: Enforces Evidence Pack and review requirements before analysis, preserves negative results, and blocks unauthorized GPU, long-run, or external-data actions. - Use Case: Resuming a multi-day ML experiment project, the worker reads the mission board, finds a blocked training run, performs one status check with evidence backup, records a frontier decision, finalizes a terminal receipt, and hands off the next single action. ## Quick Start Ask the agent to read the mission board, choose one bounded next action, record the frontier decision, update STATUS, and stop.

Frequently Asked Questions about ds-lite-iterate

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

FAQPage Schema
How do I resume a research project across multiple sessions?▼

Run one iteration that reads PROJECT.md, STATUS.md, the mission board, and the research graph, then chooses a single bounded action. It records a frontier decision and terminal receipt so the next session can continue from verified state.

How does the iteration skill prevent uncontrolled autonomous loops?▼

One invocation equals one iteration with a mandatory stop after reflection and reporting. Only an external approved controller may schedule a later iteration after the prior terminal receipt is verified; the skill itself never loops.

What happens when experiment evidence is missing or a gate is not verified?▼

Missing evidence is recorded as blocked or not-verified rather than polished success prose. Without an Evidence Pack and passing review, the worker must choose debug, review, ask-human, or stop instead of analysis or writing.

Can the worker start GPU jobs or long-running external tasks on its own?▼

No. GPU runs, long runs, dependency installs, cluster jobs, and external data access require user or supervisor approval unless a project budget policy already authorizes them. Only the plan's single launch authority may claim slots and start pane workloads.

How are negative results and failed experiments handled?▼

Negative results are preserved in the research graph using rollback, branch, or supersedes edges. Old nodes are never deleted to make the route look clean, and metric direction errors are recorded as protocol-breaking corrections.