update-project-docs

Migrate project documentation structures to the latest scaffold template.

Updated Oct 8, 2025
One-click install
npx skills add https://github.com/ichabodcole/project-docs-scaffold-template --skill update-project-docs-ichabodcole
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-project-docs
Source: https://github.com/ichabodcole/project-docs-scaffold-template/tree/main/plugins/project-docs/skills/update-project-docs
Command: npx skills add https://github.com/ichabodcole/project-docs-scaffold-template --skill update-project-docs-ichabodcole

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrade project documentation structures to align with the latest project-docs scaffold template, reducing drift when templates evolve.

Core Features & Use Cases

  • Automates detection of outdated docs scaffolds and coordinates migrations across flat structures to project folders.
  • Applies versioned migration steps, ensuring migrations are executed in sequence and verified.
  • Generates updated READMEs and scaffolds to guide teams through upgrades with minimal downtime.

Quick Start

Run the upgrade-project-docs skill to migrate your documentation structure to the latest scaffold version.

Frequently Asked Questions about update-project-docs

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

FAQPage Schema
How do I migrate project documentation to a new scaffold template?

Project documentation migration is automated by coordinating versioned steps that convert flat docs into co-located folders and update the docs_version marker, ensuring a deployable structure.

What is the best way to upgrade flat docs into co-located project folders?

Upgrading flat docs into co-located project folders is handled by applying versioned migration steps in sequence, verifying references, and updating the docs_version marker to maintain a consistent documentation structure.

How does versioning work for documentation scaffold migrations?

Documentation scaffold versioning tracks migrations by validating and updating the docs_version marker, applying stepwise migration guides in sequence, and verifying references to prevent template drift.

Do I need to manually update the docs_version marker after a template migration?

You do not need to manually update the docs_version marker; the migration process automatically validates and updates the marker while verifying references to ensure the documentation structure remains consistent and deployable.

Can I skip migration steps when upgrading to the latest project-docs template?

You cannot skip migration steps; the process applies versioned migration guides sequentially to ensure structural integrity, verifying references and the docs_version marker throughout the upgrade to prevent documentation drift.