schema-update

Migrate markdown documentation to updated schema templates with automated frontmatter updates.

Updated May 6, 2026
One-click install
npx skills add https://github.com/SuSuSleep/scaffold --skill schema-update-sususleep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: schema-update
Source: https://github.com/SuSuSleep/scaffold/tree/main/skills/schema-update
Command: npx skills add https://github.com/SuSuSleep/scaffold --skill schema-update-sususleep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of maintaining consistency across a documentation-heavy project when the underlying schema, workflow rules, or document templates need to change.

Core Features & Use Cases

  • Schema Evolution: Automatically updates format and workflow definitions while migrating existing documents to the new version.
  • Legacy Bootstrapping: Adds frontmatter and structure to legacy documents that lack formal schema definitions.
  • Use Case: When a team decides to rename a section heading or add a new required field to all user stories, this skill handles the bulk update and flags documents requiring manual content entry.

Quick Start

Run the schema-update skill to migrate all project documents to the latest schema version defined in the documentation folder.

Frequently Asked Questions about schema-update

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

FAQPage Schema
How do I migrate existing markdown documentation to a new schema?

To migrate existing markdown documentation to a new schema, run an automated schema update process that targets use cases, user stories, and architecture decision records to ensure project-wide alignment with updated templates.

What is the best way to add frontmatter to legacy markdown documents?

Adding frontmatter to legacy markdown documents requires legacy bootstrapping, a process that automatically injects formal schema definitions and structure into existing files lacking standardized metadata.

Can I automatically rename section headings across all project user stories?

Yes, you can automatically rename section headings across all project user stories by applying schema evolution rules that perform bulk updates on existing documents while flagging entries requiring manual content input.

How does schema migration handle new required fields in markdown files?

Schema migration handles new required fields in markdown files by automating frontmatter updates and explicitly flagging documents where manual content entry is necessary to meet the updated workflow definitions.

Do I need a structured scaffold to update project documentation workflows?

Yes, you need a structured scaffold containing your documentation sets including use cases, user stories, and architecture decision records to accurately target and update project-level workflow rules and markdown templates.