update-dev-docs

Sync development documentation with current TodoWrite state and implementation progress.

77|4|Updated Jun 20, 2022
One-click install
npx skills add https://github.com/htlin222/dotfiles --skill update-dev-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-dev-docs
Source: https://github.com/htlin222/dotfiles/tree/main/claude.symlink/skills/update-dev-docs
Command: npx skills add https://github.com/htlin222/dotfiles --skill update-dev-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that your development progress and key decisions are systematically documented before they are potentially lost during session compaction or when switching tasks.

Core Features & Use Cases

  • Progress Capture: Automatically updates documentation files (tasks.md, context.md, plan.md) with current implementation status.
  • Context Preservation: Records newly discovered files, decisions, code patterns, and lessons learned.
  • Use Case: Before using the /compact command to shorten your AI's memory, you can run /update-dev-docs to ensure all your recent work and insights are saved into your project's documentation.

Quick Start

Run the update-dev-docs skill, optionally providing a task name to focus the update.

Frequently Asked Questions about update-dev-docs

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

FAQPage Schema
How do I preserve development context before session compaction?

To preserve development context before session compaction, update your documentation files by syncing with the current TodoWrite state. This captures active task statuses, new files, and decisions into markdown records, ensuring no implementation progress is lost when the AI memory is shortened.

What is the best way to track implementation progress when switching tasks?

Tracking implementation progress when switching tasks requires syncing your current TodoWrite state with project documentation. This automatically updates `tasks.md`, `context.md`, and `plan.md` with newly discovered files, code patterns, and lessons learned to maintain context preservation.

How does syncing with TodoWrite state update code documentation?

Syncing with the TodoWrite state updates code documentation by identifying active tasks and generating a session summary. It systematically records implementation progress, newly discovered files, and recent decisions directly into markdown files before memory is cleared.

Do I need to manually edit tasks.md before running a session summary capture?

You do not need to manually edit tasks.md before capturing a session summary. The process automatically updates documentation files by syncing with active task statuses, recording new files, and documenting decisions without requiring manual markdown interventions.

Can I focus a documentation update on a specific task name?

You can focus a documentation update on a specific task name by providing it as an optional parameter when running the skill. This narrows the context preservation and progress tracking to sync only relevant implementation details for that particular task.