Agent Plugins Marketplace
← All plugins

engineering-harness

v0.5.1

Minimalist enterprise engineering harness for Jira bugs and features: plan/implement/evaluate workflow on a light or full track, with an independent quality gate, bounded iteration, and human-controlled merge.

Claude Code6 Skills

By SIS EngineeringLicense: MIT0 GitHub starsUpdated 5 days ago

Directory evidence

Runtimes
Claude Code
Parsed components
6 skill or MCP entries
Source updated
Sep 18, 2026
Manifest status
Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install engineering-harness for Claude Code

Installs for the current user
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install engineering-harness@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually
git clone https://github.com/hasbee-osos/claude-harness-lite

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The repository root is the plugin root.

Plugin files

engineering-harness/
├── .claude-plugin/plugin.json
├── skills/brain/SKILL.md
├── skills/engineering-standards/SKILL.md
├── skills/git-workflow/SKILL.md
├── skills/harness-core/SKILL.md
├── skills/input-packets/SKILL.md
└── skills/jira-attachments/SKILL.md

Included Skills6

brainskills/brain/SKILL.md

The single specification of how the brain is written - the team's shared git repo, cloned into the workspace as sis-brain, holding the durable per-ticket record of every harness run. Covers the layout, what each stage records, state.json, the journal, locked decisions, the index, syncing, resuming a ticket, metrics, the leadership dashboard, and what must never be written there. Read by the orchestrating commands before they write or read the record; agents return their artifacts and do not write here.

engineering-standardsskills/engineering-standards/SKILL.md

How to change this product's code - the team's own conventions for Spring Boot, Angular and PostgreSQL/Liquibase (base classes, authorization, Liquibase scripts, usage checks, common components, error handling, GMT+0 dates), the smallest-safe-change principle, and risk-based testing including characterization tests. Read before planning, implementing or evaluating a change.

git-workflowskills/git-workflow/SKILL.md

Team Git branching and PR strategy (base / gcet / gutech / osos lines) plus Git safety rules - flow selection with human confirmation, source branches, branch naming, dev-stage PR targets, conflict resolution branches, protected branches, commit discipline, no force-push, no auto-merge. Use for all Git operations, branch creation, and PR preparation.

harness-coreskills/harness-core/SKILL.md

The engineering harness's operating rules, read by every command and agent before acting - ground rules (Jira as source of truth, independent evaluator, locked decisions, human authority, evidence, bounded iteration, confirmed repos only), the multi-repo workspace and git -C usage, what each stage produces for a bug versus a feature, the light and full tracks, and when a story is too big for one run.

input-packetsskills/input-packets/SKILL.md

When the plan stops on open questions, write a paste-ready Jira comment for the people who can answer them - qa-packet.md for bugs (QA), sme-packet.md for stories, tasks and features (subject-matter expert) - then read the answers back from Jira on resume. Use whenever a stage returns NEEDS_INPUT.

jira-attachmentsskills/jira-attachments/SKILL.md

How the harness reads a Jira ticket's attachments - list them, download them through the read-only Atlassian MCP, turn screen recordings into still frames, and hand images and frames to the Planner as evidence. No per-developer setup, tokens or installs. Use whenever a ticket has attachments, which is nearly always.

Plugin manifests1

.claude-plugin/plugin.json
{
  "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
  "name": "engineering-harness",
  "displayName": "Claude Code Engineering Harness",
  "version": "0.5.1",
  "description": "Minimalist enterprise engineering harness for Jira bugs and features: plan/implement/evaluate workflow on a light or full track, with an independent quality gate, bounded iteration, and human-controlled merge.",
  "author": {
    "name": "SIS Engineering"
  },
  "keywords": [
    "bug-fix",
    "user-stories",
    "jira",
    "engineering",
    "spring-boot",
    "angular",
    "postgresql",
    "code-review"
  ],
  "license": "MIT"
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[engineering-harness on Agent Plugins Marketplace](https://pluginsmp.com/plugins/engineering-harness)