From agent-hotline-skills
Structured handoffs for software development workflows (local Builder → cloud Architect/DevOps).
How this skill is triggered — by the user, by Claude, or both
Slash command
/agent-hotline-skills:agent-hotlineThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill to coordinate a local Builder with cloud Architect and DevOps agents on the same project.
Use this skill to coordinate a local Builder with cloud Architect and DevOps agents on the same project.
Instead of Slack threads and copy/paste, all agents read/write state to .hotline.json for auditable, structured handoffs.
Builder writes code locally (fast, low cost)
↓
Architect (cloud) reads and tests thoroughly
↓
DevOps (cloud) reads Architect approval and deploys safely
↓
Cycle repeats
agent-hotline readLoad the latest handoff from the previous agent. Run this first.
agent-hotline write "<status>"Hand off your work to the next agent. Example:
agent-hotline write "OAuth2 implemented. All 15 tests passing. Ready for integration testing."
agent-hotline clearReset the state after deployment. Run this once the feature is live and stable.
agent-hotline statusShow whether there is an active handoff plus history size.
| Role | Task | Model | Cost |
|---|---|---|---|
| Builder | Code generation, unit testing | Local (GPU/CPU) | $0 |
| Architect | Integration testing, edge cases | Cloud | $ |
| DevOps | Deployment, monitoring | Cloud | $ |
npm run test locally before handing off.export HOTLINE_AUTHOR=builder before commands to tag handoffs with role names instead of usernames.Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub mrutunjay-kinagi/agent-hotline --plugin agent-hotline-skills