skills.rest
lilliangreenberg
lilliangreenbergCOMMUNITY
Explore all skills by this author →
GitHub

feature-status

Count @failing tags in Gherkin feature files and write failing_count to feature-status.json.

Updated Aug 27, 2026
Search Tags:#automation#gherkin#json-output#count#feature-files#failing-features
One-click install
npx skills add https://github.com/lilliangreenberg/valuations-autonomous_coding --skill feature-status
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-status
Source: https://github.com/lilliangreenberg/valuations-autonomous_coding/tree/main/.claude/skills/feature-status
Command: npx skills add https://github.com/lilliangreenberg/valuations-autonomous_coding --skill feature-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill counts the number of features marked as @failing and writes the count to a JSON file, enabling the autonomous coding harness to determine when the implementation loop should end.

Core Features & Use Cases

  • Count features with the @failing tag across all Gherkin feature files named gherkin.feature_*.feature.
  • Write the result to feature-status.json as { "failing_count": N } to drive loop control.
  • Works with a simple convention: a feature is considered failing if it is tagged with @failing before a Feature: line; if @passing appears first, it is ignored.

Quick Start

Run the feature-status skill after each coding session to update the failing count.

Frequently Asked Questions about feature-status

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

FAQPage Schema
How do I count failing Gherkin features for an autonomous coding loop?▼

To count failing Gherkin features, scan gherkin.feature_*.feature files for the @failing tag and write the total to feature-status.json. This outputs a failing_count value to control when your autonomous coding loop ends.

What is the best way to track failing features in Gherkin feature files?▼

Tracking failing features in Gherkin files involves detecting the @failing tag before the Feature: line. If @passing appears first, the feature is ignored, ensuring only actively failing features are counted in the JSON output.

Does the feature-status convention work with standard Gherkin feature files?▼

Yes, it works with files named gherkin.feature_*.feature. The convention requires a @failing or @passing tag before the Feature: line to determine status and generate the failing_count output.

How do I generate a JSON output of failing feature counts?▼

Generating a JSON output of failing feature counts requires scanning your feature files and writing the result to feature-status.json. The file contains a single object with a failing_count key representing the total.

Why does my failing feature count not update after a coding session?▼

Your failing feature count may not update if feature tags are incorrect. The scanner only detects @failing when it appears before the Feature: line; if @passing appears first, the feature is not counted as failing.

Related Skills

Explore More Software Engineering Skills→
morodomimorodomi
8

tdd-red

Generate failing tests and coordinate parallel workers for TDD RED phases.

Community
Intermediate
VeronikaVashkevichVeronikaVashkevich

aif-loop

Automate iterative PLAN, PRODUCE, PREPARE, EVALUATE, CRITIQUE, and REFINE loops to improve artifacts.

Community
Advanced
jongensutrechtjongensutrecht
1

ralph-loop-light

Repair small code defects with a test-first fix loop validated by ruff and pytest.

Community
Intermediate
kensauruskensaurus
8

hooks-builder

Configure Cursor agent hooks via hooks.json to observe, block, or modify actions.

Community
Intermediate