re-spec

Validate spec.md structure and assess SHA impacts after git reset operations.

Updated May 7, 2026
One-click install
npx skills add https://github.com/AtaraxiaEpiphany/conductor --skill re-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: re-spec
Source: https://github.com/AtaraxiaEpiphany/conductor/tree/main/skills/re-spec
Command: npx skills add https://github.com/AtaraxiaEpiphany/conductor --skill re-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the ambiguity and risk associated with modifying project specifications mid-track after a git reset, ensuring that changes to acceptance criteria or constraints are tracked without silently invalidating completed work.

Core Features & Use Cases

  • Spec Integrity Management: Validates spec.md structure before and after edits to prevent parser degradation.
  • Blast-Radius Analysis: Identifies completed tasks whose SHAs may be invalidated by new acceptance criteria, allowing for informed manual reconciliation.
  • Directive Persistence: Automatically mirrors constraints into the conductor directive channel to ensure they are enforced in future task dispatches.

Quick Start

Use the re-spec skill to update the acceptance criteria for the current track by running the command with the appropriate edit flags.

Frequently Asked Questions about re-spec

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

FAQPage Schema
How do I update acceptance criteria safely after a git reset without invalidating completed task SHAs?

To update acceptance criteria after a git reset safely, use spec-driven validation to analyze the blast radius of changes on completed task SHAs, preventing silent invalidation of work. Structural validation and scoped commits maintain project state consistency.

What is spec-driven blast-radius analysis for specification updates in a conductor workflow?

Spec-driven blast-radius analysis identifies completed tasks whose SHAs may be invalidated by new acceptance criteria. This allows developers to perform informed manual reconciliation and ensure state consistency across the project.

How do I validate spec.md structure before committing constraint changes mid-track?

To validate spec.md structure before committing constraint changes mid-track, enforce strict structural validation before and after edits to prevent parser degradation. Scoped git commits ensure state consistency across the project.

Can I mirror constraints into the conductor directive channel automatically during a git workflow?

Yes, directive persistence automatically mirrors constraints into the conductor directive channel during a git workflow. This ensures new acceptance criteria are enforced in future task dispatches without manual intervention.

Why does modifying project specifications mid-track create state management risks?

Modifying project specifications mid-track creates state management risks because changing acceptance criteria or constraints can silently invalidate previously completed work. Without strict validation and scoped commits, task SHAs lose consistency.

When should I manually reconcile completed tasks after injecting new constraints into a spec?

You should manually reconcile completed tasks after injecting new constraints when blast-radius analysis identifies previously finished task SHAs that conflict with the updated acceptance criteria, ensuring project state consistency.