speckit-sync-propose

Propose resolution actions for drifted and missing spec-kit requirements.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/B0yZ4kr14/OrthoPlus-Enterprise --skill speckit-sync-propose-b0yz4kr14
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-sync-propose
Source: https://github.com/B0yZ4kr14/OrthoPlus-Enterprise/tree/main/.specify-backups/20260518-141826/_agents/skills/speckit-sync-propose
Command: npx skills add https://github.com/B0yZ4kr14/OrthoPlus-Enterprise --skill speckit-sync-propose-b0yz4kr14

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams resolve mismatches between their maintained specifications and what the codebase actually does, preventing ambiguity during reviews and reducing rework caused by “spec vs implementation” drift.

Core Features & Use Cases

  • Proposes drift resolutions by deciding whether each drift item should be handled as a Backfill (code → spec), Align (spec → code), or Human Decision Required when context is insufficient.
  • Creates new specs for unspecced features by drafting spec IDs, user stories, requirements extracted from implementation, and confidence scoring.
  • Handles not-implemented requirements by recommending whether to keep, remove, or implement them based on current status.
  • Generates proposal outputs in both human-readable and machine-readable formats for downstream approval workflows.

Quick Start

Run speckit.sync.propose after you have generated a drift report with speckit.sync.analyze so it can produce proposals from .specify/sync/drift-report.json.

Frequently Asked Questions about speckit-sync-propose

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

FAQPage Schema
How do I resolve spec drift between my spec-kit requirements and actual code implementation?

You resolve spec drift by proposing targeted actions for each mismatch, categorizing items as backfill to update specs from code, align to update code from specs, or human decision flags when context is insufficient.

How do I backfill missing specifications from existing code behavior?

You backfill missing specifications by drafting new spec IDs, user stories, and requirements extracted directly from the observed implementation behavior, assigning a confidence score to each generated spec proposal.

What is the best way to handle not-implemented requirements during spec synchronization?

The best way to handle not-implemented requirements during spec synchronization is to evaluate their current status and generate recommendations to either keep, remove, or finally implement the missing functionality.

Do I need a drift report before proposing spec synchronization changes?

Yes, you need a pre-generated drift-report.json file located in the .specify/sync directory before proposing spec synchronization changes, as the tool reads this file to generate actionable proposals.

What output formats are generated for spec drift proposals?

The tool generates spec drift proposals in both human-readable Markdown format at .specify/sync/proposals.md and machine-readable JSON format at .specify/sync/proposals.json to support downstream approval workflows.