skills.rest
Vincri126
Vincri126COMMUNITY
Explore all skills by this author →
GitHub

continuity-package

Document session actions, decisions, and blockers in a date-stamped markdown report.

Updated Aug 23, 2026
Search Tags:#documentation#reporting#handoff#project-status#knowledge-transfer#session-continuity#action-log
One-click install
npx skills add https://github.com/Vincri126/MCO-Template --skill continuity-package
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: continuity-package
Source: https://github.com/Vincri126/MCO-Template/tree/main/cowork/skills/continuity-package
Command: npx skills add https://github.com/Vincri126/MCO-Template --skill continuity-package

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents knowledge gaps by documenting work, decisions, and blockers so that the next session can begin immediately without repeating context.

Core Features & Use Cases

  • Structured Checklist: Follow a mandated end-of-session checklist that updates a project status JSON, captures an action log, and records priorities and decisions.
  • State Documentation: Record file changes, feature progress, dependencies, and configuration updates to create a precise snapshot of the current workspace.
  • Use Case: At the end of a sprint day, use the continuity package to summarize engineering changes, highlight unresolved blockers, and hand the project safely to the next collaborator.

Quick Start

Summarize today's actions, blockers, and next priorities into the prescribed continuity report and save it as SESSION_CONTINUITY_YYYY-MM-DD.md.

Frequently Asked Questions about continuity-package

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

FAQPage Schema
How do I document session handoffs to prevent knowledge loss between work blocks?▼

Session handoffs are documented by updating project status metadata, logging actions and decisions, and saving a date-stamped markdown report capturing state, blockers, and next priorities.

What is the best way to track project status and action logs for engineering workflows?▼

Tracking project status involves following a structured end-of-session checklist that updates a project status JSON, captures an action log, and records priorities and decisions.

Can I use this session continuity package for sprint day handoffs to collaborators?▼

Yes, at the end of a sprint day you can use the continuity package to summarize engineering changes, highlight unresolved blockers, and hand the project safely to the next collaborator.

How do I record file changes and feature progress when ending a development session?▼

Recording file changes and feature progress requires documenting state, including dependencies and configuration updates, to create a precise snapshot of the current workspace.

What format does the session continuity report use for saving project state?▼

The session continuity report uses a date-stamped markdown format saved as SESSION_CONTINUITY_YYYY-MM-DD.md, capturing today's actions, blockers, and next priorities.

Related Skills

Explore More Product & Management Skills→
lengo0951lengo0951

ck:project-management

Manages tasks, updates plans, triggers documentation changes, and generates project status reports.

Community
Advanced
abdullah1854abdullah1854
1

daily-standup

Generate daily standup reports with Yesterday, Today, and Blockers sections.

Community
Basic
MarkusonMarkuson

bmad-sprint-planning

Parse epic and story markdown to generate sprint-status.yaml tracking files.

Community
Advanced
the-agency-aithe-agency-ai
39

Session Handoff

Generate session handoff files documenting progress, decisions, and pending issues.

Official
Basic