skills.rest
tomzx
tomzxCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

create-learnings

Capture structured retrospective learnings into a Markdown document.

5|Updated Jul 25, 2025
Search Tags:#documentation#retrospective#agile#sdlc#learnings#process-improvement#knowledge-sharing
One-click install
npx skills add https://github.com/tomzx/agents --skill create-learnings
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-learnings
Source: https://github.com/tomzx/agents/tree/main/skills/create-learnings
Command: npx skills add https://github.com/tomzx/agents --skill create-learnings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture learnings after completing a feature, sprint, or project in a structured retrospective format.

Core Features & Use Cases

  • Structured retrospective document capturing what went well, what didn't, process improvements, technical insights, and next actions.
  • Standardized output saved to .sdlc/knowledge/learnings/NNNN-<slug>.md for auditability and sharing.
  • Supports referencing context from .sdlc/knowledge/assumptions/ and .sdlc/knowledge/decisions/ to enrich learnings.

Quick Start

Draft a retrospective by gathering context and saving the Learnings document to .sdlc/knowledge/learnings/NNNN-<slug>.md.

Frequently Asked Questions about create-learnings

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

FAQPage Schema
How do I document retrospective learnings after a software development sprint?▼

Documenting retrospective learnings after a sprint involves capturing what went well, what didn't, and process improvements in a standardized Markdown file saved to .sdlc/knowledge/learnings/ for auditability and knowledge sharing.

What is the best way to capture technical insights and process improvements from a completed project?▼

Capturing technical insights and process improvements is best done by creating a structured retrospective document that records next actions and lessons learned, outputting a standardized Markdown file to your knowledge base for future reference.

Can I reference existing assumptions and decisions when creating agile retrospective documents?▼

Yes, you can reference existing context from the .sdlc/knowledge/assumptions/ and .sdlc/knowledge/decisions/ directories to enrich your agile retrospective documents and provide deeper technical insights for auditing.

Where are the generated learning documents stored in the SDLC knowledge sharing workflow?▼

The generated learning documents are stored as Markdown files at .sdlc/knowledge/learnings/NNNN-<slug>.md, following a standardized schema to ensure auditability across the software development lifecycle.

Does this approach support linking process improvements to specific software development lifecycle phases?▼

Yes, it applies after software development features or sprints to surface what went well, what didn't, and next actions, effectively linking process improvements and technical insights to specific SDLC phases.

Related Skills

Explore More Software Engineering Skills→
mkalhitti-cloudmkalhitti-cloud
2

trading-knowledge-vault

Enforce mandatory lessons-learned reviews before NinjaTrader code changes.

Community
Advanced
Yukine5377Yukine5377

bmad-retrospective

Facilitate structured epic retrospectives to capture lessons and plan improvements.

Community
Advanced
packetalienpacketalien

retrospective

Analyze sprint and milestone data to generate a structured Markdown retrospective.

Community
Advanced
openakitaopenakita
2.0k

openakita/skills@knowledge-capture

Extract insights, decisions, and action items into structured Notion pages.

Community
Advanced