ds-lite-intake

Initializes durable project goals, constraints, and handoff files for research sessions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Long research and engineering sessions lose context when chat history resets, leaving goals, constraints, and prior conclusions untraceable. This Skill converts a new, inherited, or recovered project into a durable, file-based project contract that any future session can read and continue from. ## Core Features & Use Cases - Project Initialization: Creates a ds-lite.work-unit.v1 planning unit via ds_lite_state.py init, plus PROJECT.md, STATUS.md, and RESEARCH_MAP.md files capturing goals, hypotheses, constraints, and acceptance criteria. - Intake Audit for Existing Projects: Preserves existing conclusions, flags stale or unsupported claims, and reconciles non-terminal external tasks (tmux plans, running jobs) before planning new work. - State Graph Management: Maintains research/state/graph.json as machine-readable state with revision-checked mutations and a human-readable Markdown projection. - Use Case: You inherit a half-finished ML experiment folder with scattered notes and a running tmux job. Run intake to audit existing artifacts, reconcile the external task state, and produce a Mission Board with the active node, blockers, and next action. ## Quick Start Ask the assistant to inspect this project folder and turn your research question into a structured project handoff with goals, constraints, and a first action.

Frequently Asked Questions about ds-lite-intake

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

FAQPage Schema
How do I start a research project so context survives across sessions?▼

Run the intake workflow to initialize a work-unit via ds_lite_state.py init, then fill PROJECT.md with goals, constraints, and acceptance criteria. STATUS.md and RESEARCH_MAP.md give future sessions a readable Mission Board and state map.

How do I take over an existing research project without losing prior conclusions?▼

Perform an intake audit: inspect README, notes, prior reports, and research/state/graph.json first, preserve existing conclusions, mark stale or unsupported claims, and create only the missing protocol files rather than overwriting user work.

Can intake recover interrupted tmux or external long-running tasks?▼

Yes. It inventories external-tmux-plan and external-task artifacts, records plan gates and allocated slots, and keeps non-terminal tasks in the handoff until their owner, logs, checkpoints, and evidence are reconciled.

What happens if the state script is unavailable during intake?▼

Continue with ordinary project files only, report graph synchronization as blocked, and never edit graph.json directly. On revision conflicts (exit code 4), reload state and reconcile instead of overwriting concurrent changes.

What are the limitations of a verified tmux capacity plan?▼

A verified plan proves only the recorded server fingerprint and probe scope. It does not prove a workload, CLI child worker, or provider conversation is still alive or resumable, so recovery evidence must be gathered separately.