skills.rest
friedbotstudio
friedbotstudioOFFICIAL
Explore all skills by this author →
GitHub

spec-lint

Preflight saved spec drafts for PlantUML syntax, required diagrams, and acceptance-criteria traceability.

5|Updated Apr 29, 2026
Search Tags:#claude code#traceability#plantuml#preflight#diagram validation#spec linting
One-click install
npx skills add https://github.com/friedbotstudio/baseline --skill spec-lint
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-lint
Source: https://github.com/friedbotstudio/baseline/tree/main/.claude/skills/spec-lint
Command: npx skills add https://github.com/friedbotstudio/baseline --skill spec-lint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill preflights a saved spec draft so you can catch diagram, structure, and traceability problems before the write-boundary hooks enforce them.

Core Features & Use Cases

  • PlantUML Syntax Checks: Verifies that every PlantUML fence parses cleanly before you commit to the draft.
  • Diagram Presence Validation: Confirms the spec includes the required diagram kinds configured by the project.
  • Acceptance-Criteria Traceability: Checks that each AC row points to an existing behavior section.
  • Use Case: A developer iterating on a spec can run this Skill to get a compact pass or fail report without triggering save-time enforcement.

Quick Start

Ask the skill to lint the saved spec draft for PlantUML syntax, required diagrams, and acceptance-criteria traceability.

Frequently Asked Questions about spec-lint

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

FAQPage Schema
How do I check PlantUML syntax errors in markdown spec drafts before saving?▼

You can preflight saved spec drafts to verify that every PlantUML fence parses cleanly, catching syntax errors before write-boundary hooks enforce them at save time.

What is spec linting for acceptance-criteria traceability in behavior diagrams?▼

Spec linting validates that each acceptance-criteria row references an existing behavior section, ensuring traceability between requirements and documented behaviors in markdown spec files.

How do I validate required diagram presence in Claude Code spec authoring?▼

You can run a preflight check on your spec draft to confirm it includes the diagram kinds configured by your project, validating diagram presence before committing to the draft.

Can I use preflight checks for iterative pre-commit validation of behavior diagrams?▼

Yes, you can run this preflight during iterative pre-commit or CI validation to detect diagram syntax errors, missing diagrams, and broken acceptance-criteria traceability without triggering save-time enforcement.

Does spec linting work with docs/specs markdown files and project-configured diagram rules?▼

Yes, spec linting applies to docs/specs markdown files and uses project-configured diagram presence rules to validate that required diagrams are included before save-time enforcement occurs.

What is the best way to catch broken acceptance-criteria traceability before committing a spec draft?▼

Preflighting your saved spec draft checks that acceptance-criteria rows point to existing behavior sections, providing a compact pass or fail report to catch traceability issues before enforcement.

Related Skills

Explore More Software Engineering Skills→
friedbotstudiofriedbotstudio
5

spec-render

Extract PlantUML diagrams from specification markdown and render them as SVG assets.

Official
Advanced
VectorInstituteVectorInstitute

fix-lint-failures

Fix ESLint, Black, Prettier, Ruff, and pre-commit lint failures in repositories.

Official
Advanced
JansenAnalyticsJansenAnalytics
5

arch-diagram

Generate architecture diagrams from codebase analysis in Mermaid, PlantUML, or ASCII formats.

Community
Intermediate
ousiassousiass

issue-split-en

Split large GitHub issues into scope-based sub-issues with user-approved drafts.

Community
Advanced