he-learn

Convert post-release outcomes into documentation and automated guardrails.

4|1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/mattjefferson/harness-engineering --skill he-learn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: he-learn
Source: https://github.com/mattjefferson/harness-engineering/tree/main/skills/he-learn
Command: npx skills add https://github.com/mattjefferson/harness-engineering --skill he-learn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill transforms the outcomes of completed initiatives into lasting improvements, ensuring that lessons learned are captured, documented, and used to build mechanical guardrails for future work.

Core Features & Use Cases

  • Learning Capture: Converts post-release results, surprises, and friction into actionable learning entries.
  • Durable Documentation: Updates domain docs, runbooks, and architectural documents to reflect new policies and procedures.
  • Guardrail Implementation: Establishes or updates mechanical checks (CI, linting) based on recurring issues.
  • Plan Archival: Finalizes and archives initiative plans for future reference.
  • Use Case: After a software release, this Skill analyzes the CI results, review feedback, and any operational incidents to update the project's documentation, add new automated checks to prevent similar issues, and archive the completed plan.

Quick Start

Use the he-learn skill to process the outcomes of the initiative with slug 'new-feature-launch'.

Frequently Asked Questions about he-learn

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

FAQPage Schema
How do I turn post-release outcomes into durable documentation and guardrails?

To turn post-release outcomes into durable documentation and guardrails, process learnings from PR descriptions, CI results, and incident notes to update domain docs, runbooks, and AGENTS.md while implementing automated enforcement mechanisms.

What is the best way to capture learnings from CI results and review feedback?

The best way to capture learnings from CI results and review feedback is to convert post-release surprises and friction into actionable learning entries that directly update domain docs and establish mechanical checks.

How do I archive completed initiative plans after a software release?

To archive completed initiative plans after a software release, finalize the initiative plans and clear generated scratchpads to ensure lessons learned are captured and stored for future reference.

Can I use incident notes to update runbooks and architectural documents?

Yes, you can use incident notes to update runbooks and architectural documents by processing them alongside PR descriptions and review findings to reflect new policies and procedures.

How do I implement automated enforcement mechanisms based on recurring issues?

To implement automated enforcement mechanisms based on recurring issues, establish or update mechanical checks like CI and linting rules derived from post-release learning entries and review findings.

What is continuous improvement workflow for software engineering post-release?

Continuous improvement workflow for software engineering post-release involves processing outcomes to clear scratchpads, update documentation, implement guardrails, and archive initiative plans for lasting process improvements.