solo-consistency-check

Cross-validates requirements, specs, designs, QA, and code via grep-joined traceability keys.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/cjrain-12505614/solo-forge-marketplace --skill solo-consistency-check-cjrain-12505614
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: solo-consistency-check
Source: https://github.com/cjrain-12505614/solo-forge-marketplace/tree/main/solo-forge-v0.6.0/skills/solo-consistency-check
Command: npx skills add https://github.com/cjrain-12505614/solo-forge-marketplace --skill solo-consistency-check-cjrain-12505614

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Solo developers have no second pair of eyes to catch gaps between artifacts: requirements that were never implemented, features with no test coverage, orphaned tests, or contradictions between specs and code. This Skill performs read-only cross-validation across project artifacts so those inconsistencies surface before they ship. ## Core Features & Use Cases - Traceability-key grep joins: Extracts tracking keys (REQ, AC, SCR, TSK, TC, API) from specs, designs, QA scenarios, and code, then joins them to build a traceability matrix. - Gap and contradiction detection: Flags unimplemented requirements, untested features, orphan tests, and conflicting statements across artifacts, classified as High/Medium/Low risk. - Read-only verification: Uses only Read, Grep, and Glob; it reports findings with file:line evidence and never modifies artifacts, and can run as an isolated read-only sub-agent for independent verification. - Use Case: Before a release, ask it to cross-check your feature spec, QA scenarios, and implementation; it returns a requirements traceability matrix showing REQ-02 has no test case and API-03 says PATCH in the spec but PUT in the code. ## Quick Start Ask the assistant to run a consistency cross-check across the feature specs, QA scenarios, and implementation code in this project and report any gaps or contradictions.

Frequently Asked Questions about solo-consistency-check

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

FAQPage Schema
How do I check consistency between requirements and implementation?▼

Tag each artifact item with traceability keys like REQ-01 or TC-03, then grep those keys across specs, QA scenarios, and code to join them. Keys present in requirements but absent from code indicate unimplemented features; keys in code with no requirement indicate orphans.

What is a requirements traceability matrix and how do I build one?▼

A requirements traceability matrix maps each tracking key against the artifacts where it appears, such as spec, design, QA, and implementation. Build it by extracting keys with grep from each artifact and marking presence per column, which exposes untested or unimplemented rows.

Can this verification modify my spec or code files?▼

No. The verification is strictly read-only, using only Read, Grep, and Glob. It reports inconsistencies with file and line evidence but never edits artifacts; fixes are a separate decision made by the user.

What happens if my artifacts have no traceability keys?▼

Without keys, grep-based joining is impossible, so the check reports 'untraceable — keys needed' rather than falsely claiming consistency. The recommended first step is assigning keys in the feature spec and QA scenarios.

Why run consistency checks as a separate read-only sub-agent?▼

Separating the verifier from the artifact author reduces confirmation bias, since the same context that wrote the artifacts tends to overlook its own gaps. An isolated read-only sub-agent with Read, Grep, and Glob tools provides more independent verification.