Repo Protocol
Feature specs, project instructions, prototypes, validation plans, releases, and decisions live where agents and engineers can both read them.
AI Native Dev
The repo protocol for AI-native development teams.
Give humans and coding agents the same operating context, then turn workflow events into a reliable view of engineering quality and flow.
Start with the repo protocol
npx skills add https://skill.ferryman.app --agent codex --skill '*' --copy
Repo Protocol
Project instructions, specs, tests, commits, CI, and workflow events stay connected inside the repository.
01
Shared context
Instructions
Spec
Repo
02
Test and commit evidence
Test Plan
Test Evidence
Commit
Trusted event stream
spec.created
test.evidence
commit.prepared
Observable output
Engineering Observability
Product model
From shared context to measurable engineering work.
Organization Skills
Reusable workflow units define how specs are created, tests are planned and evidenced, and commits preserve implementation intent across agents.
Trusted Workflow Events
Hooks and CI emit compact, auditable events tied to specs, tests, commits, runs, outcomes, and human approvals.
Engineering Observability
Teams can see adoption, spec lead time, test coverage, and commit evidence without reading every chat.
Engineering observability
Measure flow and quality, not AI usage theater.
The value of skills and hooks is not that an agent ran a command. The value is that the organization can see which protocol steps were actually adopted and whether work moved from intent to tested, reviewable commits.
-
01
Spec Lead Time
Source: spec.created to spec.ready or spec.reviewed:ready.
How long does it take for intent to become development-ready? -
02
Spec Adoption Rate
Source: spec files created or updated by vibe-spec-create.
Are teams using the repo-native spec protocol for feature definition? -
03
Test Adoption Rate
Source: features with vibe-test evidence or test plan artifacts.
Are teams defining validation before the commit is prepared? -
04
Test Coverage
Source: CI coverage reports when available; otherwise test evidence coverage.
Does the implementation have measurable validation evidence? -
05
Commit Adoption Rate
Source: commits prepared with vibe-commit structured evidence.
Are commits preserving intent, change surface, and validation evidence?
Workflow step
- Spec creation
- Spec readiness review
- Test planning
- Test evidence
- Commit preparation
- CI coverage
Adoption signal
- skill name
- artifact path
- event type
- outcome
- timestamp
- evidence_ref
Quality / efficiency question
- Was the spec protocol used?
- How long until the spec was ready?
- Was validation planned before commit?
- Is coverage or evidence present?
- Did the commit preserve intent?
Protocol execution layer
Make the development loop preserve context by default.
Each workflow action turns a fragile handoff into a repeatable repo-native step: define the feature, align the project instructions, plan validation, attach test evidence, and preserve commit intent.
Workflow skill
vibe-spec-create
Turn product intent, issue notes, screenshots, prototypes, and tradeoffs into a repository-native feature spec.
Workflow skill
vibe-spec-review
Review whether a spec is clear enough to start, and separate blocking questions from useful suggestions.
Workflow skill
vibe-project-instructions
Create project-level agent instructions so coding agents share the same operating rules and repository context.
Workflow skill
vibe-test
Plan validation and capture test evidence that can be reused by commits, CI, and future analysis.
Workflow skill
vibe-commit
Preserve intent, changed surface, and validation evidence in commit messages instead of losing them in chat.
Install
Install the repo protocol layer locally.
The local path gives teams a concrete way to apply the protocol without an account, a hosted backend, or a public GitHub repository requirement.
Install in Codex
npx skills add https://skill.ferryman.app --agent codex --skill '*' --copy
Inspect protocol actions
npx skills add https://skill.ferryman.app --list
Installer endpoint
https://skill.ferryman.app/.well-known/agent-skills/index.json
Local-first
The protocol layer runs inside your project.
Install it once, keep the workflow files with the repository, and let every coding agent read the same operating context.
The website is only the distribution surface; the daily workflow happens in the local repo.