Ancienttwo/repo-harness

repo-harness

Route explicit repo-harness setup, planning, execution, verification, and handoff actions through deterministic repository state.

repo-harness-cross-review

Independent outside review of the current review scope (branch diff plus staged, unstaged, untracked changes). Claude hosts use direct Codex; Codex hosts use OpenAI's official Claude Code Codex plugin app-server runtime. Use before merging, after a tricky…

repo-harness-chatgpt

Canonical rule owner for repo-harness ChatGPT integration -- Oracle-first browser/GPT Pro consult and continuation, advisory orchestration, MCP Connector setup, MCP bridge planning handoff, and Connector invocation read-back evidence.

repo-harness-product

Canonical rule owner for PRD drafting, Sprint planning/execution, and native Goal-session preparation from repo-harness planning artifacts.

obsidian-memory

Cross-project long-term memory over an Obsidian brain vault: recall relevant notes before a task, and persist distilled conclusions (decisions, pitfalls, solutions, progress) back after a task. The vault is an optional aggregation/projection layer —…

Source text: Mixed languages

repo-harness-plan

Interactive planning entrypoint for repo-local agentic development work. Produces an approved plan before implementation, and reviews an existing plan across product, engineering, design, and DevEx dimensions.

claude-plan

Get an independent architecture/implementation plan from Anthropic Claude (Fable, a different vendor's model) running Claude Code's native plan mode, from inside a non-Claude host such as Codex. Use mid-execution when work hits a genuine design fork or…

repo-harness-architecture

Resolves repo-harness architecture drift requests and updates architecture docs or diagrams without running full init, migrate, or upgrade.

repo-harness-setup

Canonical rule owner for installing, migrating, upgrading, repairing, scaffolding, and capability-configuring the repo-harness workflow in a repository.

repo-harness-check

Verification entrypoint for repo-harness workflow readiness. Runs workflow gates, task sync, contract checks, inspector, and migration dry-run before merge or release.

repo-harness-ship

Final repo-harness closeout workflow. Runs review/check gates, commits finished contract worktrees, pushes codex branches, and creates GitHub PRs by default.