dev-sync

Merge external LLM markdown sections into project specification files.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/MaxGiu67/plugin-MUCC --skill dev-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-sync
Source: https://github.com/MaxGiu67/plugin-MUCC/tree/main/dev-methodology/skills/dev-sync
Command: npx skills add https://github.com/MaxGiu67/plugin-MUCC --skill dev-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill removes the manual, error-prone work of taking markdown output from external LLMs and correctly placing it into an existing project's specification files, ensuring decisions and structure are preserved.

Core Features & Use Cases

  • Intelligent header-based routing: maps sections like Database Schema, Architecture, Wireframes, API Endpoints, and Vision to their corresponding specs files.
  • Section-level merging: preserves existing decisions, replaces only the relevant sections, and maintains original formatting and structure.
  • Project bookkeeping: appends a timestamped entry to specs/_changelog.md and updates specs/_status.md when a phase completes, while requesting user confirmation before writes.
  • Use case: import a GPT or Gemini-generated database schema fragment and merge only the "Database Schema" section into specs/database/schema.md with a changelog entry.

Quick Start

Integrate the external LLM markdown output and confirm the proposed merge into the identified spec file.

Frequently Asked Questions about dev-sync

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

FAQPage Schema
How do I merge external LLM markdown output into existing project specs?

You can integrate LLM markdown fragments by parsing headers to route content to target spec files, performing section-level merges that preserve prior decisions, and prompting for confirmation before writing.

How does intelligent section-level merging preserve existing specifications?

Section-level merging preserves existing specifications by replacing only relevant sections mapped from markdown headers, maintaining the original formatting and structure of target spec files without overwriting prior decisions.

Can I import GPT or Gemini generated fragments into specific specs files?

Yes, you can import GPT or Gemini generated fragments by mapping markdown headers like Database Schema or API Endpoints to corresponding specs files, merging only the relevant sections into your project.

Does integrating LLM outputs automatically update changelogs and status files?

Integrating LLM outputs updates project bookkeeping by appending a timestamped entry to specs/_changelog.md and updating specs/_status.md when a phase completes, requesting user confirmation before writing.

What is the best way to map markdown headers to spec files in a development pipeline?

The best way to map markdown headers to spec files is using intelligent header-based routing, which directs sections like Architecture, Wireframes, and Vision to their corresponding project specification files automatically.

Are there limitations when mapping markdown fragments from Mistral into project specs?

A limitation when mapping markdown fragments from Mistral is that the process relies on parsing markdown headers to determine target files, requiring clearly defined section headers to route content correctly.