ferrox-extract-learnings

Extract completed phase learnings from markdown artifacts into LEARNINGS.md.

21|9|Updated Jul 21, 2026

Search Tags:#knowledge capture #summary #learnings #phase review #project handoff

Ready to run

npx skills add https://github.com/FerroxLabs/ferrox-factory --skill ferrox-extract-learnings

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ferrox-extract-learnings
Source: https://github.com/FerroxLabs/ferrox-factory/tree/main/skills/ferrox-extract-learnings
Command: npx skills add https://github.com/FerroxLabs/ferrox-factory --skill ferrox-extract-learnings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill preserves the decisions, lessons, surprises, and useful patterns from a completed phase so important context is not lost before work moves forward.

Core Features & Use Cases

Learnings Extraction: Consolidates insights from phase artifacts such as PLAN.md, SUMMARY.md, VERIFICATION.md, UAT.md, and STATE.md.
Structured Knowledge Capture: Writes a LEARNINGS.md file that records decisions, lessons learned, patterns discovered, and surprises encountered.
Use Case: After finishing a development phase, use this Skill to turn scattered execution notes into a durable reference for the next phase and future contributors.

Quick Start

Use the ferrox-extract-learnings skill to extract learnings for phase 3 and write them into LEARNINGS.md.

Frequently Asked Questions about ferrox-extract-learnings

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

FAQPage Schema

How do I capture project learnings before a phase handoff?▼

Capture phase learnings by consolidating decisions, surprises, and patterns from project artifacts into a structured LEARNINGS.md file. This ensures important context is preserved before work moves forward to the next development phase.

What is the best way to summarize phase decisions from markdown files?▼

Summarize phase decisions by reading multiple markdown artifacts such as VERIFICATION.md, UAT.md, and STATE.md, then extracting structured insights. This process turns scattered execution notes into a durable reference for future contributors.

How do I preserve execution context for iterative software delivery?▼

Preserve execution context by extracting phase context from project artifacts and writing a structured LEARNINGS.md file. This records decisions, lessons learned, and patterns discovered during iterative software delivery workflows.

Do I need specific markdown artifacts to extract post-execution review learnings?▼

Yes, extracting post-execution review learnings requires reading multiple markdown artifacts such as PLAN.md, SUMMARY.md, VERIFICATION.md, UAT.md, and STATE.md to produce a structured LEARNINGS.md entry from phase context.

When should I avoid consolidating scattered execution notes into a summary file?▼

Avoid consolidating execution notes into a summary file if your project lacks completed phase artifacts or does not follow iterative software delivery workflows requiring preserved decisions and surprises for phase handoffs.