Agent Context Template

Reusable multi-agent context files for coding agents working in a shared project.

The template gives each project a consistent place for:

• Agent startup instructions.
• Team handoff state.
• Repository-change Pull Request policy.
• Durable context logs for plans, implementation, and code changes.

Quick Start

Use it directly from npm after publishing:

npx @cobhamdev/agent-context install --target .

With project defaults:

npx @cobhamdev/agent-context install `
  --target . `
  --project-name "project-name" `
  --base-branch "dev" `
  --remote "owner/repo"

Or clone this template next to, or inside, any project:

git clone <template-repo-url> agent-context-template

Install it into a target project:

powershell -ExecutionPolicy Bypass -File .\agent-context-template\scripts\install.ps1 `
  -TargetRoot D:\path\to\project `
  -ProjectName "project-name" `
  -DefaultBaseBranch "dev" `
  -DefaultRemote "owner/repo"

For a local clone from this machine:

git clone D:\workflowhub\agent-context-template agent-context-template
powershell -ExecutionPolicy Bypass -File .\agent-context-template\scripts\install.ps1 -TargetRoot D:\path\to\project

From inside an existing project:

git clone D:\workflowhub\agent-context-template .agent-context-template
powershell -ExecutionPolicy Bypass -File .\.agent-context-template\scripts\install.ps1 -TargetRoot .

After install, paste this into a coding agent before assigning work:

Before doing non-trivial work, read:
- <project-root>\contexts\agents\team-protocol.md
- <project-root>\contexts\agents\current-handoff.md
- <project-root>\contexts\index.jsonl

What Gets Installed

<project-root>/
  AGENTS.md
  contexts/
    README.md
    context-log.ps1
    index.jsonl
    agents/
      bootstrap-prompt.md
      current-handoff.md
      handoff.template.md
      team-protocol.md
    templates/
      context-entry.template.md

Daily Use

Create a durable context entry:

powershell -ExecutionPolicy Bypass -File .\contexts\context-log.ps1 `
  -Kind task `
  -Stage implementation `
  -Title "short title" `
  -Summary "what changed and why" `
  -Files "path\to\file"

Update contexts\agents\current-handoff.md after meaningful work so the next agent can continue without guessing.

Pull Request Policy

When an agent changes files inside a git repository, the default expected flow is:

1. Inspect repo root, branch, status, base branch, and remote.
2. Use a dedicated branch.
3. Keep one coherent change area per branch and PR.
4. Validate the focused change.
5. Commit, push, and open a Pull Request.

See contexts\agents\team-protocol.md for the full policy.

Publish

The unscoped npm name agent-context is already taken, so this package is configured as:

@cobhamdev/agent-context

Publish as a public scoped package:

npm login
npm publish --access public