skills.rest
victorp1leon
victorp1leonCOMMUNITY
Explore all skills by this author →
GitHub

specs-wave-migration

Migrate pending spec-driven manifest entries to canonical specs and contracts.

Updated Mar 6, 2026
Search Tags:#documentation#migration#manifest#canonical#specs#wave
One-click install
npx skills add https://github.com/victorp1leon/openclaw-bakery --skill specs-wave-migration
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: specs-wave-migration
Source: https://github.com/victorp1leon/openclaw-bakery/tree/main/.codex/skills/specs-wave-migration
Command: npx skills add https://github.com/victorp1leon/openclaw-bakery --skill specs-wave-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Migrates spec-driven documentation waves from the migration manifest into canonical specifications and contract copies, updating the manifest statuses from pending to migrated and refreshing the feature registry.

Core Features & Use Cases

  • Read pending migration entries for a selected wave from the manifest.
  • For plan entries (R-/P-), generate canonical artifacts: spec.md, clarify.md, plan.md, tasks.md, analyze.md, and history/legacy-plans/<legacy-plan>.md snapshots.
  • For contract entries (C4-*, Wave C.1), copy the source spec into the canonical destination with a migration trace header.
  • Update manifest statuses to migrated and rebuild documentation/specs/_index.md feature registry for discoverability.

Quick Start

Run the migration script to migrate the selected wave across the target domains.

Frequently Asked Questions about specs-wave-migration

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

FAQPage Schema
How do I migrate pending spec entries into canonical documentation?▼

Migrate pending spec entries by materializing canonical spec packages, contract copies, and legacy snapshots from a manifest, then update manifest statuses from pending to migrated and refresh the feature registry.

What is a spec-driven documentation wave migration?▼

A spec-driven documentation wave migration consolidates pending manifest entries by generating canonical artifacts like spec.md, plan.md, and tasks.md, while preserving legacy snapshots under history for plan entries across runtime and platform domains.

How do I generate canonical artifacts for plan entries during a documentation migration?▼

Generate canonical artifacts for plan entries by reading pending migration entries from the manifest and materializing files like spec.md, clarify.md, plan.md, tasks.md, and analyze.md, along with legacy-plan snapshots under history.

Does the migration workflow support both plan and contract spec entries?▼

The migration workflow supports both plan and contract spec entries, generating canonical artifacts for plan entries and copying source specs into canonical destinations with migration trace headers for contract entries like Wave C.1.

How do I update the feature registry after migrating spec waves?▼

Update the feature registry by refreshing the documentation/specs/_index.md file to reflect newly migrated features after the manifest statuses have been updated from pending to migrated.

What is the best way to preserve legacy snapshots during a spec migration?▼

Preserve legacy snapshots during a spec migration by creating history/legacy-plans snapshots for plan entries and adding migration trace headers to contract spec copies when materializing canonical documentation packages.

Related Skills

Explore More Content & Communication Skills→
XWIlluDeluXWIlluDelu

project-setup

Link shared skills and fragments into a repository and generate AGENTS.md with alias symlinks.

Community
Intermediate
lionbenjaminlionbenjamin
15

analyze

Analyze development specs, plans, and tasks for traceability and gap detection.

Community
Intermediate
compnew2006compnew2006
63

speckit.tasks

Convert plan.md and spec.md into a dependency-ordered tasks.md.

Community
Advanced
kimprobablykimprobably

spec-kitty.tasks-packages

Generate per-work-package task prompt files from wps.yaml manifests.

Community
Intermediate