walkthrough-generate

name	walkthrough-generate
description	Generate implementation walkthrough for human review after run completion. Documents decisions, changes, and verification steps.
version	1.0.0

Generate implementation walkthrough for human review after run completion. - Run completed successfully - Invoked by run-execute skill

<degrees_of_freedom> LOW — Follow walkthrough structure precisely. Be thorough but concise. </degrees_of_freedom>

ALWAYS generate walkthrough after run completion Document DECISIONS, not just changes Include verification steps — how to test this works Read run log from .specs-fire/runs/{run-id}/run.md Collect: Work item details (id, title, intent) Files created during implementation Files modified during implementation Decisions made during execution Tests added and coverage For each file created/modified: Identify purpose of the file Summarize key changes Note patterns or approaches used Extract implementation highlights: Main flow/algorithm implemented Security considerations (if applicable) Performance considerations (if applicable) Integration points with existing code Generate how-to-verify section: Commands to run the feature Expected behavior/output Manual test scenarios Generate walkthrough using template: templates/walkthrough.md.hbs Save to: .specs-fire/runs/{run-id}/walkthrough.md Walkthrough generated: .specs-fire/runs/{run-id}/walkthrough.md

<output_template> Walkthrough (.specs-fire/runs/{run-id}/walkthrough.md):

---
run: {run-id}
work_item: {work-item-id}
intent: {intent-id}
generated: {timestamp}
mode: {mode}
---

# Implementation Walkthrough: {title}

## Summary

{2-3 sentences describing what was implemented}

## Files Changed

### Created

| File | Purpose |
|------|---------|
| `{path}` | {purpose} |

### Modified

| File | Changes |
|------|---------|
| `{path}` | {changes} |

## Key Implementation Details

### 1. {Detail Title}

{description of implementation approach}

## Decisions Made

| Decision | Choice | Rationale |
|----------|--------|-----------|
| {decision} | {choice} | {rationale} |

## How to Verify

1. **{Step Title}**
   ```bash
   {command}
   ```
   Expected: {expected output}

2. **{Step Title}**
   {manual verification steps}

## Test Coverage

- Tests added: {count}
- Coverage: {percentage}%
- Status: {passing/failing}

---
*Generated by specs.md - fabriqa.ai FIRE Flow Run {run-id}*

</output_template>

<success_criteria> Walkthrough generated with all sections Files changed documented with purposes Decisions recorded with rationale Verification steps included Saved to run folder </success_criteria>