product-continuity

Captures decisions, assumptions, risks, and session handoffs into persistent project continuity documents.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/scoots31/engineering-playbook --skill product-continuity-scoots31
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-continuity
Source: https://github.com/scoots31/engineering-playbook/tree/main/skills/product-continuity
Command: npx skills add https://github.com/scoots31/engineering-playbook --skill product-continuity-scoots31

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Solo builders lose critical context between sessions — decisions get re-litigated, assumptions go unvalidated, and open questions disappear. This Skill acts as the project's institutional memory, continuously capturing what was decided, why, and what remains open so any future session can resume with full context. ## Core Features & Use Cases - Continuous capture: Logs decisions with reasoning, outstanding questions, assumptions, risks, changes, and glossary terms into docs/continuity/ as they surface during any phase. - Session handoff and resume prompts: Maintains a current handoff document updated at every slice completion and session close, including a copy-paste resume prompt for the next session. - Long-gap re-entry protocol: After 21+ days of inactivity, runs a three-check sequence covering codebase state, environment health, and context validity before new work begins. - Use Case: A solo builder returns to a project after a month away. The Skill reads the handoff, flags two stale assumptions and one blocking question, verifies the codebase is clean, and produces a re-entry summary so work resumes exactly where it stopped. ## Quick Start Activate guided mode and ask the assistant to log today's decisions and update the project handoff before closing the session.

Frequently Asked Questions about product-continuity

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

FAQPage Schema
How do I preserve project context between AI coding sessions?

Maintain a handoff document updated at every session close with current phase, completed work, open items, and a resume prompt. Pair it with decision and assumption logs so the next session starts with full reasoning, not just outcomes.

What should a project decision log contain?

Each entry should state the decision, the reasoning behind it, alternatives considered and rejected, tradeoffs acknowledged, and any prior decision that shaped it. Capturing the why prevents re-litigating settled choices months later.

How do I resume a software project after a long break?

Run a three-check re-entry: verify the codebase has no unexpected commits or uncommitted work, confirm the environment still runs with unchanged dependencies, and review open questions and unvalidated assumptions for staleness before starting new work.

What is the difference between an assumptions log and a risk register?

Assumptions are things treated as true without verification, tracked with validation methods and status. Risks are known threats with likelihood, impact, trigger conditions, and mitigations. Both need regular review to avoid silent project corruption.

When should session documentation be written?

Write the session log and update the handoff at session close, and update the handoff immediately when a slice is marked Done. Deferring capture to later sessions loses reasoning and leaves the handoff stale if work stops unexpectedly.