spec-review

Collect line-by-line comments and track resolutions across spec reviews.

8|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/zxdxjtu/harness --skill spec-review-zxdxjtu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-review
Source: https://github.com/zxdxjtu/harness/tree/main/skills/spec-review
Command: npx skills add https://github.com/zxdxjtu/harness --skill spec-review-zxdxjtu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec reviews are often time-consuming and opaque, making it hard for multiple stakeholders to align on the exact feature requirements. This skill provides a structured, line-by-line review workflow with tracked comments and resolutions to improve clarity and decision traceability.

Core Features & Use Cases

  • Line-by-line comments: reviewers can attach comments to specific sections or lines in a spec, with timestamps and reviewer identity.
  • Resolution tracking: track open and resolved comments, and automatically summarize status for stakeholders.
  • Review orchestration: creates or loads a central review document and coordinates input from multiple reviewers across teams.

Quick Start

Create a new review draft for a feature (e.g., F001) by loading the target spec and initializing the review file.

Frequently Asked Questions about spec-review

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

FAQPage Schema
How do I collect line-by-line comments on a feature spec from multiple stakeholders?

To track comment resolutions in spec reviews, the workflow aggregates open and resolved comments and automatically summarizes their status for stakeholders. This ensures decision traceability and clarity across product-management and engineering teams.

What is the best way to track open and resolved comments during a product requirements review?

Tracking open and resolved comments during a product requirements review requires a structured workflow that aggregates feedback and automatically summarizes status for stakeholders. This ensures decision traceability and alignment across teams.

Can I coordinate multi-person spec reviews for engineering workflows without losing decision traceability?

Yes, you can coordinate multi-person spec reviews for engineering workflows without losing traceability by loading a spec and initializing a central review document. This orchestrates input across teams while recording line-by-line comments and resolutions.

How do I start a structured review for a feature spec?

To start a structured review for a feature spec, load the target spec document and initialize the review file. This creates a central draft that enforces the workflow for collecting comments and tracking resolutions across stakeholders.

Does this spec review workflow work for both product-management and engineering teams?

Yes, this spec review workflow works for both product-management and engineering teams. It is specifically applicable to feature specs and product requirements, coordinating input across multiple stakeholders in these workflows.