feature

# Feature Management Manage Runners' feature pipeline: specs live in `docs/features/`, tracking lives in GitHub Issues with the `feature` label. ## Usage `/feature <action> [args]` ### Actions #### `new <name>` Create a new feature from scratch. 1. Ask the user to describe the feature (motivation, scope, key decisions). 2. Assign the next available number by checking existing files in `docs/features/`. 3. Create `docs/features/{number}-{slug}.md` with sections: Motivation, Scope, Implementation Phases, Verification. 4. **Pick a priority** (see Priority below). If the user didn't state one, propose one and confirm before filing. Don't file unlabeled. 5. Create a GitHub Issue with labels `feature` and the chosen `P0`/`P1`/`P2`/`P3`: - Title: `feat: <short description>` - Body: Motivation, Scope summary, Implementation Phases, and a reference back to the spec file. - Command shape: `gh issue create --label feature --label P1 --title "…" --body "…"` 6. Update `docs/features/README.md` to include the new spec. 7. Report the spec path, issue URL, and assigned priority. #### `list` Show all features, sorted by priority. 1. Fetch open features with priority + metadata as JSON so they can be sorted: `gh issue list --label feature --state open --limit 50 --json number,title,labels,createdAt,assignees` 2. List all spec files in `docs/features/` (excluding README). 3. Sort the rows by priority (`P0` first, then `P1`, `P2`, `P3`, then unlabeled-by-priority last). Withi...