Agent Harness

🗂️ Skills

Skills live in .agents/skills/ and are shared across every agent.

⚡ Quickstart

1. Install the skills with the skills.sh installer:

   npx skills@latest add codelytv/agent-harness
   

2. Pick the skills you want and the coding agents you want to install them on.

3. Run a skill in your agent, for example /codely-doc-create.

4. Done. Your agent now follows Codely's conventions.

Alternative: Claude Code plugin

1. Add this repository as a plugin marketplace and install the plugin:

   /plugin marketplace add CodelyTV/agent-harness
   /plugin install codely-skills@codely
   

2. Run a skill in Claude Code, for example /codely-doc-create.

3. Done. Every skill in this repo is now available in Claude Code.

📦 Available skills

Skills are grouped by category:

📃 Harness

Skill	What it does
codely-doc-create	Generates convention documentation from the current conversation, turning feedback and corrections into reusable docs.

Two ways to use codely-doc-create:

• After a conversation — run /codely-doc-create to turn the corrections the agent received during the session into a new doc.
• Before a conversation — run /codely-doc-create <description> to formalize a convention you want to document upfront.

🗺️ RPI

Skill	What it does
codely-plan-create	Breaks a task into reviewable phases (vertical slices), defines the public contracts to change, and saves an approved plan file.
codely-plan-create-subagents	Same planning flow, but delegates the codebase exploration to cheaper subagents running in parallel.
codely-plan-phase-implement	Executes a single phase of a plan at a time, updates its checkboxes, and stops for review without committing automatically.
codely-plan-create-github	Same planning flow, but stored as GitHub issues: a parent plan issue and one native sub-issue per phase.
codely-plan-phase-implement-github	Implements one phase issue at a time on its linked branch and opens a pull request that closes the issue on merge.
codely-plan-create-gitlab	Same planning flow, but stored as GitLab issues: a parent plan issue and one linked child issue per phase.
codely-plan-phase-implement-gitlab	Implements one phase issue at a time on its linked branch and opens a merge request that closes the issue on merge.

Typical flow:

• Plan the work with /codely-plan-create <task> (or /codely-plan-create-subagents <task> to delegate the exploration) to produce a phased plan file under .agents/plans/.
• Implement it phase by phase with /codely-plan-phase-implement <plan-file-path>, reviewing and committing after each one.

⚫ OpenSpec

Skill	What it does
codely-openspec-spec-create-from-code	Writes the OpenSpec specs of behaviour that already exists in the code, so the next change can modify or remove it instead of only adding to it.

Two ways to use codely-openspec-spec-create-from-code:

• Before a change — run /codely-openspec-spec-create-from-code <the change you are about to make> to specify the current behaviour it will touch, then continue with /openspec-explore.
• To catch up — run /codely-openspec-spec-create-from-code <capability> to specify an existing feature, or without arguments to list the features that still lack a spec.

Only intended and verified behaviour reaches the spec: bugs, accidental behaviour and dead code are reported instead.

🧩 codely-spec-plan schema

An OpenSpec custom schema that brings the codely-plan-create-subagents flow to OpenSpec. Each change produces only two things to review:

This is the beginning of the README. Read the rest at the original. Read the full README ↗