session-summary

Categorize SDD session decisions and generate structured summaries for project memory.

1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/noelserdna/claude-plugin-sdd --skill session-summary-noelserdna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-summary
Source: https://github.com/noelserdna/claude-plugin-sdd/tree/main/skills/session-summary
Command: npx skills add https://github.com/noelserdna/claude-plugin-sdd --skill session-summary-noelserdna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams capture and organize decisions and context from SDD sessions, reducing memory loss and miscommunication. It identifies formal decisions that should be captured in artifacts and informal decisions that can be recorded for future reference. It creates a concise summary that can be added to project memory.

Core Features & Use Cases

  • Session Scan and Categorization: Analyze conversation and artifacts to separate formal decisions (ADRs, requirements) from informal context for memory.
  • Pipeline Progress Delta: Compare pipeline state before and after a session to reflect progress and outstanding actions.
  • SDD Session Summary Generation: Produce a structured, readable summary that documents decisions, context, and next steps.
  • Memory Update Assistant: Propose memory entries for informal context and request user confirmation before recording to project memory.

Quick Start

To generate a session summary, invoke the session-summary skill in your Claude Code session. It will scan the current conversation, categorize decisions, compute the pipeline delta, and present a structured summary. Follow-up prompts will guide you to record informal context to project memory if you approve.

Frequently Asked Questions about session-summary

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

FAQPage Schema
How do I capture decisions and context from a development session?

To capture decisions and context from a development session, use a session summary tool that scans conversations, categorizes formal versus informal decisions, and generates a structured memory artifact. This prevents memory loss and miscommunication across the team.

What is the best way to track pipeline progress after a meeting?

Tracking pipeline progress after a meeting involves comparing the pipeline state before and after the session to reflect progress and outstanding actions. This pipeline delta helps teams align with existing pipeline stages during retrospective reviews and planning.

How do I record informal decisions without modifying formal artifacts?

Recording informal decisions without modifying formal artifacts is possible by proposing memory entries for informal context and requesting user confirmation before recording. The system does not modify formal artifacts like ADRs without explicit approval.

Can I generate a session summary for retrospective reviews automatically?

Generating a session summary for retrospective reviews automatically requires invoking the skill within your Claude Code session. It scans the current conversation, computes the pipeline delta, and presents a structured summary documenting decisions and next steps.

How do I separate formal decisions from informal context in project memory?

Separating formal decisions from informal context in project memory requires analyzing conversation artifacts to identify formal decisions like requirements and ADRs. The skill categorizes these separately, ensuring formal artifacts remain unmodified without approval.

Does the session summary update project memory automatically?

The session summary does not update project memory automatically. It ensures memory updates require user confirmation, guiding you through follow-up prompts to record informal context to project memory only if you approve the proposed entries.