apm-8-summarize-session

Summarizes an APM session and archives its planning artifacts via the apm CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an APM (Agentic Project Management) session ends, its Spec, Plan, Tracker, and Memory artifacts are scattered across the .apm/ directory with no consolidated record. This Skill produces a structured session summary and optionally archives all artifacts so the workspace is clean for the next session while history is preserved. ## Core Features & Use Cases - Session Summarization: Reads .apm/spec.md, plan.md, tracker.md, and memory notes, then writes a structured .apm/session-summary.md with YAML frontmatter (date, project, stages completed, outcome). - Subagent Cross-Validation: Spawns an explorer subagent to verify Task Logs against the actual codebase, confirming deliverables exist and commits are on expected branches. - Optional Archival: Runs apm archive --force to snapshot all .apm/ artifacts into .apm/archives/<name>/ and maintains an archive index table. - Use Case: After a Manager confirms all Stages complete, invoke this Skill to generate a point-in-time summary, review it with the user, and archive the session before running apm init for a fresh start. ## Quick Start Ask the assistant to summarize the current APM session and archive it with the default dated name.

Frequently Asked Questions about 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 starting a new one?

Invoke the summarize-session command, which reads .apm/spec.md, plan.md, tracker.md, and memory notes, then writes .apm/session-summary.md. After your review, it can run apm archive to snapshot everything before you run apm init for a fresh session.

How does the session summary verify work was actually completed?

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

What does the apm archive command do to my workspace?

The apm archive --force command snapshots all .apm/ artifacts into .apm/archives/<name>/, writes archival metadata.json inside the archive, then removes installed files from the workspace root. Archives remain accessible to future sessions during Context Gathering.

How is the session outcome field determined in the summary?

Outcome is derived from Tracker state: complete when the Tracker frontmatter contains completed_at, partial when at least one Stage finished, and incomplete when zero Stages finished. It is recorded in the summary's YAML frontmatter.

Can I use this command as a Planner, Manager, or Worker agent?

No. The command is designed for a standalone agent role. If invoked by a Planner, Manager, or Worker, the instructions direct the agent to concisely decline and take no action.