state-doc

Record tasks, decisions, blockers, and next steps in a STATE.md file.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/disciplin-run-org/jjstack --skill state-doc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: state-doc
Source: https://github.com/disciplin-run-org/jjstack/tree/main/skills/state-doc
Command: npx skills add https://github.com/disciplin-run-org/jjstack --skill state-doc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining an immediate, up-to-date overview of ongoing work sessions and decisions, preventing context loss during breaks or handoffs.

Core Features & Use Cases

  • Real-time Status Tracking: Record active tasks, decisions, blockers, and upcoming actions in a structured format.
  • Context Preservation: Preserve critical branch-specific knowledge and learning snippets for easy reference.
  • Use Case: When working on a lengthy project, create and update STATE.md to document blockers, recent decisions, and next steps, ensuring all team members stay aligned.

Quick Start

When starting your session, initialize a STATE.md file in your repository root to begin recording your current work context.

Frequently Asked Questions about state-doc

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

FAQPage Schema
How do I track current work status and prevent context loss during project handoffs?▼

To prevent context loss during handoffs, maintain a live STATE.md file in your repository root to record active tasks, recent decisions, blockers, and upcoming actions for seamless team alignment.

What is a STATE.md file used for in software development collaboration?▼

A STATE.md file is used for real-time status tracking and context preservation in software development, capturing immediate work context, branch-specific knowledge, and learning snippets to improve team collaboration.

How do I document blockers and decisions for ongoing work sessions?▼

Document blockers and decisions for ongoing work sessions by initializing a STATE.md file and continuously updating it with structured entries reflecting the present state of work, ensuring critical knowledge is retained.

What is the best way to preserve branch-specific knowledge and learning snippets?▼

The best way to preserve branch-specific knowledge and learning snippets is to record them in a structured STATE.md file, ensuring critical project context remains accessible for future reference and team handoffs.

Can I use this status tracking approach for individual developer workflows?▼

Yes, you can use this status tracking approach for individual developer workflows, as it is applicable when managing ongoing work sessions across teams or individuals to document immediate context and prepare for breaks.