ralph-update-feature-status

Update feature statuses in JSON files and recalculate summary statistics.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/Was85/ralph-rlm-agent-framework --skill ralph-update-feature-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph-update-feature-status
Source: https://github.com/Was85/ralph-rlm-agent-framework/tree/main/claude-code/shell/.claude/skills/ralph/update-feature-status
Command: npx skills add https://github.com/Was85/ralph-rlm-agent-framework --skill ralph-update-feature-status

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the management of feature statuses within a project's feature_list.json file, ensuring accurate tracking of development progress.

Core Features & Use Cases

  • Status Updates: Allows changing a feature's status to pending, in_progress, complete, or blocked.
  • Automated Stats Recalculation: Automatically updates the stats object in feature_list.json to reflect the new status counts.
  • Use Case: During development, mark a feature as in_progress when work begins, and complete once it's successfully implemented and tested. If a feature encounters persistent issues, mark it as blocked for review.

Quick Start

Use the ralph-update-feature-status skill to set the status of feature F042 to in_progress.

Frequently Asked Questions about ralph-update-feature-status

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

FAQPage Schema
How do I update feature status in a JSON file for development tracking?

To update feature status in a JSON file, specify a valid feature ID and assign one of four predefined values: pending, in_progress, complete, or blocked. The system modifies the JSON structure and recalculates summary statistics to reflect the changes.

What are the valid status values for tracking feature lifecycle stages?

The valid status values for tracking feature lifecycle stages are pending, in_progress, complete, and blocked. Using these predefined values ensures the JSON structure remains valid and summary statistics accurately track development progress.

How do I recalculate summary statistics after changing a feature status?

Recalculating summary statistics happens automatically after a feature status change. When a valid status is applied to a feature ID, the system updates the stats object in the JSON file to reflect the new status counts without manual intervention.

Can I use this feature tracking workflow without a valid feature ID?

No, a valid feature ID is required to use this feature tracking workflow. The system relies on valid feature identifiers to locate the correct entry within the JSON file and apply one of the four predefined status values.

Does updating feature status in JSON work for blocked development items?

Yes, updating feature status in JSON works for blocked development items. If a feature encounters persistent issues, you can mark it as blocked for review, and the summary statistics will automatically update to include this status.

What happens if I use an invalid status value when updating feature status in JSON?

Using an invalid status value prevents the update, as the system only accepts pending, in_progress, complete, or blocked. Maintaining these constraints ensures the JSON structure stays valid and summary statistics remain accurate.