skills.rest
LucasBiason
LucasBiasonCOMMUNITY
Explore all skills by this author →
GitHub

spec-normalizer

Convert markdown docs into a canonical spec folder structure with cross-links.

Updated Aug 27, 2026
Search Tags:#documentation#markdown#specification#structure#traceability#canonical#standardize
One-click install
npx skills add https://github.com/LucasBiason/engineering-knowledge-base --skill spec-normalizer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-normalizer
Source: https://github.com/LucasBiason/engineering-knowledge-base/tree/main/.claude/skills/workflow/spec-normalizer
Command: npx skills add https://github.com/LucasBiason/engineering-knowledge-base --skill spec-normalizer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes existing documentation into the canonical Spec-Driven format, reducing duplication and improving traceability.

Core Features & Use Cases

  • Canonical structure mapping: moves content into spec/ folders (spec/00-context, spec/10-requirements, spec/20-design, spec/90-decisions, spec/99-meta).
  • Duplication reduction: consolidates similar content and adds cross-links.
  • Traceability: connects PRD goals, FRs, acceptance criteria, and design sections for traceable lineage.

Quick Start

Provide your messy markdown docs or old PRDs and run this skill to reorganize them into a canonical spec structure.

Frequently Asked Questions about spec-normalizer

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

FAQPage Schema
How do I convert messy markdown docs into a standardized specification structure?▼

To convert messy markdown docs into a standardized specification structure, map content into canonical folders like context, requirements, and design. This reduces duplication and improves traceability across projects.

What is the best way to reorganize legacy PRDs into a canonical spec format?▼

Reorganizing legacy PRDs into a canonical spec format involves applying mapping rules to move content into designated spec directories. This process preserves meaning while adding cross-links for traceable lineage.

How do I reduce content duplication in wiki exports without losing meaning?▼

Reduce content duplication in wiki exports by consolidating similar content and adding cross-links during the spec normalization process. This maintains the original meaning while enforcing a standardized layout.

Can I enforce traceability between PRD goals and design sections in markdown?▼

Yes, you can enforce traceability between PRD goals and design sections by mapping markdown content to a canonical spec structure. This connects requirements, acceptance criteria, and design sections for traceable lineage.

Does normalizing documentation into a spec structure change my underlying content?▼

Normalizing documentation into a spec structure does not change your underlying content. The process enforces mapping rules and adds cross-links while strictly preserving the original meaning of the markdown text.

When should I use a canonical spec format for my project documentation?▼

Use a canonical spec format when you need to standardize messy docs, wiki exports, or legacy PRDs across projects. It reduces duplication and improves traceability by moving content into structured spec folders.

Related Skills

Explore More Content & Communication Skills→
mindmorassmindmorass
2

obsidian-publisher

Write Markdown notes and Mermaid diagrams into Obsidian vault folders.

Community
Basic
shynlee04shynlee04
51

hivefiver-gsd-compat

Map HiveFiver outputs to GSD lifecycle nodes with lineage validation.

Community
Intermediate
jykimjykim
1

md2html

Convert markdown documents to website-ready HTML pages with frontmatter and wiki links.

Community
Intermediate
boykushboykush
2

example-mapping-transcribe

Transcribe Example Mapping board content into YAML format.

Community
Intermediate