project-scanlisted

# project-scan — turn latent work into tracked issues/plan ## What it is (and is NOT) Surfaces work that already exists in the repo but isn't tracked, and turns the items you pick into issues on a board. **This targets the CURRENT project** — the opposite of `abios-feedback` (which targets the tool's own repo). Do not confuse them. ## Identity & target (anti-confusion) 1. **Target = the CURRENT repo.** Resolve it: `gh repo view --json nameWithOwner -q .nameWithOwner`. Issues are created ONLY there. 2. **Account matches that repo's owner**, via [[gh-account]]: a personal repo → `GITHUB_TOKEN_PERSONAL`; a `PAL-Devs` (org) repo → `--account pal-devs` (`GITHUB_TOKEN_BUSINESS`). If you get a 403, switch. 3. Never invent issues in another repo or the tool's repo. ## Step 1 — Scan (default sources) Run these read-only scans (ripgrep / the Grep tool). Two defaults matter a lot in practice: **(i) exclude doc-noise dirs** (skill/agent definitions and templates contain hundreds of `- [ ]` that are content, not project work), and **(ii) require the debt marker to follow the `TAG:` / `TAG(` convention** so a Spanish word like "todo" ("everything") is not a false positive. ```bash # shared excludes (build/data + the doc-noise dirs that otherwise dominate results) EXC="-g !**/{node_modules,dist,build,.git,vendor,Tables,outputs}/** \ -g !**/.claude/skills/** -g !**/.specify/** -g !**/templates/**" # a) code debt markers — case-sensitive, must be a TAG (followed by : ( or a TA