feature-reviewlisted

# Feature Review Review all backlog feature.json files in `.aidd/features/` against the target codebase to ensure specs are explicit, consistent, conflict-free, and aligned with project conventions. Automatically rewrites problematic files. ## Usage ``` feature-review ``` Run from within any project that has `.aidd/features/` with feature.json files. ## Workflow ### Phase 1: Discover & Load 1. Find all `feature.json` files under `.aidd/features/*/feature.json` 2. **Separate template features**: Any feature with a `spernakit_version` field is template-owned. These are read-only in derived apps and must NOT be reviewed, modified, or auto-fixed. Include them in the dependency graph (step 4) but skip them for analysis. Report their count separately. Exception: when the target project is the Spernakit template repository itself, `spernakit_version` features ARE in scope for review; skip them only in derived apps. 3. Filter remaining features to those where `status` is `"backlog"` and `passes` is `false` 4. Parse each into memory; reject and report any with invalid JSON 5. Build a full dependency graph from all features (backlog AND completed, including template features) so cross-references can be resolved 6. Report: total features found, template features (skipped), total backlog, total completed ### Phase 2: Learn Codebase Conventions Before judging any feature spec, learn the project's actual conventions by examining: #### Project Structure - Read `package.json` (roo