doc-bridge-handoff — fail-closed repository routing as a Pi package

[EmersonBraun]

I maintain Doc Bridge and packaged one of its workflows as a Pi skill for a problem I keep seeing in larger repositories: coding agents infer edit authority from prose and sometimes start in the wrong package or cross an ownership boundary.

The skill resolves a repository target into a deterministic handoff before editing:

• startHere — the correct entry document;
• readBeforeEditing — context that must be loaded;
• editRoots — paths the agent is allowed to change;
• checks — commands that define completion.

If the target is unknown or a returned path is unsafe, the resolver stops instead of inventing a fallback. The workflow is read-only, provider-independent, and does not require credentials or a hosted service.

Install

pi install npm:@agentskit/doc-bridge

The npm package declares pi.skills: ["./skills"] and the pi-package keyword, so Pi discovers the bundled doc-bridge-handoff skill directly.

Reproduce the handoff first

npx @agentskit/doc-bridge@1.4.0 init --demo
npx @agentskit/doc-bridge@1.4.0 query package example --agent

The source bundle also includes a synthetic monorepo fixture that verifies both a successful package handoff and a fail-closed unknown target.

• Source and release: https://github.com/AgentsKit-io/doc-bridge/releases/tag/v1.4.0
• Skill source: https://github.com/AgentsKit-io/doc-bridge/tree/v1.4.0/skills/doc-bridge-handoff
• npm: https://www.npmjs.com/package/@agentskit/doc-bridge

I would value Pi-specific feedback on three things:

1. Is package-level routing useful as a skill, or should invocation be more explicit?
2. Does the fail-closed behavior block any legitimate Pi workflow?
3. Is there a smaller install or invocation surface that better matches Pi conventions?

Affiliation disclosure: I maintain Doc Bridge and AgentsKit. I am sharing this here because the package uses Pi's documented package/skill mechanism; no change to Pi core is required.