30eggis 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.mdand.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}.mdand.harness/gotchas/{owning-cxx}.md
Workflow
- Check whether the requester is a CXX. CEO cannot request specialist worker assignment directly.
- Check whether a suitable worker is already hired for that owning CXX.
- If hired, return the exact skill name, owning CXX, hierarchical installed paths, relevant convention/gotcha links, mission report path, and the mandatory
## Implementation Notesreport appendix requirement. - If not hired, suggest
.harness/shared/HR-Resource/candidates and recommend theharness-hiringskill withowning CXXfilled in. - 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.