Execute plan-driven code implementation in a Git worktree with verification.
npx skills add https://github.com/DoraemonHugU/oh-my-harness --skill harness-doraemonhugu
Please help me install this Agent Skill. Skill: harness Source: https://github.com/DoraemonHugU/oh-my-harness/tree/main/plugin/skills/harness Command: npx skills add https://github.com/DoraemonHugU/oh-my-harness --skill harness-doraemonhugu
It helps you take over an implementation task that comes with an Implementation Plan (or requires converting a complex request into one) so Codex focuses on coding and verification instead of repeated reading and review-only work.
.worktrees/<slug> worktree strategy, runs a minimal project baseline, validates changes with project-specific commands, and gates completion on reviewer outcomes.Use case: You create a PR with an Implementation Plan (or a complex Implementation request that needs planning), then switch to local Codex and want a disciplined loop: implement small steps, validate, and get review without silently expanding scope.
Use the harness skill in your Codex session to execute the Implementation Plan from your current Implementation PR, run the required verifications, and complete the reviewer gate.
High-intent search queries and answers about installing and using this skill.
To execute an implementation plan inside a Git worktree safely, the skill takes over the plan and isolates code changes to a dedicated `.worktrees/<slug>` directory, enforcing strict boundaries so coding stays within the original PR scope. It validates changes using project-specific commands before completion.
Converting a complex pull request into an executable coding plan involves using research context to align requirements and generating a structured implementation plan before any coding begins. This ensures the task is fully scoped and ready for isolated worktree execution and verification.
No, you do not need an existing implementation plan to use a PR-first coding workflow. If no executable plan exists, the skill uses available research context to generate or update an implementation plan first, then proceeds with the worktree isolation and code verification loop.
Worktree isolation prevents repeated reading and review-only work by taking over the implementation task entirely within a dedicated `.worktrees/<slug>` directory. It runs a minimal project baseline, implements small steps, and validates changes autonomously, allowing Codex to focus strictly on coding and verification.
Limitations during plan-driven code implementation baseline checks include being restricted to running only minimal project baselines and project-specific validation commands within the isolated worktree. The process strictly enforces plan boundaries and cannot silently expand scope beyond the original PR or plan definitions.
fartmonarchCreate an isolated Git worktree for feature implementation and plan execution.
huidgeAutomate pre-commit verification with static security scans and quality gates.
aryan-binazirProcess Linear issues end-to-end with Codex review and pull request creation.
bacchus-labsExecute implementation plans into tested code changes with pull requests.