epic-walkthrough

Generate walkthrough.md documentation from epic workflow files and git log.

91|10|Updated Oct 4, 2025
One-click install
npx skills add https://github.com/marcusgoll/Spec-Flow --skill epic-walkthrough
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epic-walkthrough
Source: https://github.com/marcusgoll/Spec-Flow/tree/main/.claude/skills/epic-walkthrough
Command: npx skills add https://github.com/marcusgoll/Spec-Flow --skill epic-walkthrough

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Produces a thorough epic walkthrough document and triggers self-improvement prompts for ongoing quality.

Core Features & Use Cases

  • walkthrough.md generation from state.yaml, epic-spec.md, sprint plans
  • triggers self-improvement prompts and audit routines
  • provides a structured epic summary and next steps

Quick Start

Generate a walkthrough.md after epic completion and review, then trigger post-mortem prompts.

Frequently Asked Questions about epic-walkthrough

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

FAQPage Schema
How do I generate comprehensive walkthrough documentation for completed epics?

Epic-walkthrough generates audit-ready walkthrough documentation by extracting data from state.yaml, epic-spec.md, sprint-plan.md, and git logs, then applies variable substitution to a base template to produce a structured summary of epic milestones, deployment details, and velocity metrics.

When should I create an epic walkthrough after project completion?

Generate a walkthrough during epic lifecycle milestones—specifically at the finalization step, post-deployment phase, and when triggering the /finalize command—to capture audit-ready documentation while sprint context and deployment details remain fresh.

What files and data does an epic walkthrough pull from?

The walkthrough synthesizes input from state.yaml, epic-spec.md, sprint-plan.md, optimization-report.md, and git log history, then substitutes variables into the .spec-flow/templates/epic/walkthrough.md template to produce comprehensive documentation.

Can epic walkthroughs trigger quality improvement actions automatically?

Yes. Beyond generating walkthrough.md, the Skill triggers self-improvement prompts and audit routines to identify optimization opportunities and support ongoing quality refinement based on the completed epic's metrics and outcomes.

What structured information does a walkthrough document include?

A walkthrough document provides a structured epic summary covering sprint phases, velocity data, deployment specifics, and next steps—formatted as an audit-ready reference that documents the full epic lifecycle and supports post-mortem analysis.