/repo-harness-product
Canonical rule owner for PRD drafting, Sprint planning/execution, and native Goal-session preparation from repo-harness planning artifacts.
$ npx -y skills add Ancienttwo/repo-harness --skill repo-harness-product --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/repo-harness-product
Context preview
The summary Claude sees to decide when to auto-load this skill.
Canonical rule owner for PRD drafting, Sprint planning/execution, and native Goal-session preparation from repo-harness planning artifacts.
SKILL.md
repo-harness-product.SKILL.mdname: repo-harness-product
description: Canonical rule owner for PRD drafting, Sprint planning/execution, and native Goal-session preparation from repo-harness planning artifacts.
when_to_use: "repo-harness-product, generate PRD, plan a sprint, sprint from PRD, run goal session, product requirements doc, sprint backlog"
repo-harness-product
Canonical rule owner for PRD, Sprint, and Goal. Router-only: shared preflight, mode selection, and cross-mode boundaries. Mode protocol lives under `references/`.
Shared Preflight
1. Confirm the working repo with `git rev-parse --show-toplevel`. 2. Read `docs/spec.md` and `.ai/harness/policy.json` when present.
Mode Selection
- A product idea needs an upper-layer PRD -> `references/prd.md`.
- A PRD or spec needs an ordered Sprint backlog, or a Sprint task needs to run or report status -> `references/sprint.md`.
- A detailed PRD/Sprint needs a bounded native `/goal` session -> `references/goal.md`.
Boundaries
- Approval gating: no mode sets `> **Status**: Approved`, or bypasses `$think`, `repo-harness run capture-plan`, task contracts, `/check`, or external acceptance on the user's behalf; explicit human approval always precedes implementation.
- `tasks/todos.md` is the deferred-goal ledger only; no mode treats it as an active backlog or goal queue.
- Product planning does not install or imply ChatGPT; ChatGPT surfaces are discovered only through their own explicit setup.
- None of these modes implements backlog tasks itself; work flows through the existing plan -> contract -> worktree -> verify gates.
Read more
name: repo-harness-product description: Canonical rule owner for PRD drafting, Sprint planning/execution, and native Goal-session preparation from repo-harness planning artifacts. when_to_use: "repo-harness-product, generate PRD, plan a sprint, sprint from PRD, run goal session, product requirements doc, sprint backlog"
repo-harness-product
Canonical rule owner for PRD, Sprint, and Goal. Router-only: shared preflight, mode selection, and cross-mode boundaries. Mode protocol lives under `references/`.
Shared Preflight
1. Confirm the working repo with `git rev-parse --show-toplevel`. 2. Read `docs/spec.md` and `.ai/harness/policy.json` when present.
Mode Selection
- A product idea needs an upper-layer PRD -> `references/prd.md`.
- A PRD or spec needs an ordered Sprint backlog, or a Sprint task needs to run or report status -> `references/sprint.md`.
- A detailed PRD/Sprint needs a bounded native `/goal` session -> `references/goal.md`.
Boundaries
- Approval gating: no mode sets `> **Status**: Approved`, or bypasses `$think`, `repo-harness run capture-plan`, task contracts, `/check`, or external acceptance on the user's behalf; explicit human approval always precedes implementation.
- `tasks/todos.md` is the deferred-goal ledger only; no mode treats it as an active backlog or goal queue.
- Product planning does not install or imply ChatGPT; ChatGPT surfaces are discovered only through their own explicit setup.
- None of these modes implements backlog tasks itself; work flows through the existing plan -> contract -> worktree -> verify gates.
File-backed workflow harness for reliable Claude Code and Codex sessions.
Repo: Ancienttwo/repo-harness
Other skills on repo-harness.
- /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 high-stakes decision that
Open skill - /repo-harness-chatgpt
Canonical rule owner for repo-harness ChatGPT integration -- Oracle-first browser/GPT Pro consult and continuation, MCP Connector setup, MCP bridge planning handoff, and Connector invocation read-back evidence.
Open skill - /repo-harness-cross-review
Independent cross-model review of the current review scope (branch diff plus staged, unstaged, untracked changes) from the opposite vendor's model. Catches spec drift, missing edge cases, and fake tests self-review cannot see. Use before merging, after a tricky change, or a
Open skill - /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.
Open skill - /repo-harness-setup
Canonical rule owner for installing, migrating, upgrading, repairing, scaffolding, and capability-configuring the repo-harness workflow in a repository.
Open skill