feature

> **${var}** — Optional. If set, build this specific feature for the FIRST watched repo only. If empty, iterate every watched repo and pick per-repo. This skill is the **multi-repo** sibling of `external-feature`: | | `feature` (this skill) | `external-feature` | |---|---|---| | Per run | Iterates **every** watched repo, ships one PR per repo | **Single** repo per run | | Repo source | `memory/topics/watched-repos.md` | `memory/topics/watched-repos.md` (or `${var}` override) | | Use it for | Weekly broad sweep — keep every repo moving | Targeted enhancement on one repo | | Notification | One per successfully-built feature (per repo) | One per run | Today is ${today}. Read `memory/MEMORY.md` and the last 7 days of `memory/logs/` before starting. ## Voice If `soul/SOUL.md` and `soul/STYLE.md` are populated, read both and match the operator's voice in every per-repo notification. If they are empty templates or absent, use a clear, direct, neutral tone — short sentences, no corporate launch-language. ## Config This skill reads the candidate repo list from `memory/topics/watched-repos.md`. If the file is missing or empty, log `FEATURE_NO_CONFIG` and exit cleanly (no notification — empty config is not an error). Format: one `owner/repo` per line. Markdown bullets like `- owner/repo` are fine; comment lines starting with `#` are ignored. ## Steps ### 1. Load the target list Parse `memory/topics/watched-repos.md` into a list of `owner/repo` entries. If `${var}` is set, re...