mcpField
S
session-wrap

session-wrap

github.com/team-attentionAgent workflows82941 installsUpdated 27w ago
Repository

About session-wrap

A session wrap-up skill for development work that coordinates analysis agents, validates their proposals, and presents follow-up actions. It covers documentation, automation ideas, learnings, and prioritized tasks before selected actions are carried out.

Key features

  1. 01Check Git status and diffs
  2. 02Run four analysis agents in parallel
  3. 03Validate proposals with a follow-up agent
  4. 04Compile documentation and automation findings
  5. 05Execute only user-selected actions

Use cases

  1. 01Review changes before ending a work session
  2. 02Identify documentation updates and automation ideas
  3. 03Gather prioritized follow-up tasks before switching projects

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/team-attention/plugins-for-claude-natives --skill session-wrap

After installing, type/session-wrapin Claude Code to confirm it loaded.

Bundled filesreferences/multi-agent-patterns.md

Details

From the project README

Session Wrap Skill

Comprehensive session wrap-up workflow with multi-agent analysis.

Execution Flow

┌─────────────────────────────────────────────────────┐
│  1. Check Git Status                                │
├─────────────────────────────────────────────────────┤
│  2. Phase 1: 4 Analysis Agents (Parallel)           │
│     ┌─────────────────┬─────────────────┐           │
│     │  doc-updater    │  automation-    │           │
│     │  (docs update)  │  scout          │           │
│     ├─────────────────┼─────────────────┤           │
│     │  learning-      │  followup-      │           │
│     │  extractor      │  suggester      │           │
│     └─────────────────┴─────────────────┘           │
├─────────────────────────────────────────────────────┤
│  3. Phase 2: Validation Agent (Sequential)          │
│     ┌───────────────────────────────────┐           │
│     │       duplicate-checker           │           │
│     │  (Validate Phase 1 proposals)     │           │
│     └───────────────────────────────────┘           │
├─────────────────────────────────────────────────────┤
│  4. Integrate Results & AskUserQuestion             │
├─────────────────────────────────────────────────────┤
│  5. Execute Selected Actions                        │
└─────────────────────────────────────────────────────┘

Step 1: Check Git Status

git status --short
git diff --stat HEAD~3 2>/dev/null || git diff --stat

Step 2: Phase 1 - Analysis Agents (Parallel)

Execute 4 agents in parallel (single message with 4 Task calls).

Session Summary (Provide to all agents)
Session Summary:
- Work: [Main tasks performed in session]
- Files: [Created/modified files]
- Decisions: [Key decisions made]
Parallel Execution
Task(
    subagent_type="doc-updater",
    description="Document update analysis",
    prompt="[Session Summary]\n\nAnalyze if CLAUDE.md, context.md need updates."
)

Task(
    subagent_type="automation-scout",
    description="Automation pattern analysis",
    prompt="[Session Summary]\n\nAnalyze repetitive patterns or automation opportunities."
)

Task(
    subagent_type="learning-extractor",
    description="Learning points extraction",
    prompt="[Session Summary]\n\nExtract learnings, mistakes, and new discoveries."
)

Task(
    subagent_type="followup-suggester",
    description="Follow-up task suggestions",
    prompt="[Session Summary]\n\nSuggest incomplete tasks and next session priorities."
)
Agent Roles
AgentRoleOutput
doc-updaterAnalyze CLAUDE.md/context.md updatesSpecific content to add
automation-scoutDetect automation patternsskill/command/agent suggestions
learning-extractorExtract learning pointsTIL format summary
followup-suggesterSuggest follow-up tasksPrioritized task list

Step 3: Phase 2 - Validation Agent (Sequential)

Run after Phase 1 completes (dependency on Phase 1 results).

Task(
    subagent_type="duplicate-checker",
    description="Phase 1 proposal validation",
    prompt="""
Validate Phase 1 analysis results.

## doc-updater proposals:
[doc-updater results]

## automation-scout proposals:
[automation-scout results]

Check if proposals duplicate existing docs/automation:
1. Complete duplicate: Recommend skip
2. Partial duplicate: Suggest merge approach
3. No duplicate: Approve for addition
"""
)

Step 4: Integrate Results

## Wrap Analysis Results

### Documentation Updates
[doc-updater summary]
- Duplicate check: [duplicate-checker feedback]

### Automation Suggestions
[automation-scout summary]
- Duplicate check: [duplicate-checker feedback]

### Learning Points
[learning-extractor summary]

### Follow-up Tasks
[followup-suggester summary]

Step 5: Action Selection

AskUserQuestion(
    questions=[{
        "question": "Which actions would you like to perform?",
        "header": "Wrap Options",
        "multiSelect": true,
        "options": [
            {"label": "Create commit (Recommended)", "description": "Commit changes"},
            {"label": "Update CLAUDE.md", "description": "Document new knowledge/workflows"},
            {"label": "Create automation", "description": "Generate skill/command/agent"},
            {"label": "Skip", "description": "End without action"}
        ]
    }]
)

Step 6: Execute Selected Actions

Execute only the actions selected by user.


Quick Reference

When to Use
  • End of significant work session
  • Before switching to different project
  • After completing a feature or fixing a bug
When to Skip
  • Very short session with trivial changes
  • Only reading/exploring code
  • Quick one-off question answered
Arguments
  • Empty: Proceed interactively (full workflow)
  • Message provided: Use as commit message and commit directly

Additional Resources

See references/multi-agent-patterns.md for detailed orchestration patterns.

Comments

Markdown supported