skills.rest
pax-k
pax-kCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

feature-state-machine

Manage feature states with evidence-backed transitions and WIP control.

3|Updated Jun 8, 2026
Search Tags:#project management#verification#feature management#state tracking#WIP control
One-click install
npx skills add https://github.com/pax-k/pax-fullstack-harness --skill feature-state-machine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-state-machine
Source: https://github.com/pax-k/pax-fullstack-harness/tree/main/skills/feature-state-machine
Command: npx skills add https://github.com/pax-k/pax-fullstack-harness --skill feature-state-machine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures a machine-readable feature state list is maintained for agent work, enabling WIP control, verification, and evidence-backed state transitions.

Core Features & Use Cases

  • Feature State Management: Track and manage feature states, ensuring WIP control and evidence-backed transitions.
  • Verification Commands: Enforce verification for each feature to ensure accuracy and completeness.
  • Evidence-Backed Completion: Ensure every passing feature has evidence to support its completion state.

Quick Start

Use the feature-state-machine skill to define and update feature states in your project.

Frequently Asked Questions about feature-state-machine

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

FAQPage Schema
How do I track feature states in a repository for agent work?▼

Feature state tracking is managed by maintaining a machine-readable feature list, enabling WIP control and evidence-backed state transitions for project management workflows.

How does WIP control work for feature management?▼

WIP control works by enforcing verification commands on each feature, ensuring that state transitions are evidence-backed and compliant with defined project management processes before completion.

What's the best way to ensure evidence-backed feature completion?▼

Evidence-backed completion is ensured by enforcing verification commands that require every passing feature to provide concrete evidence supporting its final state in the repository.

Do I need a defined verification process to use feature state tracking?▼

Yes, a defined verification process and proper feature definition are required, as the state machine applies to workflows that demand tracking progress and ensuring compliance with defined states.

Can I use scripts to automate feature state transitions?▼

Scripts are provided as the core component to automate the management, verification, and updating of feature states, integrating WIP control directly into your repository workflows.

When should I not use a machine-readable feature state list?▼

A feature state list should not be used when a project lacks proper feature definitions or a verification process, as evidence-backed state transitions require structured inputs to function correctly.

Related Skills

Explore More Software Engineering Skills→
FrantssFrantss

setup-matt-pocock-skills

Configure repository issue tracking, triage labels, and documentation layouts.

Community
Intermediate
xxihxxih
1

quality-verify

Run verification commands and record results in .quality/quality-check.md.

Community
Intermediate
Covcloud-LLCCovcloud-LLC

pjm

Coordinate multi-session AI development workflows across git repositories.

Official
Advanced
hedgefoghedgefog
32

amxx-modding-kit-api-states

Manage entity states with a rule-based framework for AMXX applications.

Community
Advanced