Continuous Learning System

Capture and persist project-specific learning events as JSONL across agent sessions.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/drshailesh88/build_playbook --skill continuous-learning-system
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Continuous Learning System
Source: https://github.com/drshailesh88/build_playbook/tree/main/skills/continuous-learning
Command: npx skills add https://github.com/drshailesh88/build_playbook --skill continuous-learning-system

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents valuable discoveries from being lost between sessions by capturing what worked, what broke, and why, then reusing that knowledge next time.

Core Features & Use Cases

  • Session Start Learning Load: Restores the last session state and injects the most relevant prior learnings, including high-confidence items (0.8+), to speed up reasoning and reduce repeated mistakes.
  • Learning Capture at Session Boundaries: Records discoveries across patterns, pitfalls/root causes, user preferences, architecture decisions, tool behaviors, and operational/deployment knowledge during execution.
  • Project-Scoped Persistence: Stores learnings as JSONL per project and supports confidence-based accumulation so guidance improves with ongoing usage.

Quick Start

Tell your agent to run a project session and interact with the learning system using the /learn command to review and apply recent project learnings.

Frequently Asked Questions about Continuous Learning System

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

FAQPage Schema
How do I persist agent debugging context across multiple coding sessions?

You can persist agent debugging context across sessions by capturing project-specific learnings into JSONL files. The system stores what worked, what broke, and why under a project-scoped directory so future runs reload relevant context instead of repeating prior work.

How does loading prior learnings at session start improve agent workflows?

Loading prior learnings at session start restores the last session state and injects high-confidence items (0.8+) into agent context. This speeds up reasoning and reduces repeated mistakes by immediately providing historical architecture, debugging, and tool usage knowledge.

What is the best way to record root causes and pitfalls discovered during software development?

The best way to record root causes and pitfalls is structured learning capture at session boundaries. The system logs discoveries across patterns, pitfalls, architecture decisions, and tool behaviors, then applies confidence scoring to accumulate reliable guidance over time.

Can I use confidence scoring to manage accumulated agent learnings for my project?

Yes, you can use confidence scoring to manage accumulated agent learnings. The system applies confidence-based accumulation to project-scoped JSONL storage, ensuring guidance improves with ongoing usage and only high-relevance context is injected into future agent sessions.

Where are project learnings stored when using git state for agent persistence?

Project learnings are stored as JSONL files under the directory path ~/.buildplayplay/projects/{project-slug}/. This project-scoped storage structure ensures session-end persistence separates learnings per project using stored git state.

Do I need to manually save session outcomes to reuse project context in future agent runs?

You do not need to manually save session outcomes. The system automatically handles session-end persistence to project-scoped storage, while session-start learning loading automatically retrieves and injects relevant prior learnings into your agent workflow.