session

Parse plan files to track PeerTalk phase session progress and blockers.

Updated Jan 27, 2026
One-click install
npx skills add https://github.com/matthewdeaves/peertalk --skill session-matthewdeaves
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session
Source: https://github.com/matthewdeaves/peertalk/tree/main/.claude/skills/session
Command: npx skills add https://github.com/matthewdeaves/peertalk --skill session-matthewdeaves

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Navigate and manage the multi-phase PeerTalk implementation workflow to surface current progress, identify the next tasks, and surface blockers.

Core Features & Use Cases

  • Surface overall phase progress and per-session status from plan files.
  • Identify the next available session to implement and provide a seamless path to start work with /implement.
  • Show blocked sessions and dependencies to help plan mitigations and scheduling.

Quick Start

Run /session to see the next available task and follow up with /implement <phase> <session> to start work.

Frequently Asked Questions about session

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

FAQPage Schema
How do I track progress and find the next task in a multi-phase implementation workflow?

To track multi-phase implementation workflow progress, use session management to parse plan files, extract status and dependencies, and surface the next available task with actionable prompts for workflow continuity.

How do I identify blockers and dependencies across project phases?

Identify blockers and dependencies across project phases by parsing plan files to extract status data, which reveals blocked sessions and dependency chains to help schedule mitigations.

What is the best way to view session details across all implementation phases?

Viewing session details across implementation phases requires plan-file parsing to aggregate per-session status, dependencies, and overall progress metrics into a single navigable workflow surface.

How do I start implementing a specific session after finding the next available task?

After finding the next available task, start implementing a specific session by following the generated actionable next-steps prompt and executing the implement command with the designated phase and session identifiers.

Can I use this session tracking approach without predefined plan files?

No, this session tracking approach enforces plan-file parsing to extract status and dependencies, requiring predefined plan files to accurately surface progress and identify next tasks.