Agent Harness plugin
Codely team skills that run agent work in phases: a plan in a file or GitHub issues, review after each phase and a clean commit
- 296 ★ on the repository
- Last commit
Extended access
Why this level
- The github-suffixed skills create issues, branches and pull requests through GitHub CLI
- The commit skill stages changes and creates a commit in your repository
Install
- Works in
Manual install
npx skills@latest add codelytv/agent-harnessThe skills.sh installer lets you pick the skills and the agents to install them for.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The github-suffixed skills create issues, branches and pull requests through GitHub CLI
- The commit skill stages changes and creates a commit in your repository
This is third-party code. Review the repository files before installing.
What it does
Agent Harness packs the working habits of the Codely team into a set of skills that live in .agents/skills and fit several agents. The RPI group breaks a task into checkable phases. The codely-plan-create-subagents skill splits work into vertical slices, describes the public contracts and saves an approved plan to a file. The codely-plan-phase-implement skill executes one phase at a time and ticks its checkboxes. The versions with the github suffix keep the plan in GitHub issues. The codely-doc-create skill turns the corrections an agent received during a session into a conventions document. The codely-openspec-spec-create-from-code skill writes OpenSpec specs for behavior that already exists in the code and reports bugs and dead code separately. The codely-git-conventional-commit skill commits with a Conventional Commits message and a co-author trailer. An OpenSpec schema, codely-spec-plan, comes with them: for each change it yields lean specs and a plan.md with phases. Two Claude Code plugins install separately. The ste100 plugin switches the agent's replies to Simplified Technical English. The ts7-lsp plugin connects the LSP of the native TypeScript 7 compiler.
Who it is for. For development teams that work with agents in phases and want shared skills, plans in GitHub issues and consistent commit rules.
Good fit when
- A task must be split into phases, the plan approved and executed one phase at a time with a stop for review
- The plan should live in GitHub issues next to the team's other tasks
- You need OpenSpec specs for existing behavior before making a change
- You want to collect an agent's corrections from a session into a project conventions document
Not a fit when
- The change is a one-line fix: a multi-phase plan costs more than the task
- The repository is not on GitHub: the github-suffixed skills rely on issues and pull requests
- You need a commit style other than Conventional Commits: the skill follows the Codely team's conventions
- You need an LSP for TypeScript before version 7: ts7-lsp requires a tsc binary of version 7 or newer
Example request
`/codely-plan-create-subagents` add CSV report export with date filtersLimitations
The skills follow the Codely workflow, so their conventions need adapting to your team. The ts7-lsp plugin needs a tsc of version 7 or newer on PATH, for example after `npm install -g typescript`. The plugin install steps also disable typescript-lsp from the official marketplace. The codely-spec-plan schema assumes a project that uses OpenSpec: you copy it with degit and enable it with a schema line in openspec/config.yaml. The skills.sh installer asks which agents to install the skills for.
How to disable. In Claude Code run /plugin and disable the codely-skills plugin. Delete skills installed through skills.sh from your project's .agents/skills directory. After removing ts7-lsp, re-enable typescript-lsp with `/plugin enable`.
FAQ
How do I install the Codely skills in Claude Code?
As a plugin: `/plugin marketplace add CodelyTV/agent-harness` and `/plugin install codely-skills@codely`. Or `npx skills@latest add codelytv/agent-harness` and pick the skills and agents.
Does codely-plan-phase-implement commit by itself?
No. The skill executes one phase, ticks the checkboxes and stops for review; the commit is left to you.
How do I keep the plan in GitHub issues?
Use codely-plan-create-github: it creates a parent issue and one sub-issue per phase. Then codely-plan-phase-implement-github builds a phase on its linked branch and opens a pull request that closes the issue on merge.
What does the ts7-lsp plugin do and what does it need?
It connects the LSP of the native TypeScript 7 compiler and gives the agent go-to-definition, references and diagnostics.
What does the ste100 plugin do?
It turns on the Simplified Technical English output style: short sentences, active voice and one word per meaning.
Discussion
No questions or reviews yet.
Related
PluginsSoftaworks Agent Toolkit
Softaworks Agent Skills
A marketplace of skills, subagents and commands for coding agents: development, documentation, planning and workplace communication
14 skills that find the gaps in a task before the code: interviews, plans, assumption tests and proof that a bug fix works
Claude Code Skills and Agents
Claude Code Skills & Agents
A Claude Code plugin bundling skills and sub-agents: deep research, image generation, GitHub work, code review and model switching
A Claude Code and Codex plugin with skills for code research, tests, refactoring and independent review of finished changes
A Grid Dynamics plugin that loads a team's shared engineering standards, architecture and workflows into a coding agent session
A ready-made Claude Code setup: agents, slash commands, skills, safety hooks, rules and MCP connections in one install
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Repository stars | Main difference |
|---|---|---|---|
| Agent Harness (this entry) | no | 296 | |
| The Agentic Startup | no | 575 | Claude Code plugins for spec-driven development |
| AI-Enablement Prompts | no | 121 | Bitovi's plugin marketplace: specs and feature delivery, Figma and React |
README in short
The repository has four parts: skills, output styles, code intelligence through LSP and shared rules in the .agents directory. The typical flow is plan, implement phase by phase, review and commit.