How do I install the Harness skill?

Run npx skillmds@latest add vasuag09/harness in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Harness safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Harness?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Harness free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Harness?

vasuag09 (@vasuag09) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Harness by vasuag09 — Agent Skill

Name: Harness
Author: vasuag09

Harness

Run the FULL SDLC pipeline end-to-end — Plan → Implement → Verify → Maintain — with a checkpoint between every phase. Use for a complete feature from a one-line idea to merge-ready. Chains the four phase orchestrators; you approve each phase boundary.

vasuag09 Updated Sep 21, 2026

File contents

/harness — the full pipeline

The top-level orchestrator. It walks all four phases by invoking the phase orchestrators in order, pausing at every phase boundary for your go-ahead. It is a convenience wrapper — it adds checkpoints and a running summary, nothing the phase skills don't already do.

Flow

/harness-claude:harness-plan ──▶ [checkpoint] ──▶ /harness-claude:harness-implement ──▶ [checkpoint]
   ──▶ /harness-claude:harness-verify ──▶ [checkpoint] ──▶ /harness-claude:harness-maintain (optional)

Plan — run /harness-claude:harness-plan. At its HALTs, get the user's answers/approvals. → CHECKPOINT: show the approved spec + plan (+ ADR). Wait for "go" before coding.
Implement — run /harness-claude:harness-implement against the approved plan. → CHECKPOINT: report what was built and test status. Wait for "go" before verify.
Verify — run /harness-claude:harness-verify. Halt on Critical/High; stop at the git boundary. → CHECKPOINT: show review/security verdicts, coverage, observed-working evidence.
Maintain — offer /harness-claude:harness-maintain. Run it only if the user wants cleanup now.

Rules

Honor every HALT and CHECKPOINT — this is a guided pipeline, not an autonomous run.
Delegate heavy work to subagents; /harness-claude:save-session at each checkpoint so a long feature survives compaction or a new session.
Never commit or push without an explicit user ask — branch creation happens automatically at first write in the Implement phase (rules/git.md). /harness-claude:harness-verify ends at "ready to commit/PR."
For a small change, a single phase orchestrator (or atomic skill) is lighter — /harness-claude:harness is for full features.

Output

A phase-by-phase rollup ending in "merge-ready (awaiting your git go-ahead)."

---name: harnessdescription: Run the FULL SDLC pipeline end-to-end — Plan → Implement → Verify → Maintain — with a checkpoint between every phase. Use for a complete feature from a one-line idea to merge-ready. Chains the four phase orchestrators; you approve each phase boundary.---# /harness — the full pipelineThe top-level orchestrator. It walks all four phases by invoking the phaseorchestrators in order, **pausing at every phase boundary for your go-ahead**. It is aconvenience wrapper — it adds checkpoints and a running summary, nothing the phaseskills don't already do.## Flow```/harness-claude:harness-plan ──▶ [checkpoint] ──▶ /harness-claude:harness-implement ──▶ [checkpoint] ──▶ /harness-claude:harness-verify ──▶ [checkpoint] ──▶ /harness-claude:harness-maintain (optional)```1. **Plan** — run `/harness-claude:harness-plan`. At its HALTs, get the user's answers/approvals. → **CHECKPOINT:** show the approved spec + plan (+ ADR). Wait for "go" before coding.2. **Implement** — run `/harness-claude:harness-implement` against the approved plan. → **CHECKPOINT:** report what was built and test status. Wait for "go" before verify.3. **Verify** — run `/harness-claude:harness-verify`. Halt on Critical/High; stop at the git boundary. → **CHECKPOINT:** show review/security verdicts, coverage, observed-working evidence.4. **Maintain** — **offer** `/harness-claude:harness-maintain`. Run it only if the user wants cleanup now.## Rules- Honor every HALT and CHECKPOINT — this is a guided pipeline, not an autonomous run.- Delegate heavy work to subagents; `/harness-claude:save-session` at each checkpoint so a long feature survives compaction or a new session.- Never commit or push without an explicit user ask — branch creation happens automatically at first write in the Implement phase (`rules/git.md`). `/harness-claude:harness-verify` ends at "ready to commit/PR."- For a small change, a single phase orchestrator (or atomic skill) is lighter — `/harness-claude:harness` is for full features.## OutputA phase-by-phase rollup ending in "merge-ready (awaiting your git go-ahead)."

Frequently asked questions