ralph-increment-feature-attempts

Increment feature attempt counters and log errors in feature_list.json.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps track the number of times an implementation attempt for a specific feature has failed, preventing infinite loops and identifying features that may be blocked.

Core Features & Use Cases

  • Attempt Tracking: Increments a counter for each failed implementation attempt of a feature.
  • Error Logging: Optionally records the last error message associated with a failed attempt.
  • Block Identification: Helps in identifying features that have exceeded a maximum number of attempts and might need manual intervention.
  • Use Case: When Ralph fails to implement feature F001 due to a compilation error, this skill is used to increment F001's attempt count and log the error, ensuring the system doesn't keep trying the same failed approach.

Quick Start

Use the ralph-increment-feature-attempts skill to increment the attempts for feature F042 and record the error message "Build failed".

Frequently Asked Questions about ralph-increment-feature-attempts

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

FAQPage Schema
How do I track failed feature implementation attempts in a JSON file?

You can track failed feature implementation attempts by incrementing a counter and logging the last error message within a JSON feature list file. This requires providing a specific feature ID to update its status and prevent infinite loops.

What is the best way to stop infinite loops during iterative feature development?

The best way to stop infinite loops in iterative development is by tracking failed implementation attempts. Incrementing an attempt counter for each blocked feature identifies when a maximum threshold is exceeded and manual intervention is needed.

How do I log error messages for blocked features in iterative development?

To log error messages for blocked features, you increment the feature attempt counter and optionally record the last error message. This updates the feature's status in the JSON feature list to identify compilation or implementation failures.

Can I use a JSON feature list to identify features that need manual intervention?

Yes, you can use a JSON feature list to identify features needing manual intervention. By tracking attempt counts and error messages, the system flags blocked features that have exceeded the maximum number of automated implementation attempts.

Does attempt tracking work without specifying a feature ID?

No, attempt tracking requires a feature ID to function correctly. The feature ID is a mandatory input needed to locate and update the specific feature's attempt counter and error log within the feature_list.json file.

Why does my feature status not update after a failed implementation attempt?

Feature status may not update if the attempt counter and error logging process was not triggered. You must explicitly increment the feature implementation attempt counter and pass the error message to update the JSON feature list file.