Developer pipeline — from a vague idea or a user story to implemented, tested code through brainstorm → plan → build (TDD) → finish, with an autonomous leader agent, parallel review lenses, the plan format and the build loop. Also dispatches long unattended background runs that commit after every step, so an interruption costs one step. Requires terylon-git, terylon-forge, one adapter, and terylon-core.
5 skills · 9 agents
The forge port — pull request review, description, comment handling and checklist write-back, written against an operation catalog rather than one hosting platform. Ships no adapter: enable terylon-ado or terylon-github beside it. Successor to terylon-devops.
7 skills · 1 agent
Terylon itself — the owner's MCP endpoint (/mcp) as a server, and one skill per prompt it serves: briefing, hand-over, merge-gate, add-goal, review-plan, show-story. Works in any session, the terminal, SSH and Remote Control alike. Requires the TERYLON_URL environment variable; there is no default address.
6 skills · 1 MCP server
Git foundation — worktree isolation, the review engine, and the multi-lens code reviewer. No forge, no MCP server; works in any git repository. Requires terylon-core.
3 skills · 1 agent
Tester — walks a pull request test plan and its linked item acceptance criteria, exercises what can be exercised, reconciles the two, and reports what cannot. Separates executed from asserted so a tick means something. Requires terylon-forge, one adapter, and terylon-core.
3 skills · 1 agent
The Azure DevOps adapter — fills the terylon-forge port with ADO mechanics over Microsoft's remote Azure DevOps MCP server (https://mcp.dev.azure.com), signed in with OAuth as the owner. The connect skill registers it from ADO_MCP_CLIENT_ID and ADO_MCP_TENANT_ID; every call carries ADO_ORGANIZATION. No default organisation.
3 skills