dev-docs-workflow

Maintains three-file task documentation (plan.md, context.md, tasks.md) for Claude Code sessions.

Updated Dec 13, 2025
One-click install
npx skills add https://github.com/imehr/vet --skill dev-docs-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-docs-workflow
Source: https://github.com/imehr/vet/tree/main/.claude/skills/dev-docs-workflow
Command: npx skills add https://github.com/imehr/vet --skill dev-docs-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill preserves context across long Claude Code sessions by maintaining a persistent three-file documentation workflow that tracks decisions, context, and tasks for each feature or task.

Core Features & Use Cases

  • Three-file task docs: plan.md, context.md, and tasks.md capture strategy, key choices, and progress in one place.
  • Session continuity: enables seamless resumption of work after interruptions, reducing cognitive load.
  • Collaboration-ready: provides a clear record for reviews, handoffs, and audits of decisions and tasks.

Quick Start

Initialize a new task's dev docs using the skill to set up the three-file structure and start recording planning, context, and tasks for your feature.

Frequently Asked Questions about dev-docs-workflow

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

FAQPage Schema
How do I preserve context across Claude Code sessions?

You can preserve context across Claude Code sessions by maintaining a persistent three-file documentation structure with plan.md, context.md, and tasks.md to track decisions and progress for seamless resumption.

What is the best way to track development tasks and decisions for ongoing feature work?

The best way to track development tasks and decisions is using a three-file task documentation workflow that organizes strategy into plan.md, key choices into context.md, and progress into tasks.md for ongoing feature development.

How do I set up dev docs to resume work after a session interruption?

Set up dev docs by initializing a three-file structure containing plan.md, context.md, and tasks.md, then record planning, context, and tasks to enable seamless work resumption after session interruptions.

Does this task documentation workflow work for multi-session experiments?

Yes, this task documentation workflow is explicitly designed for multi-session experiments and ongoing feature development, enabling seamless planning, context capture, and task tracking across long Claude Code sessions.

Why do I lose context when resuming Claude Code sessions and how do I prevent it?

You lose context because session data is volatile; prevent it by maintaining a persistent three-file documentation workflow that captures decisions, context, and tasks in plan.md, context.md, and tasks.md files.

Can I use this documentation workflow for code reviews and handoffs?

Yes, this documentation workflow is collaboration-ready and provides a clear record of decisions and tasks for reviews, handoffs, and audits during ongoing feature development.