repo-harness-review

Review repo-harness plans across product, engineering, design, and DevEx dimensions.

407|29|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/Ancienttwo/repo-harness --skill repo-harness-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-harness-review
Source: https://github.com/Ancienttwo/repo-harness/tree/main/assets/skill-commands/repo-harness-review
Command: npx skills add https://github.com/Ancienttwo/repo-harness --skill repo-harness-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of reviewing a repo-harness plan comprehensively across various dimensions, ensuring that all aspects are considered before implementation or release.

Core Features & Use Cases

  • Multi-Dimensional Review: Conducts reviews from product, engineering, design, and DevEx perspectives.
  • Blocking Issue Identification: Helps identify and report blocking issues early in the process.
  • Plan Edits: Suggests minimal edits to the plan to clear blocking issues.

Quick Start

Use the repo-harness-review command to initiate a review of the repo-harness plan.

Frequently Asked Questions about repo-harness-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I conduct a comprehensive engineering and design review for a repo plan?

To conduct a comprehensive engineering and design review, evaluate the repo-harness plan across product, engineering, design, and DevEx dimensions to identify blocking issues and suggest minimal plan edits.

What is the best way to identify blocking issues in a software plan before implementation?

Identifying blocking issues in a software plan requires a structured multi-dimensional review across product, engineering, design, and DevEx perspectives to catch flaws early before implementation begins.

How do I review a repo-harness plan from a DevEx perspective?

Reviewing a repo-harness plan from a DevEx perspective involves analyzing the plan file within the repository to evaluate developer experience factors and flag blocking issues for correction.

Can I get automated suggestions to edit and improve a product plan?

Yes, you can get automated suggestions to improve a product plan by running a structured review that outputs minimal plan edits required to clear identified blocking issues across all review dimensions.

Do I need repository access to perform a multi-dimensional plan review?

Yes, you need direct access to both the repository and the specific plan file to execute a multi-dimensional plan review and accurately identify blocking issues within the codebase context.

What are the limitations of automated engineering plan reviews?

Automated engineering plan reviews are limited to analyzing the provided plan file and repository context, meaning they can only suggest minimal edits for blocking issues rather than rewriting the entire implementation strategy.