# fspec Feature File Tag Registry ## Tag Categories ### Component Tags (Required) Tags that identify which architectural component a feature belongs to. | Tag | Description | |-----|-------------| | `@agent-registry` | Agent registry and configuration management | | `@algorithm` | Algorithmic components - similarity matching, scoring, deduplication algorithms | | `@cli` | Command-Line Interface | | `@demos` | Demo script functionality and video recording infrastructure | | `@dialog` | Dialog and modal UI components in TUI | | `@file-ops` | File Operations | | `@formatter` | Formatting & Prettification | | `@generator` | Template Generation | | `@git` | Git operations and version control integration | | `@git-integration` | Git integration and version control features | | `@git-ops` | Git operations and version control features | | `@hooks` | Hooks system and execution engine | | `@init` | Initialization and setup features | | `@integration` | Cross-Component Integration | | `@npm` | npm package management and dependency resolution | | `@parser` | Gherkin Parser Integration | | `@templates` | Template generation and transformation system | | `@tui` | Terminal User Interface components and infrastructure | | `@tui-component` | Terminal User Interface components | | `@ui` | User interface and visual components | | `@utils` | Utility functions and helpers | | `@validator` | Validation Logic | | `@viewer` | Attachment viewer component (web-based mermaid/markdown renderer) | | `@virtuallist` | Features related to VirtualList component | **Rule**: Every feature file MUST have at least ONE component tag (may have multiple if cross-component). ### Feature Group Tags (Required) Tags that categorize features by functional area. | Tag | Description | |-----|-------------| | `@accuracy` | Accuracy measurement | | `@agent-compatibility` | Features ensuring correct behavior across all 18 supported AI agents | | `@agent-detection` | Agent detection and runtime configuration features | | `@agent-integration` | Features related to AI agent initialization, detection, and integration | | `@agent-support` | Multi-agent support and agent-specific configurations | | `@ai-assistance` | AI-assisted features for analysis and extraction | | `@answer-question` | Question answering operations | | `@assumption-management` | Assumption tracking in Example Mapping | | `@attachment` | File attachment management features | | `@attachment-management` | Attachment management features for work units | | `@attachment-viewer` | Features related to viewing and rendering work unit attachments | | `@attachments` | Feature related to work unit attachments (diagrams, documents, mockups) | | `@authentication` | Authentication and authorization functionality | | `@auto-blocking` | Automatic blocking state transitions | | `@auto-transition` | Automatic state transitions | | `@blocked-state` | Blocked state handling | | `@board` | Kanban board operations | | `@board-view` | Kanban board visualization | | `@board-visualization` | Kanban board visualization and layout features | | `@bootstrap` | Bootstrap documentation and initialization workflows | | `@bug-reporting` | Bug reporting and issue submission features | | `@bulk` | Bulk operations | | `@bulk-add` | Bulk add operations | | `@bulk-export` | Bulk export operations | | `@bulk-operations` | Bulk Multi-File Operations | | `@burndown` | Burndown chart generation | | `@by-prefix` | Querying or filtering work units by prefix (e.g., AUTH-, DASH-) | | `@calculation` | Calculation operations | | `@cascade` | Cascade operations | | `@checkpoint` | Checkpoint and snapshot management for experimentation and recovery | | `@checkpoint-management` | Checkpoint creation, restoration, and management functionality | | `@code-analysis` | Code analysis and AST research features | | `@code-quality` | Code quality validation and review features | | `@comparison` | Comparison operations | | `@completion` | Completion operations | | `@compound` | Compound query operations | | `@config-management` | Configuration management and settings features | | `@configuration` | Configuration loading and validation | | `@coverage` | Coverage tracking and traceability features | | `@coverage-tracking` | Coverage tracking and traceability from scenarios to tests to implementation code | | `@critical-path` | Critical path analysis | | `@crud` | Create, Read, Update, Delete operations | | `@delete` | Delete operations | | `@dependencies` | Dependency management between work units | | `@dependency-management` | Work unit dependency tracking | | `@diagram` | Features related to diagram management and visualization | | `@diagram-viewer` | Diagram viewing and fullscreen modal features | | `@diff-display` | Diff display and visualization features in TUI | | `@diff-viewer` | Diff visualization and comparison features | | `@discovery-command` | Example Mapping discovery commands | | `@documentation` | Documentation Display | | `@documentation-management` | Documentation generation, updates, and maintenance | | `@epics` | Epic management and high-level work grouping | | `@estimation` | Estimation operations | | `@event-storm` | Event Storming functionality for domain modeling | | `@event-storming` | Event Storming discovery and domain modeling features | | `@example-mapping` | Example mapping for BDD discovery (rules, examples, questions, assumptions) | | `@export` | Export operations | | `@feature-management` | Feature File Operations | | `@filtering` | Filtering and query operations | | `@forecasting` | Forecasting and predictions | | `@formatting` | Auto-Formatting | | `@foundation` | Foundation documentation and schema features | | `@foundation-management` | FOUNDATION.md Operations | | `@generate-scenarios` | Scenario generation from examples | | `@help-system` | Help system and documentation features | | `@help-text` | Help and documentation features | | `@hook-execution` | Hook execution and lifecycle management | | `@impact-analysis` | Impact analysis and dependency chains | | `@infrastructure` | Core infrastructure and shared utilities | | `@interaction` | User interaction and input handling features | | `@interactive-cli` | Interactive CLI features and TUI workflows | | `@kanban` | Kanban board and workflow management | | `@language-support` | Programming language support and integration | | `@list` | List operations | | `@metrics` | Metrics and measurements | | `@metrics-estimation` | Metrics and estimation tracking | | `@migration` | Migration & Data Transformation | | `@modification` | Feature Modification Operations | | `@multi-agent-support` | Features related to supporting multiple AI coding agents beyond Claude | | `@navigation` | Navigation and keyboard interaction features in the TUI | | `@operations` | General operations | | `@orchestration` | Command orchestration features that coordinate multiple operations | | `@parent-child` | Parent-child work unit relationships | | `@prediction` | Prediction operations | | `@prefix-epic` | Prefix and epic management | | `@prefixes` | Work unit ID prefix management | | `@priority` | Priority management and reordering | | `@progress` | Progress tracking and reporting | | `@project-management` | Project management features including work units, epics, and workflow | | `@quality-assurance` | Quality assurance and code review features | | `@query` | Query operations for searching and filtering | | `@query-reporting` | Query and reporting features | | `@querying` | Query & Search Operations | | `@read` | Read operations | | `@read-only` | Read-Only Operations | | `@recommendations` | Recommendation features providing suggestions based on historical data | | `@release-management` | Release and version management features | | `@remove` | Remove operations | | `@repair` | Data repair operations | | `@report-bug` | Features related to reporting bugs to GitHub | | `@reporting` | Reporting and statistics | | `@research` | Research and discovery tools | | `@research-integration` | Research tool integration and plugin system features | | `@research-tools` | Research tool system features and integrations | | `@reverse-acdd` | Features related to reverse ACDD for documenting existing codebases | | `@safety` | Safety and security features preventing accidental operations | | `@scaffolding` | Project Setup & Templates | | `@scalability` | Scalability and performance optimization features | | `@scenario-deduplication` | Scenario deduplication and refactoring detection features | | `@scenario-generation` | Features related to generating scenarios from example mapping | | `@schema-design` | Schema design and data structure definition | | `@security` | Security-related features and bug fixes | | `@soft-dependency` | Soft dependency relationships | | `@state-enforcement` | State transition enforcement | | `@state-history` | State history tracking | | `@state-management` | Work unit state management and transitions | | `@state-transition` | State transition operations | | `@statistics` | Statistical analysis | | `@strategy-detection` | Strategy detection and selection for reverse ACDD workflows | | `@system-reminders` | System reminder and anti-drift pattern features | | `@tag-management` | TAGS.md Operations | | `@test-coverage` | Test coverage tracking and validation features | | `@test-maintenance` | Test maintenance and quality assurance features | | `@testing` | Testing and quality assurance features | | `@tool-discovery` | Tool discovery and listing features | | `@tracking` | Metric tracking operations | | `@ui-enhancement` | TUI user interface enhancements and visual improvements | | `@ui-refinement` | UI refinement and enhancement operations | | `@update` | Update operations | | `@utility` | Utility & Helper Commands | | `@validation` | Syntax & Structure Validation | | `@velocity` | Velocity calculation | | `@version-management` | Features related to version checking, upgrading, and file synchronization | | `@video-recording` | Video recording and demo playback features | | `@visual-design` | Visual design and branding features | | `@visualization` | Data visualization | | `@work-management` | Work unit management and Kanban workflow operations | | `@work-unit-linking` | Scenarios related to work unit and feature file linking functionality | | `@work-unit-management` | Work unit lifecycle and status management | | `@work-units` | Work unit CRUD operations | | `@workflow` | Workflow and state transition features | | `@workflow-automation` | Workflow automation and lifecycle integration utilities | | `@workflow-command` | ACDD workflow-related commands | **Rule**: Every feature file MUST have at least ONE feature group tag. ### Technical Tags Tags for specific technical concerns or architectural patterns. | Tag | Description | |-----|-------------| | `@ai-assisted` | Features using AI-driven analysis and interaction | | `@ai-driven` | AI-driven interactive and conversational commands | | `@ai-guidance` | Features that provide contextual guidance to AI agents | | `@anti-drift` | Features that prevent AI drift and maintain workflow discipline | | `@ast` | Abstract Syntax Tree | | `@ast-analysis` | AST-based code analysis features | | `@auth-001` | Work unit identifier for authentication features (example in example-mapping feature) | | `@auto-create` | Scenarios testing automatic file creation when files are missing | | `@automation` | Automated workflow operations and state transitions | | `@backward-compatibility` | Features ensuring compatibility with older file formats or legacy systems | | `@bdd` | Behavior-Driven Development methodology | | `@browser-integration` | Features requiring browser launcher integration | | `@build` | Build system configuration and bundling | | `@bundling` | Features related to build bundling and module resolution | | `@checkpoints` | Git checkpoint and state restoration features | | `@cleanup` | Cleanup and resource management features | | `@code-review` | Code review and quality analysis features | | `@codex` | Codex AI agent integration features | | `@command-registration` | CLI command registration features | | `@concurrency` | Concurrent access coordination and file locking mechanisms | | `@config` | Configuration loading and management features | | `@cucumber-parser` | Cucumber Parser Integration | | `@cucumber-style` | Cucumber-style step definition and matching patterns | | `@dart` | Dart language and Flutter framework features | | `@data-integrity` | Data integrity validation and consistency checks | | `@data-model` | Features related to data models, schemas, and data structure transformations | | `@ddd` | Domain-Driven Design concepts, Event Storming, bounded contexts, aggregates | | `@destructive-action` | Features requiring confirmation dialogs for destructive operations (delete, overwrite, etc.) | | `@development-tools` | Development tooling and utilities | | `@discovery` | BDD discovery technique used before writing Gherkin scenarios | | `@email` | Email-related functionality | | `@error-handling` | Error Handling | | `@eslint` | ESLint configuration and linting | | `@file-discovery` | File discovery and pattern matching functionality | | `@file-initialization` | Scenarios testing initialization of project files | | `@file-structure` | File and directory structure validation | | `@file-system` | File System Operations | | `@file-watcher` | File system watching and monitoring features | | `@file-watching` | Features using file system watchers (fs.watch) for change detection | | `@flexbox` | Flexbox layout implementation and responsive design | | `@format-check` | Format and style checking | | `@fullscreen` | Fullscreen modal and overlay features | | `@function-signature` | Function signature validation and checking | | `@gherkin` | Gherkin Specification Compliance | | `@github-integration` | Features integrating with GitHub API or URLs | | `@graceful-degradation` | Features that gracefully handle missing or invalid data | | `@guidance` | Features that provide AI guidance/prompts rather than code implementation | | `@http-server` | HTTP server implementation and lifecycle management | | `@idempotent` | Operations that can be safely repeated without changing results | | `@initialization` | File and system initialization features | | `@ink` | Ink (React for CLIs) rendering engine | | `@interactive` | Interactive terminal UI features using Ink | | `@internal` | Internal Utility | | `@investigation` | Investigation and research tasks for evaluating technical approaches | | `@ipc` | Inter-process communication features using Unix sockets or named pipes | | `@isomorphic-git` | Uses isomorphic-git library for pure JavaScript git operations | | `@jira` | JIRA integration and API features | | `@json-backed` | JSON-Backed Documentation | | `@json-output` | JSON format output support | | `@json-schema` | JSON Schema Validation | | `@keyboard-navigation` | Keyboard input and navigation features | | `@kotlin` | Kotlin language and JVM features | | `@layout` | Layout and visual presentation features | | `@learning` | Machine learning and adaptive features based on usage patterns | | `@logging` | Logging and diagnostics features | | `@markdown` | Markdown rendering and processing | | `@markdown-formatting` | Markdown formatting and rendering features | | `@marked` | Marked library for markdown parsing | | `@mermaid` | Mermaid Diagram Support | | `@modal` | Modal overlay and dialog components | | `@mouse-events` | Features that handle mouse and trackpad events | | `@multi-agent` | Multi-agent compatibility features and agent-specific customizations | | `@outside-in-bdd` | Outside-in BDD approach using personas and behavior-first thinking | | `@pattern-detection` | Features involving pattern detection and analysis from historical data | | `@performance` | Performance optimization and efficiency features | | `@platform-agnostic` | Features supporting multiple platforms (Python, Rust, Go, JavaScript, etc.) | | `@plugin-system` | Plugin architecture and dynamic module loading | | `@prettier` | Prettier configuration and code formatting | | `@push` | Push notification functionality | | `@query-api` | Tree-sitter Query API features using S-expression pattern matching | | `@react` | React framework and component lifecycle features | | `@real-time` | Features with real-time data synchronization and live updates | | `@resilience` | Error handling and graceful degradation features | | `@responsive` | Components that respond to viewport or terminal dimension changes | | `@reverse-engineering` | Reverse engineering existing code to create specifications | | `@review` | Code review and quality analysis | | `@runtime` | Runtime behavior and dynamic configuration | | `@schema-validation` | JSON Schema validation features and commands | | `@search` | Search and query functionality for finding scenarios, work units, and code patterns | | `@server` | Server-side components and HTTP endpoints | | `@session-based` | Session-based interactive command pattern (similar to discover-foundation) | | `@setup` | Setup and initialization commands | | `@similarity-matching` | Text similarity and matching algorithms | | `@slash-command` | Slash command features for Claude Code | | `@slash-commands` | Claude Code slash command implementations | | `@sms` | SMS-related functionality | | `@stable-indices` | Stable indices system for maintaining unique IDs across soft-delete operations | | `@step-validation` | Step-level validation and Gherkin step matching | | `@strategy-planning` | Strategy planning and decision-making features that guide user choices | | `@system-reminder` | Anti-drift pattern for AI agents using contextual reminders | | `@template` | Template System | | `@template-generation` | Template and documentation generation | | `@testing-framework` | Testing framework and infrastructure features | | `@toml` | TOML configuration file parsing and manipulation | | `@traceability` | Scenario-to-test-to-implementation traceability and coverage tracking | | `@trackpad` | Trackpad and touchpad input handling with smoothing and gesture support | | `@tree-sitter` | Tree-sitter library for language-agnostic AST parsing | | `@type-system` | Work unit type system features for categorizing work (story, task, bug) | | `@typescript` | TypeScript-specific features and configuration | | `@ui-formatting` | UI formatting and layout features | | `@ui-rendering` | UI rendering and layout issues | | `@versioning` | Version management and migration features | | `@vitest` | Vitest testing framework related features | | `@web` | Web-based features and browser functionality | | `@worker-threads` | Features involving Node.js worker threads for parallel processing | | `@zoom` | Zoom and scaling functionality for diagrams and visualizations | | `@zoom-pan` | Zoom and pan interaction features | | `@zustand` | Zustand state management library | **Rule**: Use technical tags to highlight specific architectural concerns. ### Platform Tags Tags for platform-specific scenarios or cross-platform requirements. | Tag | Description | |-----|-------------| | `@claude-code` | Features specific to Claude Code integration | | `@cross-platform` | Cross-Platform Requirement | | `@linux` | Linux-Specific | | `@macos` | macOS-Specific | | `@windows` | Windows-Specific | **Rule**: Use platform tags when a scenario has platform-specific behavior or requirements. ### Priority Tags Tags indicating implementation priority or criticality. | Tag | Description | |-----|-------------| | `@breaking-change` | Breaking changes requiring major version bump (v2.0+) | | `@critical` | Critical Priority - Must Have | | `@high` | High Priority - Should Have | | `@low` | Low Priority - Future Enhancement | | `@medium` | Medium Priority - Nice to Have | | `@p1` | Phase 1 - Core foundation and infrastructure | | `@phase-1` | Phase 1 features - core functionality | **Rule**: Use priority tags to guide implementation order within a phase. ### Status Tags Tags tracking development status of features. | Tag | Description | |-----|-------------| | `@auth-002` | Example work unit for authentication testing | | `@auth-999` | Non-existent work unit for testing error handling | | `@blocked` | Blocked | | `@bug` | Bug fix work units | | `@bug-fix` | Marks bug fixes and corrections to existing functionality | | `@deprecated` | Deprecated | | `@done` | Complete | | `@enhancement` | Feature enhancement or improvement | | `@exmap-001` | Work unit: Redesign Example Mapping to match BDD technique | | `@init-001` | Work unit: Add ensureWorkUnitsFile to ALL 48+ commands | | `@partial` | Partially implemented feature - work in progress | | `@refactor` | Code refactoring and technical improvements | | `@refactoring` | Code that needs refactoring | | `@remind-008` | Feature file prefill detection and CLI enforcement work unit | | `@technical-debt` | Technical debt that should be addressed | | `@test-001` | Example test work unit | | `@todo` | To Do | | `@wip` | Work In Progress | **Rule**: Update status tags as features progress through development lifecycle. ### Testing Tags Tags for test-related scenarios and requirements. | Tag | Description | |-----|-------------| | `@blocking` | Operations that block workflow progression | | `@circular-dependency` | Circular dependency detection tests | | `@complex-command` | Complex command with multiple modes and options | | `@confirmation` | Tests confirmation messages and user feedback | | `@consistency` | Data consistency validation | | `@duplicate` | Duplicate detection tests | | `@e2e` | End-to-end integration tests | | `@e2e-test` | End-to-End Test Required | | `@edge-case` | Edge case tests - validation of boundary conditions and unusual scenarios | | `@happy-path` | Happy path test scenarios | | `@integration-test` | Integration Test Required | | `@main-help` | Main help menu tests | | `@manual-test` | Requires Manual Testing | | `@medium-command` | Medium complexity command with multiple options | | `@overwrite` | Tests overwrite behavior (file replacement without prompts) | | `@prerequisites` | Prerequisite validation scenarios | | `@regression` | Regression tests - comprehensive validation of existing functionality | | `@simple-command` | Simple command with minimal options | | `@smoke` | Smoke tests - quick validation of critical functionality | | `@test-infrastructure` | Test infrastructure and framework code | | `@test-isolation` | Test isolation and concurrent execution | | `@unit-test` | Unit Test Coverage Required | | `@unregistered-scenario-tag` | Example tag used in test scenarios to demonstrate error handling | | `@unregistered-tag1` | Example tag used in test scenarios to demonstrate error handling | | `@unregistered-tag2` | Example tag used in test scenarios to demonstrate error handling | | `@warning` | Operations that produce warnings | **Rule**: Use testing tags to indicate what level of testing is required for a scenario. ### Automation Tags Tags for automation integration and agentic coding workflows. | Tag | Description | |-----|-------------| | `@acdd` | Acceptance Criteria Driven Development | | `@cli-integration` | CLI integration and workflow automation features | | `@discovery-workflow` | Discovery workflow and bootstrapping processes | | `@draft-driven` | Draft-driven development and feedback loops | | `@execa` | Child process execution integration point | | `@spec-alignment` | Specification Alignment | **Rule**: Use automation tags to indicate integration points with automation systems and lifecycle hooks. --- ## Tag Combination Examples ### Example 1: Phase 1 Feature File Creation ```gherkin @phase1 @cli @generator @feature-management @gherkin @cross-platform @critical @unit-test @integration-test Feature: Create Feature File with Template Feature: Create Feature File with Template ``` **Interpretation**: - Phase 1 feature - Belongs to CLI and generator components - Part of feature management functionality - Ensures Gherkin compliance - Must work on all platforms - Critical priority (core functionality) - Requires both unit and integration tests ### Example 2: Phase 2 Tag Registry Validation ```gherkin @phase2 @validator @tag-management @validation @error-handling @high @integration-test @hook Feature: Validate Feature File Tags Against Registry Feature: Create Feature File with Template ``` **Interpretation**: - Phase 2 feature - Belongs to validator component - Part of tag management functionality - Includes validation and error handling - High priority - Requires integration tests - Called from lifecycle hooks ### Example 3: Phase 3 Advanced Querying ```gherkin @phase3 @cli @querying @parser @ast @medium @unit-test @e2e-test Feature: Advanced Scenario Search and Filtering Feature: Create Feature File with Template ``` **Interpretation**: - Phase 3 feature - Belongs to CLI and querying components - Uses parser and AST processing - Medium priority - Requires unit and end-to-end tests --- ## Usage Guidelines ### Required Tag Combinations - One Phase Tag: @phase1, @phase2, or @phase3 - At least One Component Tag: @cli, @parser, @generator, @validator, etc. - At least One Feature Group Tag: @feature-management, @tag-management, etc. **Minimum Example**: ```gherkin @phase1 @cli @feature-management Feature: Minimal Valid Feature ``` ### Recommended Tag Combinations - Required tags (phase, component, feature group) - Technical tags for key architectural concerns - Platform tags if platform-specific - Priority tag for implementation planning - Testing tags for test strategy - Automation integration tags if applicable **Recommended Example**: ```gherkin @phase1 @cli @parser @validation @gherkin @cucumber-parser @error-handling @cross-platform @critical @integration-test @hook Feature: Gherkin Syntax Validation ``` ### Tag Ordering Convention - Phase tag - Component tag(s) - Feature group tag(s) - Technical tags - Platform tags - Priority tag - Status tag - Testing tags - Automation integration tags **Example**: ```gherkin @phase2 @cli @validator @tag-management @validation @mermaid @cross-platform @high @wip @integration-test @hook Feature: FOUNDATION.md Mermaid Diagram Validation ``` --- ## Adding New Tags ### Process **Identify Need**: Determine if existing tags are insufficient **Check Registry**: Verify tag doesn't already exist in this document **Define Tag**: Create clear description and usage guidelines **Update TAGS.md**: Add to appropriate category table **Document Examples**: Show how tag should be used **Use fspec**: Register tag using `fspec register-tag` command **Apply**: Use tag in feature files ### Naming Conventions - Use lowercase - Use hyphens for multi-word tags (@cross-platform, not @crossplatform) - Be specific and descriptive (@cucumber-parser not @parser-integration) - Avoid redundancy (@cli-commands → just @cli) - Keep concise (prefer @wip over @work-in-progress) ### Anti-Patterns ❌ **DON'T**: - Create overlapping tags (@validate and @validation → use @validation) - Use vague tags (@important → use @critical, @high, etc.) - Create single-use tags (@login-feature → use combination of existing tags) - Mix concerns (@cli-validation → use @cli @validation) ✅ **DO**: - Reuse existing tags through combinations - Create specific technical tags (@gherkin, @mermaid) - Document new tags thoroughly - Use tags to enable filtering and reporting --- ## Common Tag Queries **All Phase 1 features**: ```bash fspec list-features --tag=@phase1 ``` **Critical validation features**: ```bash fspec list-features --tag=@validation --tag=@critical ``` **Features requiring integration tests**: ```bash fspec list-features --tag=@integration-test ``` **Lifecycle hook integration points**: ```bash fspec list-features --tag=@hook ``` **Cross-platform CLI features**: ```bash fspec list-features --tag=@cli --tag=@cross-platform ``` --- ## Tag Statistics ### By Phase | Phase | Total Features | Complete | In Progress | Planned | |-------|----------------|----------|-------------|---------| | Phase 1 | 5 | 5 | 0 | 0 | | Phase 2 | 7 | 7 | 0 | 0 | | Phase 3 | 2 | 2 | 0 | 0 | | Phase 4 | 4 | 4 | 0 | 0 | | Phase 5 | 7 | 7 | 0 | 0 | | Phase 6 | 3 | 3 | 0 | 0 | | Total | 28 | 28 | 0 | 0 | ### By Component | Component | Feature Count | Percentage | |-----------|---------------|------------| | @cli | 28 | 100% | | @parser | 3 | 11% | | @generator | 1 | 4% | | @validator | 1 | 4% | | @formatter | 1 | 4% | | @file-ops | 1 | 4% | ### By Feature Group | Feature Group | Feature Count | Percentage | |---------------|---------------|------------| | @feature-management | 11 | 39% | | @modification | 11 | 39% | | @tag-management | 7 | 25% | | @querying | 6 | 21% | | @foundation-management | 3 | 11% | | @bulk-operations | 3 | 11% | | @validation | 3 | 11% | | @documentation | 2 | 7% | | @read-only | 2 | 7% | | @formatting | 1 | 4% | | @utility | 1 | 4% | _Last updated: 2025-11-18T02:38:59.960Z_ **Update Command**: `fspec tag-stats` --- ## Validation ### Rules - **Registry Compliance**: All tags in feature files MUST exist in this TAGS.md - **Required Tags**: Every feature MUST have phase + component + feature group tags - **No Orphans**: Tags in TAGS.md should be used in at least one feature file - **Consistent Naming**: Follow tag naming conventions strictly ### Commands **Validate all feature files**: ```bash fspec validate-tags ``` **Check for orphaned tags**: ```bash fspec tag-stats --show-orphans ``` **Validate specific feature**: ```bash fspec validate login.feature ``` --- ## References - [Gherkin Reference](https://cucumber.io/docs/gherkin/reference/#tags) - [Cucumber Tag Expressions](https://cucumber.io/docs/cucumber/api/#tag-expressions)