review-spec-local

To review specs for an open-source repository, you must scope review expectations to the specific repo and outline required sections like product.md and tech.md, ensuring consistent spec quality and alignment with core guidelines.

Referencing specs in a repository requires using repo-root-relative paths. This convention keeps specifications navigable and maintainable by ensuring links remain valid regardless of where the documentation is accessed within the repository structure.

A complete specification document in oz-for-oss requires both a product.md and tech.md section. Additionally, the spec needs a top-level heading referencing the originating GitHub issue by number to maintain proper tracking and context.

No, you cannot redefine the output schema when providing repo-specific spec-review guidance. You must ensure alignment with the core review-spec skill and may only specialize categories explicitly declared as overridable by the core skill.

You need specialized spec-review guidance when a repository has unique conventions, such as specific linking paths or required heading formats referencing GitHub issues. This specialization allows you to apply repo-defined overridable categories without altering the core schema.