feature-status

Count features marked as @failing and write to status JSON file. Used to determine when the autonomous coding loop should end.

16 stars

Best use case

feature-status is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Count features marked as @failing and write to status JSON file. Used to determine when the autonomous coding loop should end.

Teams using feature-status should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/feature-status/SKILL.md --create-dirs "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/product/feature-status/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/feature-status/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How feature-status Compares

Feature / Agentfeature-statusStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Count features marked as @failing and write to status JSON file. Used to determine when the autonomous coding loop should end.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Feature Status Skill

## Purpose

This skill counts the number of features marked as `@failing` and writes the count to a JSON file. This is used by the autonomous coding harness to determine when the implementation loop should end (when `failing_count` reaches 0).

## Output File

**File**: `feature-status.json`

**Format**:
```json
{
  "failing_count": 3
}
```

**Loop Termination Logic**:
- If `failing_count > 0` → Continue coding sessions
- If `failing_count == 0` → All features implemented, end loop

## How It Works

### Step 1: Find Feature Files

Use Glob to find all Gherkin feature files:
```
Pattern: gherkin.feature_*.feature
```

### Step 2: Count @failing Tags

For each feature file:
1. Read the first few lines
2. Look for `@failing` tag
3. If found, increment the failing counter

**Tag Detection**:
```
@failing
Feature: Some Feature Name
  ...
```

Read lines until you find either:
- `@failing` → Count this feature as failing
- `@passing` → Skip (not failing)
- `Feature:` line → Stop searching (assume no tag = passing)

### Step 3: Write JSON

Write `feature-status.json` with just the failing count:
```json
{
  "failing_count": <count>
}
```

## Usage

Simply invoke the skill:
```
/feature-status
```

This will:
1. Scan all `gherkin.feature_*.feature` files in the current directory
2. Count how many have `@failing` tags
3. Write the count to `feature-status.json`

## Example Implementation

```python
# Pseudocode for reference
def count_failing_features(directory):
    failing_count = 0

    # Find all feature files
    feature_files = glob("gherkin.feature_*.feature")

    for file in feature_files:
        with open(file) as f:
            for line in f:
                line = line.strip()

                if line.startswith("@failing"):
                    failing_count += 1
                    break
                elif line.startswith("@passing"):
                    break
                elif line.startswith("Feature:"):
                    # No tag found, assume passing
                    break

    return failing_count
```

## Integration with Autonomous Coding Harness

The harness can check the status file to decide whether to continue:

```python
import json

def should_continue_loop():
    with open("feature-status.json") as f:
        status = json.load(f)
    return status["failing_count"] > 0
```

## Best Practices

1. **Run after each coding session** to update the failing count
2. **Commit the status file** to track progress over time
3. **Check before starting a new session** to avoid unnecessary runs
4. **Use as a termination condition** in automation scripts

Related Skills

prioritize-python-3-10-features

16
from diegosouzapw/awesome-omni-skill

Prioritizes the use of new features available in Python 3.12 and later versions.

plan-feature

16
from diegosouzapw/awesome-omni-skill

Plan a new feature from concept to approved implementation plan. Activates Product Council for strategic evaluation, then Feature Council for technical planning. Produces a documented decision and scoped task breakdown. Use when starting any new feature work.

new-feature

16
from diegosouzapw/awesome-omni-skill

Use when starting new feature development - sets up Agent Teams, gathers requirements, creates plan, implements with parallel agents, runs code review/QA/security checks, and commits with conventional commits

Implementing Features

16
from diegosouzapw/awesome-omni-skill

Execute specification-driven implementation with automatic quality gates, multi-agent orchestration, and progress tracking. Use when building features from specs, fixing bugs with test coverage, or refactoring with validation.

genomic-feature-annotation

16
from diegosouzapw/awesome-omni-skill

This skill is used to perform genomic feature annotation and visualization for any file containing genomic region information using Homer (Hypergeometric Optimization of Motif EnRichment). It annotates regions such as promoters, exons, introns, intergenic regions, and TSS proximity, and generates visual summaries of feature distributions. ChIPseeker mode is also supported according to requirements.

full-stack-orchestration-full-stack-feature

16
from diegosouzapw/awesome-omni-skill

Use when working with full stack orchestration full stack feature

feature-investigation

16
from diegosouzapw/awesome-omni-skill

[Investigation] Use when the user asks to investigate, explore, understand, explain, or analyze how an existing feature or logic works. Triggers on keywords like "how does", "explain", "what is the logic", "investigate", "understand", "where is", "trace", "walk through", "show me how".

feature-implementation

16
from diegosouzapw/awesome-omni-skill

[Implementation] Use when the user asks to implement a new feature, enhancement, add functionality, build something new, or create new capabilities. Triggers on keywords like "implement", "add feature", "build", "create new", "develop", "enhancement".

feature-engineering

16
from diegosouzapw/awesome-omni-skill

モデルの性能を向上させるために、既存のデータから新しい特徴量を作成する。

feature-dev-workflow

16
from diegosouzapw/awesome-omni-skill

Complete end-to-end feature development workflow from issue tracking through PR delivery. Use for implementing features, building new functionality, and adding capabilities. Includes requirements discovery, architecture planning, implementation, testing, code review, design audit, and comprehensive validation.

feature-design-assistant

16
from diegosouzapw/awesome-omni-skill

Turn ideas into fully formed designs and specs through natural collaborative dialogue. Use when planning new features, designing architecture, or making significant changes to the codebase.

docker-2025-features

16
from diegosouzapw/awesome-omni-skill

Latest Docker 2025 features including AI Assistant, Enhanced Container Isolation, and Moby 25