continuous-learning

Capture and organize reusable learnings from diamond completions into skill and documentation files.

7|1|Updated Jul 27, 2021
One-click install
npx skills add https://github.com/podcodar/webapp --skill continuous-learning-podcodar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: continuous-learning
Source: https://github.com/podcodar/webapp/tree/main/.opencode/skills/continuous-learning
Command: npx skills add https://github.com/podcodar/webapp --skill continuous-learning-podcodar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continuous-learning turns scattered, momentary learnings from each diamond completion into organized, reusable knowledge so future work improves instead of repeating the same mistakes.

Core Features & Use Cases

  • Capture and condense learnings: identify what is new and reusable, and rewrite it as durable knowledge rather than raw notes.
  • Classify by learning type: skill, agent behavior, workflow, or reference so the right artifact gets updated.
  • Create and update the right storage locations: generate new skill entries under .opencode/skills, update agent instructions under .opencode/agent, and record long-term docs under .opencode/docs and .maestro.
  • Register for discoverability: append each learning to .opencode/learnings/registry.md with type, source, summary, location, and confidence.

Quick Start

Use the continuous-learning skill to capture the learning from your latest diamond, then create or update the appropriate skill, agent, or docs entry and register it in the learnings registry.

Frequently Asked Questions about continuous-learning

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

FAQPage Schema
How do I capture and organize reusable knowledge from project discoveries?

Capture reusable knowledge by identifying significant discoveries, condensing them into durable documentation, and registering entries in a learnings registry with type, source, summary, location, and confidence to prevent knowledge loss.

What's the best way to prevent knowledge loss after completing a development phase?

Prevent knowledge loss by classifying learnings as skill, agent behavior, workflow, or reference types, then creating or updating corresponding files under .opencode directories and appending them to the learnings registry.

How do I classify learnings to update the right agent instructions and documentation?

Classify learnings by type to determine storage: generate skill entries under .opencode/skills, update agent instructions under .opencode/agent, and record long-term reference docs under .opencode/docs and .maestro.

Does continuous learning require a GitHub repository for workflow improvement tracking?

A GitHub repository provides the structured file system needed to store .opencode skills, agent instructions, and the learnings registry, ensuring workflow improvements are tracked and discoverable for future development phases.

When should I create a new skill entry versus updating existing agent behavior?

Create a new skill entry under .opencode/skills when capturing a distinct reusable capability, and update agent behavior under .opencode/agent when adjusting existing processing logic or workflow rules.

Can I use a learning registry to manage agent behavior adjustments and workflow improvements?

Yes, a learning registry manages agent behavior adjustments and workflow improvements by recording each learning's type, source, summary, location, and confidence level for consistent discoverability and future reference.