feature-status

Parse YAML frontmatter from docs/features/*.md and group features by status into a formatted table.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/edgeandnode/ampup --skill feature-status-edgeandnode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-status
Source: https://github.com/edgeandnode/ampup/tree/main/.agents/skills/feature-status
Command: npx skills add https://github.com/edgeandnode/ampup --skill feature-status-edgeandnode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aggregates feature metadata from docs to provide a concise project status overview.

Core Features & Use Cases

  • Parse YAML frontmatter from docs/features/*.md to collect feature metadata.
  • Group features by maturity levels (stable, experimental, unstable, development, unknown) for clear visibility.
  • Render a readable table in the terminal and support auditing of missing status fields.

Quick Start

Run the report script in this skill's directory to generate the current feature status overview.

Frequently Asked Questions about feature-status

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

FAQPage Schema
How do I generate a feature maturity report from markdown frontmatter?

Parsing YAML frontmatter from markdown docs generates a feature maturity report by grouping features by status. It outputs a formatted table with name, type, and description for quick project status visibility.

How does YAML frontmatter parsing handle missing status fields?

When parsing YAML frontmatter, missing status fields are marked as unknown for auditing. This ensures incomplete feature documentation is flagged and accounted for in the final maturity report.

What maturity levels are supported when grouping features by status?

Features are grouped by stable, experimental, unstable, development, and unknown maturity levels. These status categories provide a concise overview of feature readiness in the project documentation.

Can I audit feature documentation completeness using frontmatter metadata?

Yes, parsing frontmatter metadata audits feature documentation completeness by detecting missing status fields. Features lacking a status are assigned an unknown maturity level to highlight documentation gaps.

What is the best way to aggregate feature metadata from multiple markdown files?

Parsing YAML frontmatter from multiple markdown files is the best way to aggregate feature metadata. It groups extracted data to render a readable table summarizing feature status and types.