Capture and curate reusable knowledge from software development work units.
npx skills add https://github.com/Obsidian-Owl/specwright --skill sw-learn
Please help me install this Agent Skill. Skill: sw-learn Source: https://github.com/Obsidian-Owl/specwright/tree/main/skills/sw-learn Command: npx skills add https://github.com/Obsidian-Owl/specwright --skill sw-learn
This Skill addresses the challenge of knowledge loss and repeated mistakes in software development by systematically capturing, curating, and promoting valuable learnings from the development process.
CONSTITUTION.md or patterns.md.Run the sw-learn skill to capture learnings from the current work unit.
High-intent search queries and answers about installing and using this skill.
To capture and reuse knowledge from software development work units, this Skill analyzes build failures, gate findings, and architectural decisions to identify reusable patterns for user approval. Approved patterns are then promoted into persistent knowledge bases to prevent knowledge loss.
The best way to stop repeated mistakes in software development is to systematically curate project learnings by identifying recurring themes across multiple work units. This retrospective analysis promotes user-approved patterns into persistent files like CONSTITUTION.md.
Yes, you can promote architectural decisions into a persistent knowledge base after the Skill identifies them as reusable patterns. The user-driven curation process requires your explicit approval before patterns are written to files like patterns.md.
You identify recurring patterns across multiple software development work units through retrospective analysis of build failures and gate findings. This mechanism tracks recurring themes over time, enabling deeper insights into your continuous improvement process.
Yes, continuous improvement knowledge management works without external dependencies because the Skill operates autonomously to analyze work units. It relies solely on user-approved curation to promote identified patterns into your existing markdown knowledge bases.
You should not use automated pattern recognition for software learnings when you need immediate code deployment without curation overhead, because the user-driven approval process requires manual review before patterns are promoted to persistent knowledge bases.
arcasilesgroupCheck staged changes against governance standards in advise, gate, and drift modes.
IgorGanapolskySearch Thumbgate lessons to retrieve corrective actions and linked enforcement rules.
joseph-c-mcguireAutomate lint, format, type, test, and security checks during builds.
GiorgioRicciardielloAnalyze tournament debates and reflection reviews to synthesize patterns into a structured meta-review note.