spec-remix

Reuse validated Project Spec files to generate v1.1-conformant updated specs.

Updated May 21, 2026
One-click install
npx skills add https://github.com/furqan90/ai_mediated_platform_engineering --skill spec-remix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-remix
Source: https://github.com/furqan90/ai_mediated_platform_engineering/tree/main/skills/spec-remix
Command: npx skills add https://github.com/furqan90/ai_mediated_platform_engineering --skill spec-remix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

For teams building multiple similar projects on the platform, manually recreating full project specs from scratch for every new build is slow, repetitive, and prone to human error. This skill eliminates that overhead by letting you reuse an existing validated project spec as a starting point for new builds.

Core Features & Use Cases

  • Prior Spec Loading: Import any previously validated Project Spec file to use as a base for new projects.
  • Guided Diff Editing: Make precise, controlled changes to spec fields via a guided interface to avoid invalid modifications.
  • Conformant Spec Emission: Output a fully valid, v1.1-compliant updated Project Spec ready for the platform's planning and scaffolding pipeline.
  • Use Case: If you previously built an orders-platform project with 2 backends and now need to build a similar inventory-platform project with 3 backends and a different realm strategy, use this skill to load the old orders-platform spec, adjust only the changed fields, and generate the new valid spec in minutes instead of rebuilding from scratch.

Quick Start

Use the spec-remix skill to load your existing orders-platform project spec and update the backend count to 3 to generate the new inventory-platform spec.

Frequently Asked Questions about spec-remix

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

FAQPage Schema
How do I reuse an existing project spec for a new platform engineering build?

To reuse a project spec for new builds, load a previously validated spec file and apply guided diff edits to adjust only the changed fields. This generates a new v1.1-conformant spec without manual schema validation overhead.

What is guided diff editing for project spec modification?

Guided diff editing is a controlled workflow for modifying project spec fields. It ensures precise changes to prior validated specs while preventing invalid modifications, outputting a fully compliant updated spec for the scaffolding pipeline.

Can I duplicate a platform engineering spec and change the backend count?

Yes, you can duplicate a platform engineering spec and change the backend count. By loading an existing spec like an orders-platform build, you adjust specific values such as backend count to quickly generate a new valid inventory-platform spec.

Do I need a previously validated Project Spec file to start remixing specs?

Yes, you need a previously validated Project Spec file as input. The remixing workflow uses this existing validated spec as the base template to apply guided modifications and emit a new compliant configuration.

Best way to generate a v1.1-compliant Project Spec from an older version?

The best way to generate a v1.1-compliant Project Spec is to load an existing validated spec into a guided diff editor. This ensures controlled modifications and outputs a conformant spec without manual schema validation overhead.

When should I remix a project spec instead of creating one from scratch?

Remix a project spec instead of starting from scratch when building multiple related projects on a platform. If the new build requires only minor adjustments to prior spec values, remixing eliminates redundant manual effort and prevents human error.