speckit-summary-run

Name: speckit-summary-run
Availability: InStock
Author: OpsMill

Generate a flow-level session summary with timeline and outcomes as Markdown.

9|4|Updated May 13, 2025

Search Tags:#workflow #documentation #session #claude-code #summarize

Ready to run

npx skills add https://github.com/opsmill/infrahub-mcp --skill speckit-summary-run

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-summary-run
Source: https://github.com/opsmill/infrahub-mcp/tree/main/.agents/skills/speckit-summary-run
Command: npx skills add https://github.com/opsmill/infrahub-mcp --skill speckit-summary-run

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claude Code sessions can grow complex; this Skill condenses the flow into a concise, shareable summary that highlights decisions, milestones, and outcomes.

Core Features & Use Cases

Executive summary: Generate a one-paragraph overview of the session including goals and key takeaways.
Timeline: Produce a chronological outline of phases and events with timestamps or relative order.
Artifact generation: Write the summary into the active feature directory next to spec.md / plan.md for easy reference.

Quick Start

Run the summary command on the active feature branch to generate the session document.

Frequently Asked Questions about speckit-summary-run

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

FAQPage Schema

How do I generate a session summary for my Claude Code workflow?▼

To generate a session summary for Claude Code, you run a summary command on your active feature directory. It produces an executive summary, timeline, and outcomes list, writing the results to a Markdown file without altering source artifacts.

What is the best way to document complex Claude Code sessions?▼

The best way to document complex Claude Code sessions is to condense the workflow into a concise, shareable summary. This captures decisions, milestones, and outcomes in a structured Markdown file alongside your existing plan.

Does the session summary output modify my existing feature branch artifacts?▼

No, generating a session summary does not modify your existing feature branch artifacts. The process reads live session context and writes a new Markdown file into a sessions subdirectory, leaving source artifacts unaltered.

Can I create an executive summary and timeline for Claude Code work sessions?▼

Yes, you can create an executive summary and timeline for Claude Code work sessions. The process automates extraction of goals, key takeaways, and chronological events into a structured Markdown document stored in your feature directory.

Where are Claude Code session summaries stored after generation?▼

Claude Code session summaries are stored as Markdown files at FEATURE_DIR/sessions/session-YYYY-MM-DD-HHMM.md. This places the generated documentation next to spec.md and plan.md for easy reference.