spec-backfill

Analyze code, docs, and git history to backfill missing specifications.

346|50|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/liza-mas/liza --skill spec-backfill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-backfill
Source: https://github.com/liza-mas/liza/tree/main/skills/spec-backfill
Command: npx skills add https://github.com/liza-mas/liza --skill spec-backfill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams recover and organize missing specifications by analyzing code, existing docs, and historical changes, ensuring alignment between code and its intended behavior.

Core Features & Use Cases

  • Code-to-spec backfill: Detect gaps where code implements functionality without corresponding specs.
  • Gap analysis and conflict detection: Identify mismatches between current code paths and documented specs, and surface conflicts for review.
  • Changelog and archiving: Reconstruct changelogs and move superseded specs to the archive to preserve history.
  • Interactive confirmation workflow: Require explicit user confirmation before generating new specs or archiving existing ones.
  • Stateful progress tracking: Maintain session state to prevent work loss across conversations.

Quick Start

Start a new backfill session on a repository, then review and confirm each gap and generated spec before proceeding.

Frequently Asked Questions about spec-backfill

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

FAQPage Schema
How do I backfill missing specifications from existing code?

To backfill missing specifications, this process analyzes your code, existing documentation, and git history to surface functional boundaries and detect gaps where functionality lacks corresponding specs.

What is code-to-spec traceability and how do I reconstruct it?

Code-to-spec traceability maps implemented functionality to its intended behavior. You reconstruct it by analyzing historical changes and code paths, then updating the spec mapping and changelog to ensure consistency.

How do I detect conflicts between documented specs and current code paths?

Detecting spec conflicts involves analyzing mismatches between your current code paths and documented specifications. The process identifies gaps and surfaces these conflicts for review before any changes are made.

Can I review and confirm generated specs before they are applied to my repository?

Yes, an interactive confirmation workflow requires explicit user confirmation before generating new specs or archiving existing ones, ensuring you maintain control over all specification updates.

How do I archive superseded specs while preserving project history?

You archive superseded specs by moving them to a designated archive during the backfill process. This reconstructs changelogs and preserves historical context while maintaining current spec mapping consistency.

Will I lose my spec mapping progress if the conversation session is interrupted?

No, stateful progress tracking maintains your session state to prevent work loss across conversations, allowing you to resume incremental specification work without losing prior gap analysis.