Dev Docs Update

Update context and task documents before context compaction.

3|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/joshka0/foxctl --skill dev-docs-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Dev Docs Update
Source: https://github.com/joshka0/foxctl/tree/main/configs/skills-condensed/dev-docs-update
Command: npx skills add https://github.com/joshka0/foxctl --skill dev-docs-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents important development decisions and status from getting lost when context is reset, so you can recover quickly without rereading everything from scratch.

Core Features & Use Cases

  • Pre-compaction documentation updates: Keeps active task files current by updating context and task tracking documents.
  • Session knowledge capture: Records what was solved, what was decided, which bugs were fixed, and which optimizations were made.
  • Memory and handoff readiness: Captures new patterns, entities/relationships, observations, and unfinished work, plus handoff notes with actionable file/line and command details.

Quick Start

Run Dev Docs Update for the current repository focus before compaction to ensure your next session has the latest task, memory, and handoff information.

Frequently Asked Questions about Dev Docs Update

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

FAQPage Schema
How do I preserve engineering context before session memory gets compacted?

To preserve engineering context before session memory gets compacted, update your development documentation to capture active task states, debugging outcomes, and unfinished feature handoffs in context and task tracking files.

What is the best way to track unfinished development tasks across multiple coding sessions?

Tracking unfinished development tasks across multiple coding sessions requires refreshing task-state tracking documents and capturing precise handoff notes with actionable file, line, and command details for fast rediscovery.

How do I document solved bugs and decisions so I don't lose them when context resets?

Documenting solved bugs and decisions when context resets involves recording what was solved, what was decided, and which optimizations were made directly into your active context markdown files.

Can I use session handoff notes to recover project status without rereading everything?

Session handoff notes allow you to recover project status without rereading everything by capturing new patterns, entity relationships, observations, and unfinished work with specific file and command references for quick rediscovery.

When should I update dev docs to prevent losing active task context?

You should update dev docs to prevent losing active task context right before context compaction occurs, ensuring your next coding session has the latest task, memory, and handoff information available.

What files need to be refreshed to maintain engineering workflow memory during development?

Maintaining engineering workflow memory requires refreshing active context markdown files and task tracking documents, specifically identifying and updating artifacts within your active development directory.