skills.rest
Maple-and-Spruce
Maple-and-SpruceOFFICIAL
Explore all skills by this author →
GitHub

session-management

Coordinate session documentation and lifecycle updates across the SDLC.

Updated Oct 4, 2025
Search Tags:#workflow#documentation#agile#archiving#session-management#sdlc#team-docs
One-click install
npx skills add https://github.com/Maple-and-Spruce/maple-and-spruce --skill session-management-maple-and-spruce
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-management
Source: https://github.com/Maple-and-Spruce/maple-and-spruce/tree/main/.claude/skills/session-management
Command: npx skills add https://github.com/Maple-and-Spruce/maple-and-spruce --skill session-management-maple-and-spruce

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing session docs and keeping project documentation synchronized across the SDLC can be error-prone and time-consuming. This skill standardizes session initiation and closure, ensuring updates are captured and archived consistently.

Core Features & Use Cases

  • Self-updating documentation workflow following the READ -> FIND -> UPDATE -> CREATE -> ARCHIVE lifecycle.
  • Clear guidance on where to locate session context (AGENTS.md, docs/sessions/SESSION.md) and related references for different task types.
  • Use Case: Start a new development session and end it with a complete, archived set of status notes.

Quick Start

Begin a session by reading AGENTS.md and docs/sessions/SESSION.md, then apply the READ -> FIND -> UPDATE -> CREATE -> ARCHIVE workflow to keep documentation current.

Frequently Asked Questions about session-management

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

FAQPage Schema
How do I maintain project documentation across the agile SDLC?▼

To maintain project documentation across the agile SDLC, apply a structured READ, FIND, UPDATE, CREATE, and ARCHIVE lifecycle. This workflow ensures session docs and status notes are consistently captured and synchronized throughout development.

What is the best way to track development session status notes?▼

Tracking development session status notes is best handled by standardizing session initiation and closure within AGENTS.md and docs/sessions/SESSION.md. This approach enforces traceability and archives records consistently across the project.

How do I start and end development sessions with consistent documentation?▼

To start and end development sessions with consistent documentation, begin by reading AGENTS.md and docs/sessions/SESSION.md. Then apply the READ, FIND, UPDATE, CREATE, and ARCHIVE workflow to capture updates and archive session records upon closure.

Can I use this session management workflow for archiving team docs?▼

Yes, you can use this workflow for archiving team docs. It enforces a structured lifecycle that applies to ending development sessions and archiving session records, ensuring updates are captured and traceable through project references.

Why does session documentation become unsynchronized across the SDLC?▼

Session documentation becomes unsynchronized across the SDLC because manually keeping project docs updated is error-prone and time-consuming. Standardizing session initiation and closure resolves this by enforcing a structured lifecycle for all updates.

Related Skills

Explore More Content & Communication Skills→
paradox123paradox123

context-bootstrap

Collect repository structure, runnable commands, and architecture anchors at startup.

Community
Intermediate
gaiastudio-aigaiastudio-ai
2

gaia-history

Display historical sprint velocity, estimate accuracy, and recurring findings.

Official
Intermediate
ShipTodayShipToday

forge-autopilot

Automate and manage SDLC activities through Forge platform workflows.

Official
Advanced
wilsonfaustinowilsonfaustino
2

wrap-up

Automate end-of-session knowledge capture with Obsidian notes and memory updates.

Community
Intermediate