Resource Manager

Manage worker availability and invocation wording.

Data

• Hired roster: .harness/shared/hr-roster.json
• Keyword index: .harness/shared/resource-index.json
• Candidate pool: .harness/shared/HR-Resource/*/SKILL.md
• Installed hired workers: .claude/skills/{owning-cxx}/{worker}/SKILL.md and .codex/skills/{owning-cxx}/{worker}/SKILL.md
• Mission worker reports: .harness/documents/{mission}/{owning-cxx}/workers/{worker}.md
• Related convention/gotcha links: selected from .harness/conventions/{owning-cxx}.md and .harness/gotchas/{owning-cxx}.md

Workflow

1. Check whether the requester is a CXX. CEO cannot request specialist worker assignment directly.
2. Check whether a suitable worker is already hired for that owning CXX.
3. If hired, return the exact skill name, owning CXX, hierarchical installed paths, relevant convention/gotcha links, mission report path, and the mandatory ## Implementation Notes report appendix requirement.
4. If not hired, suggest .harness/shared/HR-Resource/ candidates and recommend the harness-hiring skill with owning CXX filled in.
5. Keep aliases narrow enough to avoid accidental generic invocation.

Mandatory Worker Report Appendix

Every worker assignment must include only the convention/gotcha links relevant to the assigned task. The owning CXX selects those links from its CXX index files.

Every worker assignment must require the worker to append an English ## Implementation Notes section with these subsections: Design Decisions, Deviations, Tradeoffs, and Open Questions. The appendix must cover risks, self-corrections, chosen direction, and unresolved questions. Use None for empty subsections.