lessons-learned

To document lessons learned, this skill captures structured learning entries after Design, Build, Refinement, or Finalize phases. It evaluates trigger conditions and writes standardized YAML frontmatter and Markdown notes to a local archive for future reference.

Capturing phase reflections is best handled by generating standardized Markdown entries with YAML frontmatter. This approach records the date, repository, epic, stage, and phase alongside actionable future guidance in a local learning archive.

To record noteworthy events from an epic-stage-workflow phase, run this skill after finishing the phase. It assesses defined triggers and automatically generates a timestamped learning entry in your local documentation folder.

No external dependencies are required to archive learning entries locally. The skill independently writes structured YAML frontmatter and Markdown body files directly to the ~/docs/claude-learnings directory on your system.

Yes, structured documentation supports retrospective analysis across multiple phases. Each entry includes standardized fields like category, phase, and an analyzed flag, making it easy to retrieve and review past experiences from the local archive.

Automated phase-review documentation should not be used if your workflow lacks distinct Design, Build, Refinement, or Finalize phases. The skill relies on these specific epic-stage-workflow phases to trigger learning entry generation effectively.