tommymorgan:review-features

Review Features with Expert Panel

Review any Gherkin scenarios using a panel of domain experts. Accepts feature files, plan files, directories, or glob patterns.

Workflow

Step 1: Detect Input Type and Load Scenarios

Parse the argument to determine input type:

$ARGUMENTS

Input detection:

• Ends in .feature → single feature file
• Ends in .md → plan file (extract Gherkin scenarios)
• Is a directory (no extension, exists as dir) → all .feature files in directory
• Contains * → glob pattern for .feature files

If no argument provided:

1. Check for features/ directory in current project
2. If exists, use features/*.feature
3. Otherwise, error: "No input provided. Specify a .feature file, plan file, directory, or glob pattern."

Load scenarios based on input type:

For .feature files:

• Read file content
• Extract all Scenario: and Scenario Outline: blocks
• Preserve Feature context (Feature name, Background if present)

For .md plan files:

• Read file content
• Extract Gherkin scenarios from User Requirements and Technical Specifications sections
• Scenarios are blocks starting with Scenario: after <!-- TODO --> or <!-- DONE --> markers

For directories:

• Find all .feature files in directory (non-recursive)
• Load scenarios from each file

For glob patterns:

• Expand glob to matching .feature files
• Load scenarios from each file

Step 2: Detect Context from Content

Scan scenario content for keywords to categorize the context:

Keywords → Categories:

• api, endpoint, http, rest, jwt, request, response → backend_service
• hook, bash, cli, git, pre-push, pre-commit, shell → hook
• web, ui, page, component, dashboard, form, button, click → ui_component
• database, schema, migration, table, postgres, sql, query → database_migration
• plugin, command, skill, agent, claude → claude_plugin

Content may have multiple categories.

Store detected categories - experts will use this to filter relevance.