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
Specs, instructions, commits, PRs, CI, and workflow events stay connected inside the repository.
01
Shared context
Spec
Instructions
Repo
02
Workflow evidence
Validation
Commit
PR Review
CI Evidence
Trusted event stream
spec.created
commit.prepared
pr.reviewed
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 evidenced, commits are written, and PRs are reviewed across agents.
Trusted Workflow Events
Hooks and CI emit compact, auditable events tied to specs, commits, PRs, runs, outcomes, and human approvals.
Engineering Observability
Teams can see readiness, lead time, review quality, validation coverage, rework signals, and workflow adoption 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 trace how work moved from unclear intent to reviewed, validated, mergeable change.
- 82% Spec readiness rate
- 4.8d Feature lead time
- 91% Commit compliance
- 100% PR review coverage
- 76% Test evidence coverage
- -31% Rework signals
- 6/6 Workflow adoption
Workflow events
- spec.created
- spec.reviewed
- test.evidence
- commit.prepared
- pr.reviewed
- ci.completed
Trusted event model
- repo
- feature
- skill
- actor
- outcome
- evidence_ref
Observable questions
- Which specs are ready?
- Where does lead time stall?
- Which PRs lack validation?
- Which changes are reworked?
- Which workflows are adopted?
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, attach validation evidence, preserve commit intent, and review merge readiness.
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, PRs, CI, and future analysis.
Workflow skill
vibe-commit
Preserve intent, changed surface, and validation evidence in commit messages instead of losing them in chat.
Workflow skill
vibe-pr-review
Review merge readiness through spec alignment, validation evidence, risk, and decision traceability.
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.