ns-sdd-analyze-consistency
(NS) Verify internal consistency of requirements.md and adherence to project rules before task generation. Use whenever the user asks to analyze or validate requirements, after scope confirmation, or after manual edits to requirements — also automatically between Gate 2 and task generation. Appends Consistency status (Approved|Reproved) to requirements.md; on Reproved informs the user and stops. Do NOT generate tasks or consistency-report.md.
How do I install this agent skill?
npx skills add https://github.com/nextstage-brasil/skills --skill ns-sdd-analyze-consistencyIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill is a requirements validator that performs static analysis on local Markdown files. It poses no security risk as it lacks network access, obfuscation, or dangerous command execution.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Analyze Consistency
Pre-execution validation: plan vs plan before coding.
Harness discovery
See ../ns-harness/references/harness-discovery.md. Load rules from {harness_root}/rules/*.md. Read architecture-rules.md first. Legacy: .cursor/rules/*.mdc only if {harness_root} is absent.
When to use
- After Gate 2 (
scope_confirmed) - User asks "analyze requirements" or "check consistency"
- After manual
requirements.mdedits
Prerequisites
{product_root}/docs/versions/{version_san}/requirements.mdexists
Workflow
Step 1 — Index requirements
Read requirements.md and index:
- Main objective
- Features (title, precedence, acceptance criteria)
- NFRs
- Declared stack
Step 2 — Run checks
Classify each as ✅ OK | ⚠️ Warning | ❌ Blocker:
Feature integrity
| Check | Failure level |
|---|---|
| Every feature has title, description, acceptance criteria | ❌ Blocker |
| At least 2 acceptance criteria per feature | ⚠️ Warning |
| No circular precedence | ❌ Blocker |
| At least one root feature (no precedence) | ❌ Blocker |
| Frontend features mention test ids when E2E expected | ⚠️ Warning |
Test coverage
| Check | Failure level |
|---|---|
| Backend features include unit test criteria | ⚠️ Warning |
| UI features include E2E criteria | ⚠️ Warning |
| Infra before domain on greenfield | ⚠️ Warning |
Data model
| Check | Failure level |
|---|---|
| Clear "Data model and APIs" section | ❌ Blocker |
| All entities in features listed in data model | ❌ Blocker |
| FK creation order respected | ❌ Blocker |
| API endpoints for frontend consumption declared | ❌ Blocker |
Alignment
| Check | Failure level |
|---|---|
| Features support stated objective | ⚠️ Warning |
| Out-of-scope features present | ⚠️ Warning |
Apply stack-specific checks from harness rules when they exist (Laravel/React checks are optional).
Step 3 — Write status into requirements.md
Do not create consistency-report.md.
Append (or replace an existing trailing ## Consistency block) at the end of
requirements.md:
## Consistency
**Status:** Approved | Reproved
**Date:** {date}
## Warnings
{Omit this heading when there are no warnings.}
- {warning}
## Recommendations
{Omit this heading when there are no recommendations.}
- {recommendation}
Rules:
- Any ❌ Blocker →
Status: Reproved - Zero blockers →
Status: Approved(warnings/recommendations still allowed) - Include Warnings only when at least one ⚠️ exists
- Include Recommendations only when there is at least one optional improvement
- On re-run, replace the previous
## Consistencyblock — do not duplicate
Step 4 — Proceed decision
- Reproved: Tell the user in chat (list blockers briefly), stop — do not proceed to task generation. Ask them to fix requirements, then re-run.
- Approved with warnings: Inform; ask fix now or proceed; user decides.
- Approved with no warnings: Inform auto-proceed to task generation;
execution_confirmedimplicit (skip Gate 3).
Critical rules
- Edit
requirements.mdonly to update the trailing Consistency block - Blockers prevent task generation without fix or explicit waiver
- If requirements missing → redirect to Gate 1 /
ns-sdd-requirements-generator - Never write
consistency-report.md
Integration
Gate 2 → ns-sdd-analyze-consistency → [Approved] → ns-sdd-task-generator
→ [Reproved] → stop; fix requirements
Post-implementation: ns-code-reviewer validates requirements × code — complementary, not a substitute.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/nextstage-brasil/skills/ns-sdd-analyze-consistency">View ns-sdd-analyze-consistency on skillZs</a>