consolidate-task

Consolidate completed task work into architecture decision records.

77|11|Updated Dec 26, 2025
One-click install
npx skills add https://github.com/mcouthon/agents --skill consolidate-task
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: consolidate-task
Source: https://github.com/mcouthon/agents/tree/main/.github/skills/consolidate-task
Command: npx skills add https://github.com/mcouthon/agents --skill consolidate-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates completed task work into architectural decision records to reduce clutter in the .tasks directory and preserve decisions for future reference.

Core Features & Use Cases

  • ADR creation: Generate a new ADR when a task introduces a significant architectural decision.
  • ADR updates: Update the ADRs table and architecture README when existing decisions evolve.
  • Audit trail: Maintain a chronological record of decisions linked to completed tasks.

Quick Start

Read the task file at .tasks/{task-folder}/task.md and create a new architecture decision record under .tasks/architecture/ADR-NNN-{decision-name}.md.

Frequently Asked Questions about consolidate-task

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

FAQPage Schema
How do I convert completed tasks into architecture decision records?

To convert completed tasks into architecture decision records, the Skill reads a task file from the .tasks directory, generates a new ADR, and saves it under .tasks/architecture/ADR-NNN-{decision-name}.md.

What is the best way to organize architecture decision records in a task management workflow?

Organizing architecture decision records involves scanning the .tasks/architecture directory for existing files, assigning the next available ADR-NNN number, and updating the relevant ADRs table and architecture README.

When should I create an ADR for a completed development task?

You should create an ADR when a completed task introduces architectural changes or clarifies decisions, such as adding new patterns, modifying existing components, or updating conventions across typical development tasks.

How does generating architecture decision records reduce clutter in the .tasks directory?

Generating architecture decision records reduces clutter by consolidating completed task work into permanent ADR files, preserving decisions for future reference while removing resolved task entries from the active .tasks directory.

Can I update existing ADRs when architectural decisions evolve?

Yes, when existing decisions evolve, the Skill updates the ADRs table and architecture README to maintain a chronological audit trail of decisions linked to completed tasks.

Do I need a specific folder structure to consolidate tasks into architecture records?

You need a .tasks directory containing task folders with task.md files and an .tasks/architecture subdirectory for storing the generated ADR-NNN-{decision-name}.md files and the architecture README.