source-command-apm-8-summarize-session

Summarizes APM session artifacts and archives them via the apm CLI.

1|Updated Dec 13, 2025
One-click install
npx skills add https://github.com/ZK-Theory/TDL --skill source-command-apm-8-summarize-session-zk-theory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-command-apm-8-summarize-session
Source: https://github.com/ZK-Theory/TDL/tree/main/.agents/skills/source-command-apm-8-summarize-session
Command: npx skills add https://github.com/ZK-Theory/TDL --skill source-command-apm-8-summarize-session-zk-theory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? At the end of an APM (Agentic Project Management) session, project state is scattered across spec, plan, tracker, and memory files. This Skill consolidates that state into a structured session summary and optionally archives the entire session for future reference. ## Core Features & Use Cases - Session Summarization: Reads .apm/spec.md, .apm/plan.md, .apm/tracker.md, and .apm/memory/index.md to produce a point-in-time session-summary.md with YAML frontmatter (date, project, stages completed, outcome). - Subagent Cross-Validation: Spawns an Explore subagent to verify Task Logs against the actual codebase, confirming deliverables exist and commits are on expected branches. - Session Archival: Runs apm archive --force to snapshot all .apm/ artifacts into .apm/archives/<name>/ and maintains an archive index table. - Use Case: After completing a multi-stage APM project, ask the assistant to summarize the session; it produces a structured summary, asks for your corrections, then archives everything so a fresh session can start with apm init. ## Quick Start Ask the assistant to summarize the current APM session and archive it when you confirm.

Frequently Asked Questions about source-command-apm-8-summarize-session

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

FAQPage Schema
How do I summarize an APM session before closing it?

Invoke the summarize-session command, which reads the spec, plan, tracker, and memory index files, then writes a session-summary.md with YAML frontmatter capturing date, project, stages completed, and outcome. You review the summary before it is finalized.

How does APM session archival work?

After you approve, the command runs `apm archive --force` (optionally with a custom name), which snapshots all .apm/ artifacts into .apm/archives/<name>/, writes metadata.json, and cleans the workspace root. An entry is appended to .apm/archives/index.md.

Does the summary verify that code deliverables actually exist?

Yes. The procedure spawns an Explore subagent that reads all .apm/ artifacts including Task Logs and cross-validates them against the current codebase, checking that deliverables exist, commits are on expected branches, and validation results hold.

What determines the outcome field in the session summary?

The outcome is derived from session state: `complete` when the Tracker frontmatter contains completed_at, `partial` when at least one Stage finished, and `incomplete` when zero Stages finished.

Can I start a new APM session after archiving?

Yes. After archival, run `apm init` or `apm custom` in the terminal to scaffold a fresh .apm/ directory with blank planning documents. Previous archives remain accessible in .apm/archives/ for the new Planner during context gathering.