Find work — Home Assistant Homelab

SkillProductivity

Orient on Home Assistant Homelab, scout read-only work sources (docs/issues + docs/plans, local_todo Issues/Tasks/Ideas ICS, shopping list, docs, TODO markers), rank a backlog with evidence, and emit launch briefs. Use when the user says find work, /find-work, what's left to do, or what should I work on.

Available today. Use it from your connected AI after setup.

Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.

Then ask your AI: use the Find work skill

What this skill tells your AI

The instructions your AI receives, as published by apocrathia/home-assistant-config in .agents/skills/find-work/SKILL.md and read by ahel’s review.

Read-only discovery. Orient, scout sources, rank and dedupe, then recommend with launch briefs. Do not edit files, create worktrees, commit, push, or open PRs. Git is operator-owned (operator-owned-git.md).

Authoritative source rules live in .agents/context/work-sources.md — follow that module; this skill is the workflow around it.

Workflow

- [ ] 1. Orient (project model + constraints)
- [ ] 2. Scout sources (parallel, read-only)
- [ ] 3. Rank and dedupe into a backlog
- [ ] 4. Recommend top items + emit launch briefs
- [ ] 5. Hand off — wait for operator pick (or continue if they say so)

1. Orient

Read these (skim is fine):

FileWhy
AGENTS.mdRouter
.agents/context/README.mdContext hub
.agents/context/constraints.mdHard limits
.agents/context/traps.mdKnown pitfalls
.agents/context/work-sources.mdWhat to scan + dual-channel issue rules
.agents/context/development-loop.mdLap shape (find → implement → handoff)

2. Scout sources

Scan in parallel. Every candidate needs source + evidence. Missing sources are non-fatal — note and continue.

SourceHowNotes
Docs issuesdocs/issues/*.md (skip README, _template)Agent ledger. Honor frontmatter status. Cite title + path + found_at.
Docs plansdocs/plans/*.md (skip README, _template)How-work. Honor status; note checkbox progress when cheap.
Local Todo Issues.storage/local_todo.issues.ics (STATUS:NEEDS-ACTION)Human-reported. Cite SUMMARY + UID.
Local Todo Tasks.storage/local_todo.tasks.ics (STATUS:NEEDS-ACTION)Human-scoped. Cite SUMMARY + UID.
Local Todo Ideas.storage/local_todo.ideas.ics (STATUS:NEEDS-ACTION)Speculative. Cite SUMMARY + UID.
Shopping listRead .shopping_list.jsonLegacy; still valid.
Other docsdocs/README.md, docs/packages.md, docs/projects.md, docs/CONTRIBUTING.mdDocumented follow-ups outside the issue/plan ledgers.
TODO markers# TODO: under packages/** and docs/**Cite path + line.
Live HA (optional)Home Assistant MCP / live contextPrefer when it clarifies broken entities/automations. Discovery stays read-only.
GitHub (optional)Issues/PRs if MCP/gh availableNice-to-have; do not require or block on it.

Do not scan

docs/backlog/roadmap.md, docs/design/technology.md (unless they exist and operator asked), ponytail: comments, Linear, Notion, sync-main.sh, Macroscope, agent-loop state, PR eligibility scripts. Do not invent worktrees.

Docs issues / plans

Per work-sources.md and the READMEs under docs/issues/ and docs/plans/. Skip closed/wontfix/superseded/promoted issues and done plans.

Local Todo + shopping list

Same read-only jq/python snippets as in work-sources.md. Never write those files.

TODO scan

rg -n '# TODO:' packages docs

3. Rank and dedupe

TierWhat
1Broken / urgent: open docs/issues bugs + human Local Todo Issues
2Open docs/plans with work left; issues ready for plan authoring
3Open Local Todo Tasks; incomplete shopping-list items
4# TODO: markers; other documented follow-ups
5Open Local Todo Ideas; speculative / nice-to-have

Dedupe: same outcome from two sources → one backlog row, cite both sources.

4. Recommend + launch briefs

Hand-off routing

SituationNext
Vague title / unclear acceptancealignment
Issue has acceptance, no planPlan authoring → docs/plans/<slug>.md + set issue plan:
Scoped config/package/automation changeimplement-change
Out-of-scope gap found while scoutingfile-issue (agent channel)
YAML validity / package layout / broken automationconfig-validate, package-organize, automation-debug
Deep HA config questionsha-config-expert
Complex automation designautomation-architect

Stop at: implement → validate → "operator validates & commits". Never recommend commits, pushes, PRs, or worktrees.

Launch brief template

## Launch brief: <short title>

Source: <docs/issues | docs/plans | local_todo issues|tasks|ideas | shopping-list | docs | TODO | HA live | GitHub>
Evidence: <path + title | list + SUMMARY + UID | name + id | path:line>
Tier: <1–5>
Next skill: <alignment | file-issue | plan authoring | implement-change | …>

### Goal
<one paragraph>

### Acceptance
- [ ] …

### Constraints
- Dual channel: agent issues → docs/issues; human → Local Todo (read-only)
- Operator-owned git — no commit/push/PR/worktree
- Never write `.storage/local_todo.*.ics` or `.shopping_list.json`
- Validate before handoff (config-validate where relevant)
- Stop at: operator validates & commits

### Paste into new chat (or continue here)
<self-contained prompt the next agent can run cold>

5. Hand off

Present the backlog and briefs. Wait for the operator to pick an item unless they already said to continue with the top recommendation.

Do not start implementation during find-work.

Signals

GitHub stars
179
Forks
32
Last commit
Sep 2026
Advanced
Item type
skill
Key
find-work
Source
github.com/apocrathia/home-assistant-config