dev-docs-complete

Archive completed tasks and extract insights from project context files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill simplifies the process of task completion by archiving finished projects and extracting critical insights, reducing time spent on documentation and ensuring knowledge retention.

Core Features & Use Cases

  • Task Archiving: Automates the transfer of completed tasks from active to completed project documentation.
  • Insight Extraction: Summarizes key decisions, patterns, and issues from project context files.
  • Documentation Update: Facilitates the update of project documentation with relevant decisions and patterns.

Quick Start

To archive a completed task, run the skill with the task name, e.g., /dev-docs-complete "task-name".

Frequently Asked Questions about dev-docs-complete

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

FAQPage Schema
How do I automate task completion and project archiving?

Automate task completion by running the skill with a task name to transfer completed tasks from active to completed project documentation, extracting insights and updating documentation automatically.

What is the best way to extract insights from completed project documentation?

Extract insights from completed project documentation by archiving finished tasks, which summarizes key decisions, patterns, and issues from project context files into a consolidated knowledge base.

How does documentation update work when archiving finished projects?

Documentation updates work by archiving finished projects, extracting critical insights to reduce time spent on manual documentation, and ensuring knowledge retention through automated updates.

Are there limitations when using YAML and Markdown for project archiving?

The skill is limited to utilizing YAML for project structure and Markdown for documentation formatting, meaning it requires your project context to be compatible with these specific file formats for successful archiving.