walkthrough-generate

Generate a template-driven implementation walkthrough from run logs and intents.

201|19|Updated Dec 24, 2025

Search Tags:#templates #documentation #generation #walkthrough #run-review #specs-fire

Ready to run

npx skills add https://github.com/fabriqaai/specs.md --skill walkthrough-generate-fabriqaai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: walkthrough-generate
Source: https://github.com/fabriqaai/specs.md/tree/main/src/flows/fire/agents/builder/skills/walkthrough-generate
Command: npx skills add https://github.com/fabriqaai/specs.md --skill walkthrough-generate-fabriqaai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate an implementation walkthrough after a run completes, documenting decisions, changes, and verification steps for human review.

Core Features & Use Cases

Structured Walkthrough: Produces a consistent, template-driven document capturing decisions, deviations, and verification steps.
Run-to-Walkthrough Linkage: Reads run logs and work-item plans to produce traceable evidence of work performed.
Usage Scenarios: After a FIRE or AI-DLC run, automatically generate a walkthrough for auditing and knowledge transfer.

Quick Start

Trigger walkthrough generation after a run completes via the designated flow.
Locate the generated file at .specs-fire/runs/{run-id}/walkthrough.md and review.

Frequently Asked Questions about walkthrough-generate

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

FAQPage Schema

How do I generate implementation documentation after a run completes?▼

To generate implementation documentation after a run, trigger the walkthrough generation flow to read run logs and intents, producing a template-driven walkthrough that documents decisions, changes, and verification steps.

What is a structured walkthrough for run reviews?▼

A structured walkthrough for run reviews is a template-driven document that captures decisions, deviations, and verification steps from run logs and work-item plans, providing traceable evidence of work performed for auditing.

How do I document decisions and verification steps from AI run logs?▼

Document decisions and verification steps from AI run logs by executing the five-step process: gather, analyze, document, verify, and generate, which reads run intents and saves an audit-friendly walkthrough file.

Where are generated walkthrough files saved for auditing purposes?▼

Generated walkthrough files for auditing purposes are saved directly in the designated run folder at .specs-fire/runs/{run-id}/walkthrough.md, allowing for immediate human review and knowledge transfer.

Does the walkthrough generation process require manual input for each run?▼

The walkthrough generation process does not require manual input for each run; it automatically reads run logs and work-item plans through a structured five-step process to produce traceable evidence of work performed.

Can I use this walkthrough generation for FIRE and AI-DLC runs?▼

Yes, you can use this walkthrough generation for FIRE and AI-DLC runs to automatically produce consistent, audit-friendly documentation that captures decisions, deviations, and verification steps for knowledge transfer.