spec-refine

Refines existing LiveSpec artifacts through guided conversation with diff-based edits.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/julien-m/livespec --skill spec-refine-julien-m
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-refine
Source: https://github.com/julien-m/livespec/tree/main/.agent-sync/skills/spec-refine
Command: npx skills add https://github.com/julien-m/livespec --skill spec-refine-julien-m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Specs drift out of date as requirements evolve, but editing them freely breaks traceability with plans and code. This Skill updates LiveSpec project profiles, feature specs, and plans through a controlled, conversation-driven refinement flow that preserves requirement IDs and downstream consistency. ## Core Features & Use Cases - Eligibility gating: Blocks refinement of specs or plans already consumed by implementation, preventing traceability breakage. - Diff-based editing: Presents before/after diffs for every change, never regenerates files from scratch, and never renumbers existing AC/FR identifiers. - Roadmap re-evaluation: Re-runs the inference matrix after project-level changes to propose new, stale, or modified roadmap items. - Use Case: A product owner needs to add a new user role and acceptance criteria to a Draft feature spec; the Skill asks targeted questions, shows the diff, applies it, updates changelogs, and warns that the plan needs regeneration. ## Quick Start Ask the AI to run /spec-refine on a feature number or project to interactively refine that spec artifact with guided questions and confirmed diffs.

Frequently Asked Questions about spec-refine

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

FAQPage Schema
How do I refine an existing feature spec without breaking traceability?

Run /spec-refine with the feature number or name. It checks eligibility, asks targeted questions, shows a before/after diff, and applies changes while preserving all existing AC and FR numbering so @spec anchors in code remain valid.

When is a spec or plan blocked from refinement?

Specs with status In Progress, Implemented, or Deprecated cannot be refined because code already exists. Plans are blocked once implementation.md exists. The Skill suggests creating a new feature or running /spec-check instead.

Does spec-refine renumber acceptance criteria when items are removed?

No, existing AC, FR, and SC numbers never change, even after removals. New items take the next number after the highest existing one, and gaps in numbering are explicitly acceptable to protect code anchors.

What happens to the roadmap after project-level refinement?

After project.md changes, the Skill re-runs the inference matrix and proposes a delta of new, stale, or modified roadmap items with a before/after diff. Changes apply only after confirmation unless --auto is set.

Can I preview spec changes without applying them?

Yes, use the --dry-run flag to display proposed diffs and roadmap deltas without writing anything. The --auto flag does the opposite, applying confirmed changes without interactive prompts.