merge

Promote draft documentation and ADRs to confirmed repository locations with quality gates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the fragmentation and manual overhead of finalizing documentation by automating the promotion of draft use cases and architectural decisions into their permanent, confirmed locations.

Core Features & Use Cases

  • Automated Promotion: Moves files from draft directories to confirmed paths while applying standardized simplification rules.
  • Quality Gates: Enforces strict pre-merge checks, including behavioral test verification and interface contract alignment.
  • Consistency: Automatically updates module READMEs and cleans up draft plans to ensure the documentation repository remains a single source of truth.

Quick Start

Use the merge skill to promote all completed draft documentation and update the project status for the current plan.

Frequently Asked Questions about merge

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

FAQPage Schema
How do I automate promoting draft documentation to confirmed repository locations?

Automated documentation promotion moves files from draft directories to confirmed paths while applying standardized simplification rules. This process enforces strict pre-merge quality gates, including behavioral test verification and interface contract alignment, to ensure repository consistency.

What quality gates are enforced when finalizing architectural decision records?

Quality gates for finalizing architectural decisions enforce strict pre-merge checks, including behavioral test verification and interface contract alignment. These gates ensure that draft ADRs meet project requirements before being promoted to confirmed locations.

How do I keep module READMEs updated when migrating draft use cases?

Migrating draft use cases automatically updates module READMEs to maintain a single source of truth. This consistency mechanism cleans up draft plans and ensures the documentation repository reflects the newly promoted user stories and use cases.

Does automated file migration support content simplification for user stories?

Automated file migration supports content simplification by applying standardized rules when moving user stories from draft to confirmed paths. This ensures documentation remains streamlined while satisfying repository-level consistency checks during the promotion workflow.

When should I use an automated workflow for promoting draft documentation instead of manual updates?

An automated workflow for promoting draft documentation is necessary when managing structured repositories with use cases, user stories, and ADRs. It eliminates manual overhead and fragmentation by enforcing quality gates and automatically updating module READMEs during file migration.