specflow-lintlisted

Verify and correct the structural integrity of both spec trees (.specflow/specs/ and .specflow/specs-business/). Checks that every spec follows the correct format, naming conventions, frontmatter schema, entity reference style, folder structure, and bidirectional linking rules. Fixes violations automatically where possible, flags ambiguous issues for human review. Use this skill whenever the user says "check specs", "lint specs", "verify spec structure", "are my specs correct", "fix spec formatting", "validate the spec tree", or after any bulk spec operation (onboarding, ingest, batch editing) to ensure consistency. Also trigger proactively after specflow-spec-editor completes a batch of changes, or when the specflow-viewer reports parsing warnings.
pedropacheco95/cortex · ★ 1 · Code & Development · score 74

Install: claude install-skill pedropacheco95/cortex

# Specflow: Spec Linter Verify and correct the structural integrity of both spec trees. This skill ensures every spec file follows the conventions exactly — format, naming, frontmatter, entity references, folder structure, overviews, and bidirectional links. It fixes what it can and flags what it cannot. > **Cortex awareness:** on a Cortex project, `cortex validate` is the mechanical backbone > this linter layers judgment on. Run it first: it already enforces frontmatter schema, > ID/path agreement, link resolution and `implements:`/`implemented_by:` symmetry, and > dependency cycles — do not reimplement those checks here. This skill adds the judgment > layer the validator cannot: naming conventions, entity-reference style, overview > quality, engineering-jargon leakage, and the auto-fixes. ## When to Run - After onboarding (specflow-onboard-codebase or deep-onboard agent) - After bulk spec changes (specflow-ingest manifest applied, batch spec-editor operations) - After manual spec edits - When the spec-viewer reports warnings - On demand: "lint the specs", "check my spec tree", "verify spec structure" ## What It Checks The linter runs checks in order. Each check produces: PASS, AUTO-FIXED, or NEEDS REVIEW. ### 1. File Structure **1a. Directory layout** - `.specflow/specs/` exists at project root - `.specflow/specs-business/` exists at project root - `.specflow/specs/` contains `_index.md` at root - Both trees are organized in domain subfolders (not flat) - Dev spec p