# Durable Work

> Carry a large job through planning, specialists, coding tools, background topics and durable Tasks without losing decisions or claiming unfinished work is done. Use for long implementation, multi-stage research and work continued across chats.

- Skill: `vstorm-co/durable-work` (Agent Skill)
- Install (CLI): `npx get-skill add vstorm-co/durable-work`
- Raw SKILL.md: https://api.skillmd.com/api/skills/vstorm-co/durable-work/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Research & Search
- Author: vstorm-co (https://skillmd.com/u/vstorm-co)
- Updated: 2026-11-12
- Page: https://skillmd.com/skills/vstorm-co/durable-work

---


# Carry substantial work through to evidence

Use for a long, multi-stage job or a handoff across runs. Routine operations need their current tool contracts, not this skill.

State the deliverable and keep a short plan when it helps. Inspect existing sources, decisions and work before starting another copy. Continue authorized work through implementation and verification; dispatch is an intermediate state.

Choose the lifetime deliberately. A specialist or background tool works inside the current run. A background topic lets independent work continue while the person chats. A durable Task keeps a commitment, owner and next action across runs. A routine owns recurrence. Do not promise future work without saving the mechanism that will actually perform it.

Delegate independent research, exploration and review with a bounded question, relevant context, allowed changes and acceptance criteria. Keep dependent writes ordered, avoid overlapping edits and circular delegation, and collect evidence before using a result. Dynamic specialists do not automatically inherit every tool, private source or credential.

For coding, provide the repository/folder, goal, constraints and checks. Use only the configured execution environment and the initiating person's authorized account. Inspect changes and test evidence before integrating them; follow the person's branch and publication instructions.

Keep durable decisions in project material, preferences in appropriately scoped Memory and unfinished commitments in Tasks. A handoff records completed results, links, checks, blockers and the next owner; it does not copy the whole transcript into Context. Ask only for consequential missing choices and continue independent work. End with the usable result and honest limits.

