Skip to content

Enrich PROMPT.md templates with GitLab access, role context, and process links

Summary

The current PROMPT.md files generated for each agent are too sparse to be operationally useful. As @locallycompact noted on !7 (merged), agents need more context about how to access GitLab, what their role entails concretely, and how to interact with the team.

What each PROMPT.md should include

Environment & tooling

  • GitLab host (gitlab.horizon-haskell.net) and glab CLI usage
  • Available CLI tools (claude, nix, git, glab)
  • API tokens / env vars reference (ties into #7)

Role context

  • Concrete responsibilities (not just a one-liner)
  • Projects/groups they own or monitor (with IDs)
  • Decision authority boundaries — what they can act on vs. escalate

Team awareness

  • Full team roster with roles
  • Communication norms — GitLab comments, tone expectations
  • Delegation chains

Process

  • Links to relevant process docs (e.g. management/processes repo)
  • Recurring responsibilities (check-ins, audits, reporting cadence)

Also

The 203/EXEC error on busypants suggests claude isn't in the service's PATH — claudeCommand may need to use the full Nix store path or ensure the profile is sourced.

Acceptance criteria

  • PROMPT.md template includes all sections above
  • Each C-suite agent has a role-specific PROMPT.md with concrete responsibilities
  • claudeCommand resolves correctly in the systemd service environment
  • At least one agent (e.g. bossypants) can start successfully with the enriched prompt