speckit-bugfix-verifylisted

# Verify Bugfix Consistency Verify that all spec artifacts are consistent after bugfix patches — checks that new requirements have corresponding plan sections and tasks, reopened tasks are not still marked complete, and no orphaned references exist. ## User Input ```text $ARGUMENTS ``` You **MUST** consider the user input before proceeding (if not empty). The user may specify a bug ID to verify (e.g., "BUG-001") or "all" to check everything. ## Prerequisites 1. Verify a spec-kit project exists by checking for `.specify/` directory 2. Locate the current feature's spec directory 3. Verify at least `spec.md` exists ## Outline 1. **Load all artifacts**: Read from the current feature directory: - `spec.md` — the source of truth - `plan.md` — implementation plan (if exists) - `tasks.md` — task breakdown (if exists) - `specs/{feature}/bugs/*.md` — all bug reports 2. **Check bug report status**: For each bug report file: | Check | Pass Condition | Fail Condition | |-------|---------------|----------------| | Report exists | Bug file is in `bugs/` directory | Missing bug file | | Report is patched | Has `**Status**: Patched` marker | Still `Open` or missing status | | Patch date present | Has `**Patched**: [DATE]` entry | Missing patch date | 3. **Verify spec.md consistency**: For each bugfix note in spec.md: - New requirements have clear acceptance criteria - Strikethrough items have a reason documented - No duplicate requirements introd