skills.rest
Redtropig
RedtropigCOMMUNITY
Explore all skills by this author →
GitHub

feature-state-keeper

Coordinate feature_list.json, progress.md, and session-handoff.md state files.

14|Updated May 28, 2026
Search Tags:#handoff#progress-tracking#feature-management#project-workflow#scope-tracking#state-record
One-click install
npx skills add https://github.com/Redtropig/harness-anchor --skill feature-state-keeper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-state-keeper
Source: https://github.com/Redtropig/harness-anchor/tree/main/skills/feature-state-keeper
Command: npx skills add https://github.com/Redtropig/harness-anchor --skill feature-state-keeper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

You maintain the machine-readable scope record of this project. Three files form the state trio: feature_list.json, progress.md, session-handoff.md. When used correctly, these files provide a durable, auditable record of what features exist, what is done, and what needs to be done next.

Core Features & Use Cases

  • Centralizes feature lifecycle data across feature_list.json (scope, done criteria, evidence), progress.md (session history), and session-handoff.md (current state snapshot).
  • Enforces consistency rules like the "exactly one in-progress feature" and the Default-FAIL evidence contract to prevent drift.
  • Use case: start a session, advance features, and generate a handoff that captures current state for the next team member.

Quick Start

Begin a session by inspecting the active feature in feature_list.json and recording progress to progress.md as you advance it.

Frequently Asked Questions about feature-state-keeper

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

FAQPage Schema
How do I maintain machine-readable feature state across multiple sessions?▼

Maintain feature state by coordinating a trio of files: feature_list.json for scope and evidence, progress.md for session history, and session-handoff.md for the current state snapshot to ensure durable alignment across sessions.

What is a Default-FAIL evidence contract in feature lifecycle tracking?▼

A Default-FAIL evidence contract requires strict proof of completion for features in feature_list.json before marking them as done, preventing state drift and ensuring auditable feature lifecycle tracking across progress.md and handoff files.

How do I generate a session handoff to prevent project workflow drift?▼

Generate a session handoff by recording your progress in progress.md and updating session-handoff.md with the current state snapshot, capturing what features exist and what needs to be done next for the next team member.

Can I track multiple in-progress features simultaneously in a project workflow?▼

No, feature state tracking enforces an exactly one in-progress feature consistency rule. This constraint in feature_list.json prevents scope drift and ensures focused progress updates before advancing features to done.

What are the limitations of using markdown and JSON files for progress tracking?▼

Limitations include the strict requirement for unique feature ids and structured progress updates in feature_list.json, meaning any deviation from the state trio coordination rules will break the Default-FAIL evidence contract and session handoff alignment.

Related Skills

Explore More Software Engineering Skills→
ChenShizheChenShizhe
1

session-handoff

Capture current session state into a handoff.md file.

Community
Intermediate
cyberpunk042cyberpunk042

pm-handoff

Generates a comprehensive handoff document from project metadata to docs/handoff.md.

Community
Advanced
Bossmann007Bossmann007

renewal-tracker

Track contract renewal deadlines and manage notice periods.

Community
Intermediate
silvarojasdiegoarturo91silvarojasdiegoarturo91

triage

Classify project issues into categories and manage their statuses.

Community
Intermediate