feature-status

Scan project artifacts to identify feature progress and blockers.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/bbolek-ap/new-ai-native --skill feature-status-bbolek-ap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-status
Source: https://github.com/bbolek-ap/new-ai-native/tree/main/.claude/skills/feature-status
Command: npx skills add https://github.com/bbolek-ap/new-ai-native --skill feature-status-bbolek-ap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly determine the status of a feature by aggregating project artifacts and backlog data, surfacing progress, blockers, and next actions in a single view.

Core Features & Use Cases

  • Scans .project/features/<slug>/ to determine feature-phase progress and compiles a feature-wide status summary.
  • Reports feature-level artifact completion (requirements, spec, and e2e-scenarios) and per-story progress (plan, impl, QA design, QA auto), plus current step, blockers, and recommended next actions.
  • Accepts a slug or backlog code (e.g., F-01.02) and resolves the slug automatically from .project/backlog/features/ when a backlog code is provided.

Quick Start

Invoke /feature-status <slug-or-code> to view the current status.

Frequently Asked Questions about feature-status

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

FAQPage Schema
How do I track feature progress and identify blockers in my project pipeline?

Feature pipeline tracking works by scanning standard project artifacts like requirements.md, spec.md, and e2e-scenarios.md under .project/features to aggregate phase completion, story progress, and blockers into a single view.

How do I check feature status using a backlog code instead of a slug?

Checking feature status with a backlog code automatically resolves the slug by reading mapping files under .project/backlog/features, allowing you to query progress directly using standard codes like F-01.02.

What project artifacts are required to determine feature phase and current step?

Determining feature phase and current step requires access to standard artifact files including requirements.md, spec.md, and e2e-scenarios.md located within the .project/features/<slug>/ directory structure.

Can I monitor mid-flight pipeline progress without setting up new feature tracking?

Yes, you can monitor mid-flight pipeline progress by scanning existing project artifacts, as the feature status mechanism applies to both new feature work and pipelines already requiring status checks.

How do I report per-story progress for plan, implementation, and QA design phases?

Reporting per-story progress involves scanning project artifacts to compile completion metrics across plan, implementation, QA design, and QA automation phases, alongside surfacing current blockers and recommended next actions.