dev-docs-update

Update active task documentation before context reset.

70|28|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/AIBiz-Automatyzacje/claude-code-starter --skill dev-docs-update-aibiz-automatyzacje
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-docs-update
Source: https://github.com/AIBiz-Automatyzacje/claude-code-starter/tree/main/.claude/skills/dev-docs-update
Command: npx skills add https://github.com/AIBiz-Automatyzacje/claude-code-starter --skill dev-docs-update-aibiz-automatyzacje

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the update of technical documentation to ensure a seamless transition after resetting context, saving time and reducing manual effort.

Core Features & Use Cases

  • Documentation Update Automation: Automatically update active task documentation to reflect current status and decisions.
  • Session Context Preservation: Record session context, decisions, and unresolved issues for continuity.
  • Quick Start: Update documentation for the 'taskX' task before context reset by running dev-docs-update docs/active/taskX/.

Quick Start

Run the command dev-docs-update docs/active/taskX/ to update documentation for the 'taskX' task.

Frequently Asked Questions about dev-docs-update

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

FAQPage Schema
How do I update technical documentation before a context reset?

To update technical documentation before a context reset, run the command `dev-docs-update docs/active/taskX/` to automatically capture the current task status and ensure seamless continuation.

How does session continuity work for software development workflows?

Session continuity works by automatically recording session context, active decisions, and unresolved issues during software development workflows, which preserves the exact task state for seamless continuation later.

What is the best way to preserve active task decisions for later reference?

The best way to preserve active task decisions is to automate documentation updates, which records your session context and unresolved issues accurately before you lose your current working state.

Do I need to manually execute commands to preserve session context?

Yes, you need to manually execute the update command and perform file operations, as the automation requires user initiation to capture the current state of tasks and decisions.

Can I use this for unresolved issue tracking across multiple tasks?

Yes, you can use it for unresolved issue tracking by running the update command on specific task directories, ensuring that unresolved issues are recorded for each unique task context.