Add agentic-harness to Agent infrastructure#130
Open
MrBogomips wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposes adding agentic-harness under Harnesses & orchestration → Agent infrastructure (placed at the bottom, ⭐ 0, per the star-descending order).
agentic-harness is an MIT-licensed Claude Code plugin (a meta-tool) that builds, reviews, and maintains a project's agentic harness — the agents, skills, and orchestrator under
.claude/— coordinating with existing spec-driven-development systems and issue trackers, and optionally syncing a repo-native tracker with Jira/Linear.Honest scope note for the maintainer: agentic-harness runs inside Claude Code as a plugin; it is not a standalone terminal binary of its own. I'm proposing it for Agent infrastructure (the "extension tools" part of that subsection's scope) rather than the CLI-agent sections, since it's infrastructure that configures and maintains the harness CLI agents work through — alongside existing entries here that are themselves Claude Code plugins/skills (e.g. linear-cli, claude-northstar). If you feel it falls outside the list's "CLI or terminal interface" criterion, no hard feelings closing this — your call.