Skip to content
Back to skills

047 Description E49043e4

ASecurity

Mark a feature as completed (passed) or failed

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 11, 2026
testingtestingapi

Works with

  • api

Security analysis

A100/100

Scanned October 11, 2026

npx -y skills add tools-only/X-Skills --skill 047-description_e49043e4 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 047 Description E49043e4?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for 047 Description E49043e4
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tools-only-047-description-e49043e4/badge)](https://www.skillsdirectory.com/skills/tools-only-047-description-e49043e4)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

SKILL.md
---
description: Mark a feature as completed (passed) or failed
allowed-tools: Read, Write, Edit
argument-hint: [feature-id] [passed|failed] [optional-notes]
---

# Long-Running Agent - Mark Feature Status

Update the status of a feature in the feature list.

## Arguments

- **$1** (feature-id): The feature ID (e.g., F012)
- **$2** (status): `passed` or `failed`
- **$3+** (notes): Optional notes about the completion or failure

## Example Usage

```
/lra:mark-feature F012 passed
/lra:mark-feature F015 failed API rate limiting not yet implemented
/lra:mark-feature F023 passed Implemented with Redis caching
```

## Your Task

1. Read `.lra/feature-list.json`

2. Find the feature with ID = `$1`
   - If not found, report error and list available IDs

3. Update the feature:

**If marking as `passed`:**
```json
{
  "status": "passed",
  "completed_at": "ISO timestamp",
  "notes": "$3 (if provided)"
}
```

**If marking as `failed`:**
```json
{
  "status": "failed",
  "completed_at": null,
  "notes": "$3 (required - explain why it failed)"
}
```

4. Save the updated feature-list.json

## Important Rules

- **ONLY mark as passed after TESTING the feature end-to-end**
- **It is UNACCEPTABLE to mark features as passed without verification**
- **Do NOT remove or edit the feature description or acceptance criteria**
- **Failed features should include clear notes about what went wrong**

## Output

Confirm the status update:

```
✅ Feature Updated

ID: F012
Description: User can create a new account
Status: passed ✓
Completed: 2024-01-15T14:32:00Z
Notes: Implemented with email verification

Progress: 6/42 features completed (14%)
```

Or for failures:

```
⚠️ Feature Marked as Failed

ID: F015
Description: API rate limiting per user
Status: failed ✗
Notes: API rate limiting not yet implemented - needs Redis setup first

This feature remains in the backlog for future implementation.
```

## Execution Instructions

**Agent Selection**: To execute this LRA task, use the following approach:
- Primary: Use `general-purpose` agent with task management and state persistence capabilities
- Or use `plan` agent for complex multi-step workflows

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.