speckit-refine-update

To refine a spec.md in-place, the Skill modifies the existing file directly within your active feature branch, preserving original formatting while appending a date-stamped refinement note to reflect the new requirements.

In-place spec refinement prevents inconsistent implementations by automatically marking downstream artifacts as stale after updating the specification, ensuring dependent code is flagged for review against the newly recorded changes.

Spec refinement operates within a spec-kit project structure, specifically requiring a .specify/ directory and active feature branches to correctly determine context and apply in-place modifications to your specification.

The best way to iterate on a specification is to refine the existing spec.md in-place, which safely records the new feedback via a date-stamped note and propagates the changes to downstream artifacts without altering your branch structure.

You should use in-place specification modification when you need to update an existing spec.md to reflect new requirements or feedback without creating a new feature branch, ensuring safe propagation of changes to stale downstream artifacts.

Yes, refining an existing specification file preserves your original formatting while appending a date-stamped refinement note, ensuring the document structure remains intact as new requirements are integrated into the spec.md.