복잡한 작업을 한 개의 거대한 프롬프트로 처리하면 컨텍스트가 오염되고, 같은 맹점을 반복하고, 재사용이 안 됩니다. myharness는 그 작업을 역할이 분리된 전문 에이전트 팀 + 절차가 담긴 스킬 + 이들을 엮는 오케스트레이터로 분해해 생성합니다.
Agent Claude Code
Part of my_harness
A documentation role that keeps English, Korean, and Japanese README files synchronized, including their version, feature-count, and translation badges.
Agent Claude Code
Part of my_harness
A product-planning agent for turning feature requests into a requirements document and a technical design. It also checks how the proposal affects the app’s architecture, security, file changes, and user interface.
Agent Claude Code
Part of my_harness
An agent for preparing software releases by choosing a version number, updating release files, and drafting a changelog. SemVer is a versioning convention that uses major, minor, and patch numbers to describe the size of a change.
Agent Claude Code
Part of my_harness
A quality checker for repository changes that must agree across multiple files. It compares versions, translated READMEs, badges, referenced skill files, release notes, and related configuration.
Agent Claude Code
Part of my_harness
A maintenance role for improving the written instructions and reference files of a harness skill while keeping their links, phase numbers, and checklists aligned.
Agent Claude Code
Part of my_harness
A release-safety coordinator for changes to the shared instructions and reference files that generate agent teams. It checks those changes before they are distributed to every generated harness.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: