learning-refresh

Refresh and maintain 'docs/solutions' entries in ADLC based on review outcomes.

2|1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/bigeasyfreeman/adlc --skill learning-refresh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: learning-refresh
Source: https://github.com/bigeasyfreeman/adlc/tree/main/skills/learning-refresh
Command: npx skills add https://github.com/bigeasyfreeman/adlc --skill learning-refresh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the refresh and maintenance of 'docs/solutions' entries, ensuring they remain accurate and useful without overburdening ADLC runs.

Core Features & Use Cases

  • Scoped Maintenance: Refresh only the necessary entries based on specific triggers like stale signals or user requests.
  • Trigger Conditions: Responds to stale conditions, user refresh requests, refactor impacts, and learning capture overlaps.
  • Outcomes: Provides options to keep, update, consolidate, replace, or delete entries based on review.
  • Process: Inventory scoped entries, verify evidence, update content, validate changes, and emit a refresh report.

Quick Start

Run the learning-refresh skill with a specific scope to refresh 'docs/solutions' entries.

Frequently Asked Questions about learning-refresh

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

FAQPage Schema
How do I refresh stale documentation entries without triggering a full ADLC run?

Scoped maintenance of docs/solutions entries allows you to refresh only necessary items based on specific triggers like stale signals, preventing overburdened ADLC runs.

What triggers a solution management documentation update?

Documentation updates are triggered by stale conditions, user refresh requests, refactor impacts, and learning capture overlaps within the ADLC framework.

How do I consolidate or delete redundant docs/solutions entries?

You can inventory scoped entries, verify evidence, and review outcomes to keep, update, consolidate, replace, or delete redundant docs/solutions entries efficiently.

What is the best way to maintain ADLC documentation accuracy after refactoring?

The best way to maintain ADLC documentation accuracy is using scoped maintenance triggered by refactor impacts to inventory, verify, and update affected docs/solutions entries.

Can I refresh specific documentation sections instead of the entire solution?

Yes, you can scope maintenance to refresh only necessary entries based on specific triggers, allowing targeted updates without processing the entire solution documentation.

What happens after a docs/solutions entry is reviewed and updated?

After reviewing and updating docs/solutions entries, the process validates changes and emits a refresh report documenting the maintenance outcomes and updated content.