speckit-sync-backfill

Generate a backfilled feature spec from existing code, tests, and documentation.

Updated Apr 12, 2026

Search Tags:#automation #documentation #backfill #spec-generation #code-to-spec

Ready to run

npx skills add https://github.com/datamonsterr/mycoai_projects --skill speckit-sync-backfill

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-sync-backfill
Source: https://github.com/datamonsterr/mycoai_projects/tree/main/.agents/skills/speckit-sync-backfill
Command: npx skills add https://github.com/datamonsterr/mycoai_projects --skill speckit-sync-backfill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of a complete feature spec by backfilling from existing code, tests, and documentation, saving time and aligning implementation with documentation.

Core Features & Use Cases

Backfill versatile specs from Commands, Services, Tests, and Docs.
Infer user stories, acceptance criteria, and requirements from code.
Produce a structured spec with sections for backfill notice, requirements, and architecture plan.

Quick Start

Run the speckit-sync-backfill command with a feature identifier to generate a backfilled spec from existing code.

Frequently Asked Questions about speckit-sync-backfill

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

FAQPage Schema

How do I generate documentation from existing code that lacks any specs?▼

To generate documentation from existing code, this Skill analyzes your implementation, tests, and docs to infer user stories, acceptance criteria, and requirements, producing a structured spec outline with traceability to the current codebase.

Can I backfill user stories and acceptance criteria directly from source code and tests?▼

Yes, you can backfill user stories and acceptance criteria directly from source code and tests. The process derives scope and requirements deterministically from Commands, Services, Tests, and Docs to create a complete feature spec.

Do I need a specific directory structure to backfill specs from my codebase?▼

Yes, you need a .specify/ directory structure in your codebase. The backfill process relies on this specific structure to generate spec outlines and artifacts with proper end-to-end extraction and documentation scaffolding.

What is the best way to align undocumented implementation with formal feature requirements?▼

The best way to align undocumented implementation with formal feature requirements is running a deterministic backfill process that extracts scope and architecture plans from existing code, ensuring documentation matches current implementation.

What sections are included in a backfilled spec generated from existing code?▼

A backfilled spec generated from existing code includes sections for backfill notice, inferred requirements, user stories, acceptance criteria, and an architecture plan, providing complete documentation scaffolding for your feature.

When should I avoid using automated code-to-spec backfill for documentation generation?▼

You should avoid automated code-to-spec backfill when your codebase lacks a .specify/ structure, or when implementation logic is too ambiguous to deterministically infer accurate user stories and requirements from existing tests and documentation.