speckit-refine-propagate

Propagate refined specifications to plan.md and tasks.md while preserving existing content.

2|Updated Jan 29, 2026

Search Tags:#automation #spec #tasks #plan #spec-kit #propagation

Ready to run

npx skills add https://github.com/pradeepmouli/lspeasy --skill speckit-refine-propagate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-refine-propagate
Source: https://github.com/pradeepmouli/lspeasy/tree/main/.github/skills/speckit-refine-propagate
Command: npx skills add https://github.com/pradeepmouli/lspeasy --skill speckit-refine-propagate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Propagate refined specifications to plan.md and tasks.md without regenerating them from scratch.

Core Features & Use Cases

Cascade refined specs to plan.md and tasks.md automatically while preserving existing content
Perform surgical updates based on refinement state and status
Prerequisites: .specify/ directory exists, the refined spec.md is present; plan.md and tasks.md exist

Quick Start

Run /speckit.refine.update to cascade refined spec changes downstream to plan.md and tasks.md.

Frequently Asked Questions about speckit-refine-propagate

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

FAQPage Schema

How do I update plan.md and tasks.md after refining a spec without regenerating them?▼

To propagate refined specifications without regenerating downstream artifacts, run the update command to cascade spec.md changes to plan.md and tasks.md. It performs surgical updates based on refinement state while preserving existing content and formatting.

What is spec propagation in spec-kit projects?▼

Spec propagation is the process of cascading refined specifications from spec.md to downstream artifacts like plan.md and tasks.md. It ensures traceability by adding propagation notes and validating consistency without regenerating the files from scratch.

Do I need a .specify directory to propagate spec changes to tasks?▼

Yes, you need a .specify directory containing a refined spec.md, along with existing plan.md and tasks.md files. These prerequisites are required to perform surgical updates and maintain traceability during the propagation process.

Can I cascade spec refinements to downstream artifacts while preserving existing content?▼

Yes, you can cascade refined specs to plan.md and tasks.md automatically while preserving existing content. The propagation process targets only the necessary updates based on refinement state and status, ensuring formatting and traceability are maintained.

What's the best way to maintain traceability between spec.md and downstream plan/tasks files?▼

The best way to maintain traceability is using a propagation tool that adds propagation notes and validates consistency between spec.md and downstream artifacts. This ensures surgical updates without regenerating plan.md and tasks.md from scratch.

Why does spec propagation fail when plan.md or tasks.md are missing?▼

Spec propagation requires existing plan.md and tasks.md files to perform surgical updates. Without these downstream artifacts present in the .specify directory, the propagation process cannot cascade refined spec.md changes while preserving existing content and formatting.