agent-learn

Capture project learnings into PROJECT.md, ADRs, and tech spec retrospectives.

8|13|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/queen-of-code/AI-DLC --skill agent-learn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-learn
Source: https://github.com/queen-of-code/AI-DLC/tree/main/plugins/ai-dlc-skills/skills/agents/agent-learn
Command: npx skills add https://github.com/queen-of-code/AI-DLC --skill agent-learn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Learn agent ensures that insights, decisions, and retrospective notes from completed features or incidents are captured as durable, agent-readable repository artifacts so future agents and team members start with current context.

Core Features & Use Cases

  • PROJECT.md Updates: Adds implemented features, status, short descriptions, links to issues, key technical decisions, and updates the architecture overview and conventions.
  • ADR Creation & Updates: Generates or updates adr/ entries using the repository ADR template for significant architectural decisions with context, options, rationale, and consequences.
  • Tech Spec Retrospectives & Docs Maintenance: Appends retrospective notes to tech specs, updates README and docs when onboarding or developer-facing information changes, and records process friction for AIDLC improvements.
  • Output: Produces a single commit or PR containing all documentation changes following a standardized commit message and repository formatting conventions.

Quick Start

Run the Learn agent after a feature validation or incident close to update PROJECT.md, add any required ADRs, and commit documentation changes.

Frequently Asked Questions about agent-learn

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

FAQPage Schema
How do I capture project learnings and update documentation after closing an incident?

To capture project learnings after an incident closure, you can update PROJECT.md, write new ADRs, and append retrospective notes to tech specs. This consolidates decisions and insights into durable repository artifacts via a single commit or pull request.

What is the best way to document architectural decisions in a repository?

Documenting architectural decisions is best handled by generating Architecture Decision Records in an adr/ directory. The records should include context, options, rationale, and consequences, following the repository's existing naming and formatting conventions.

When should I update PROJECT.md during the development lifecycle?

You should update PROJECT.md after feature validation, incident closure, or major architectural decisions. It involves adding implemented features, status updates, links to issues, and key technical decisions to ensure future agents and team members start with current context.

Can I automate appending retrospective notes to existing tech specs?

Yes, you can append retrospective notes directly to existing tech specs. This process records process friction for AIDLC improvements and ensures retrospective documentation is maintained alongside developer-facing information changes in the repository.

Does generating ADRs require an existing repository template?

Generating ADRs uses the repository ADR template to ensure formatting consistency. The process creates or updates files in the adr/ directory and produces a single commit or PR that follows the repository's standardized commit message conventions.