Skip to main content
Version: v1.0

Team workflow

Agentbriefer separates shared repository policy from personal conveniences.

Commit shared state​

Commit agentbriefer.yaml. It contains the complete developer/project policy, output selection, stop rules, custom instructions, and installed skill IDs.

Teams may also commit generated instruction files so agents receive guidance immediately after checkout. If the team chooses not to commit them, document agentbriefer sync as a setup step.

Materialized .agentbriefer/skills/ files are reproducible from the config and CLI catalog. Decide as a team whether readable copies should be committed.

Keep personal state personal​

Developer profiles and skill profiles live in the user's configuration directory and are not part of the repository. Applying either writes explicit values back to project YAML, keeping the shared result visible.

skill list --role and --recommended are browsing filters only. Two teammates can use different filters without changing installed project state.

Suggested review process​

When agentbriefer.yaml changes, review it like application configuration:

  • Does a policy conflict with the project's risk level?
  • Is a new stop rule precise enough to act on?
  • Does an installed skill fit the actual stack?
  • Will changing outputs add or remove tool-specific files?
  • Were generated files synchronized in the same change?

Example pull-request check​

cargo test --all-targets       # project-specific checks, when applicable
agentbriefer sync
agentbriefer doctor
git diff -- agentbriefer.yaml CLAUDE.md AGENTS.md .cursor .github

Because doctor warnings do not fail the process, review its output explicitly.