walkthrough-generate

Generate a structured implementation walkthrough from run data after completion.

3|1|Updated Jan 23, 2026

Search Tags:#automation #workflow #templates #documentation #reproducibility #walkthrough

Ready to run

npx skills add https://github.com/4tikhonov/the-minority-report --skill walkthrough-generate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: walkthrough-generate
Source: https://github.com/4tikhonov/the-minority-report/tree/main/ontologies/.specsmd/fire/agents/builder/skills/walkthrough-generate
Command: npx skills add https://github.com/4tikhonov/the-minority-report --skill walkthrough-generate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes post-run reviews by generating a complete implementation walkthrough, documenting decisions, changes, verifications, and developer notes for future debugging and knowledge transfer.

Core Features & Use Cases

Automated walkthrough generation: Produces a structured, template-based walkthrough from run data.
Decision and deviation tracking: Captures decisions, deviations from plan, and rationale for changes.
Verification readiness: Includes verifications steps and test coverage notes to support quality checks.
Developer knowledge transfer: Encodes gotchas, tips, and context to accelerate future work.

Quick Start

After a run completes, the skill automatically generates a walkthrough at .specs-fire/runs/{run-id}/walkthrough.md using the templates/walkthrough.md.hbs.

Frequently Asked Questions about walkthrough-generate

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

FAQPage Schema

How do I generate an implementation walkthrough after a development run?▼

To generate an implementation walkthrough, use a tool that automatically analyzes run data, intents, and decisions to produce a structured, template-based record for audits and future debugging.

What is an automated post-run walkthrough and how does it help with debugging?▼

An automated post-run walkthrough is a structured documentation record that captures decisions, deviations, and verifications from a completed run, encoding developer context to accelerate future debugging and knowledge transfer.

How do I document project decisions and deviations from the plan for future reference?▼

Document project decisions and deviations by generating a walkthrough that automatically captures changes, rationale, and compliance with the work item plan into a standardized markdown file for future reference.

Can I automatically capture verification steps and test coverage notes after a run?▼

Yes, automated walkthrough generation includes verification steps and test coverage notes within the documented record, directly supporting quality checks and verification readiness for the completed run.

Where does the generated walkthrough file get saved?▼

The generated walkthrough file is automatically saved as a markdown document at .specs-fire/runs/{run-id}/walkthrough.md, utilizing a predefined handlebars template to enforce structure and compliance.

Do I need to manually format my documentation when using automated walkthrough generation?▼

No, automated walkthrough generation enforces the use of a predefined template, ensuring all decisions, changes, and developer notes are consistently formatted without manual intervention.