speckit-opsmill-summary

Generates a flow-level markdown summary of the current Claude Code session into the feature directory.

9|2|Updated Aug 27, 2025
One-click install
npx skills add https://github.com/opsmill/infrahub-solution-ai-dc --skill speckit-opsmill-summary-opsmill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-opsmill-summary
Source: https://github.com/opsmill/infrahub-solution-ai-dc/tree/main/.agents/skills/speckit-opsmill-summary
Command: npx skills add https://github.com/opsmill/infrahub-solution-ai-dc --skill speckit-opsmill-summary-opsmill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a long working session, it is hard for teammates (or future-you) to reconstruct what happened without reading the full transcript or git log. This Skill produces a concise, high-level session summary — executive summary, chronological timeline, and outcomes — written next to spec.md and plan.md in the active feature directory. ## Core Features & Use Cases - Flow-Level Summaries: Produces a narrative summary with exactly three sections (Executive Summary, Timeline, Outcomes), deliberately excluding diffs, line numbers, and per-tool-call narration. - Optional Time Bounding: Supports a --since <commit|time> argument to limit the summary window to recent work. - Strictly Additive & Idempotent: Never modifies spec.md, plan.md, or source files; repeated invocations produce comparable summaries rather than summaries of summaries. - Use Case: At the end of a feature-branch work session, run the command to write sessions/session-YYYY-MM-DD-HHMM.md so a reviewer can understand the session's purpose, order of work, and shipped outcomes in under 60 seconds. ## Quick Start Ask the assistant to summarize the current session into the feature directory, optionally bounding it with an argument like --since HEAD~10.

Frequently Asked Questions about speckit-opsmill-summary

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

FAQPage Schema
How do I summarize a Claude Code session in a spec-kit project?▼

Run the summary command on an active feature branch; it resolves FEATURE_DIR via check-prerequisites.sh and writes a session-YYYY-MM-DD-HHMM.md file under FEATURE_DIR/sessions/ with an executive summary, timeline, and outcomes.

How do I limit the session summary to recent work?▼

Pass the --since argument, for example --since HEAD~10 or --since 14:00. The value is passed to git log as a revision range or date filter so only phases after that point appear in the timeline.

Does the session summary modify spec.md or plan.md?▼

No. The command is strictly additive and only writes the session summary file under FEATURE_DIR/sessions/. It never edits spec.md, plan.md, tasks.md, or any source files.

Why does the summary command fail with a feature directory error?▼

It fails fast when no FEATURE_DIR can be resolved, which happens when you are not on an active feature branch in a spec-kit project. Switch to a feature branch with a .specify structure and re-run.

What level of detail does the session summary include?▼

It stays at the flow level: no diffs, line numbers, code snippets, or per-tool-call narration. The target is a document under roughly 80 lines that a reader can absorb in under 60 seconds.