harness-port-spec

Port Claude-based harness workflows to Gemini and LangGraph.

7|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/namojo/gemini-harness --skill harness-port-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-port-spec
Source: https://github.com/namojo/gemini-harness/tree/main/.claude/skills/harness-port-spec
Command: npx skills add https://github.com/namojo/gemini-harness --skill harness-port-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill codifies a faithful port specification to Gemini + LangGraph, preserving original harness semantics, workflows, and references while enabling runtime via LangGraph.

Core Features & Use Cases

  • Preserves original Phase 0–7 workflow mapping from revfactory/harness to Gemini.
  • Documents port decisions with clear references to original CLAUDE-based artifacts and LangGraph equivalents.
  • Provides actionable porting guidance for agent templates, skill generation, and orchestrator integration.

Quick Start

Begin porting by mapping CLAUDE-based elements to Gemini + LangGraph artifacts and validating against the workflow artifacts.

Frequently Asked Questions about harness-port-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I port a Claude-based workflow harness to Gemini and LangGraph?

Specifying a harness port to Gemini and LangGraph involves documenting port decisions with clear references to original CLAUDE-based artifacts and mapping them to LangGraph equivalents to preserve original semantics and workflows.

What is the best way to ensure feature parity when porting agent templates to LangGraph?

Validating ported harness definitions requires checking the mapped LangGraph artifacts against the original workflow.json and .agents files to ensure faithful workflow mapping and feature parity without unnecessary executable scripts.

Can I use LangGraph to maintain the original structure of a ported Gemini workflow?

Yes, LangGraph can preserve original harness structures by mapping CLAUDE-based elements to Gemini equivalents and validating definitions against workflow artifacts while maintaining original naming conventions and CLAUDE.md pointers.

How do I document port decisions when migrating a harness to Gemini?

Documenting port decisions for a Gemini migration involves recording references to original CLAUDE-based artifacts and their LangGraph equivalents in workflow.json and .agents files to ensure faithful workflow mapping.

Do I need to include executable scripts when porting harness specs to LangGraph?

No, executable scripts should not be included unless necessary; the port specification focuses on validating definitions and preserving original workflow structures and references rather than providing executable runtime scripts.