Feature Status Skill

This skill generates status reports for this repository's features based on their maturity level. It reads the status field from feat doc frontmatter and organizes features by maturity.

When to Use This Skill

Reports the maturity declared in each feat doc's frontmatter. It does not read code, so a feature documented as stable and never implemented still reports stable; confirming that the code matches the feat doc is a manual read, and no skill here covers it.

Use this skill when:

• User asks "What's the project status?"
• User asks "What features are stable/experimental/development?"
• User wants to know "What features are ready for production?"
• User asks "Which features are mature vs experimental?"
• User requests "Show feature maturity levels"
• User asks "What features need documentation updates?" (features with unknown status)
• Auditing features to find missing status fields

How Feature Status Works

The skill:

1. Parses frontmatter: Extracts status field from all docs/feat/*.md files
2. Groups by maturity: Organizes features by status level
3. Generates report: Creates formatted tables grouped by status with feature details

Available Commands

Status Report Command

python3 .agents/skills/feat-status/report.py

Generates a comprehensive status report with:

• Features grouped by maturity level (stable, experimental, unstable, development, unknown)
• Unicode tables showing name, type, and description for each feature
• Summary counts by status

Output Format:

Feature Status Report
================================================================================

stable (3)
┌───────────────────┬─────────┬──────────────────────────────────────────────────────────┐
│ Name              │ Type    │ Description                                              │
├───────────────────┼─────────┼──────────────────────────────────────────────────────────┤
│ budget-check      │ feature │ Prose checked against a per-section length budget        │
│ frontmatter-check │ feature │ Frontmatter checked against the schema a corpus declares │
│ structure-check   │ feature │ Section outline checked against a structure file         │
└───────────────────┴─────────┴──────────────────────────────────────────────────────────┘

experimental (2)
┌──────────────┬───────────┬───────────────────────────────────────────────────────┐
│ Name         │ Type      │ Description                                           │
├──────────────┼───────────┼───────────────────────────────────────────────────────┤
│ skill-check  │ feature   │ Skills checked against the Agent Skills specification │
│ spec-dialect │ component │ Namespace specs narrowing the corpus spec             │
└──────────────┴───────────┴───────────────────────────────────────────────────────┘

Summary: 3 stable, 2 experimental (5 total)

Use this when: You need an overview of feature maturity across the project.

When There Is Nothing to Report

Until docs/feat/ holds its first feat doc the script has two quiet ways of saying there is nothing to report. Report the answer and stop: neither is a broken script, and neither is worth a retry.

Query Matching

Status-Related Queries

The skill should be invoked for queries about:

• Project status: "What's the status of the project?", "Show me project health"
• Maturity levels: "What features are stable?", "Which features are experimental?"
• Production readiness: "What features are ready for production?", "What can I use in prod?"
• Development progress: "What features are still in development?", "What's being worked on?"
• Documentation audits: "What features are missing status?", "Which features need updates?"

Not Status Queries

Do NOT use this skill for:

• "How does feature X work?" -> Use /feat-discovery
• "What features are available?" -> Use /feat-discovery
• "Check feat doc format" -> Use /docs-rules-check
• "Does the code do what the doc says?" -> No skill covers this; read the feat doc and the code

Notes

Status Field Values

The status field in feature frontmatter should be one of:

• stable - Production-ready, well-tested, documented
• experimental - Usable but may change, feedback welcome
• unstable - API may change significantly, use with caution
• development - Under active development, not for production
• Missing/unknown - Flagged in report with ⚠ marker

When to Load Full Feat Docs

After running the status report, if user wants details about specific features:

1. Note which features the user is interested in
2. Use /feat-discovery to load full documentation for those features

Example Workflows

Example 1: User Asks About Project Status

Query: "What's the overall status of the project?"

1. Run python3 .agents/skills/feat-status/report.py
2. Review the generated report
3. Summarize findings: X stable features, Y experimental, Z in development
4. Highlight any features with unknown status that need attention

Example 2: User Asks About Production Readiness

Query: "Which features are ready for production?"

1. Run the status report
2. Extract and list features marked as stable
3. If user wants details, use /feat-discovery to load specific stable features

Example 3: User Audits Documentation

Query: "What features are missing status information?"

1. Run the status report
2. Look for features grouped under "⚠ unknown"
3. List features that need status field added to frontmatter
4. Suggest updating those feat docs

Example 4: User Filters by Maturity Level

Query: "Show me all experimental features"

1. Run the status report
2. Extract features from the "experimental" section
3. Present the list with descriptions
4. If user wants more details, use /feat-discovery to load specific feat docs

Common Mistakes to Avoid

Anti-patterns

Best Practices

• Run the report script to get current status
• Use report for overview, /feat-discovery for details
• Flag features with unknown status for documentation updates
• Present status grouped by maturity level for clarity

Next Steps

After generating a status report:

1. Present findings - Summarize status distribution to user
2. Identify actions - Note features needing status updates
3. Provide details - Use /feat-discovery if user wants specifics
4. Suggest improvements - Recommend adding status to unknown features

Script Note

report.py is a standalone script in this repository: a plain python3 script, needing nothing outside the standard library, that carries its own frontmatter parser and its own table renderer. Invoke it exactly as written above, and expect the lorecraft library to replace it.