spec/edit

Name: spec/edit
Availability: InStock
Author: NexusSema

Coordinate specification edits with impact tracking and approval before changes.

5|3|Updated Mar 4, 2026

Search Tags:#workflow #documentation #editing #specification #version-control #cross-references #impact-analysis

Ready to run

npx skills add https://github.com/NexusSema/omg-marketplace --skill spec-edit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec/edit
Source: https://github.com/NexusSema/omg-marketplace/tree/main/plugins/sdlc/skills/spec/edit
Command: npx skills add https://github.com/NexusSema/omg-marketplace --skill spec-edit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Specification changes often ripple across many sections and references, causing stale links and inconsistencies. This Skill provides an end-to-end workflow to propagate edits safely.

Core Features & Use Cases

Micro-file step architecture with four sequential steps: load, impact, apply, and verify.
Automatic term registry, impact mapping, and cross-reference checks to maintain consistency across the document.
Guardrails that require explicit user approval before applying changes, with a detailed verification pass.

Quick Start

Start a 4-step edit session to load the spec, analyze impact, apply changes, and verify consistency.

Frequently Asked Questions about spec/edit

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

FAQPage Schema

How do I edit complex specifications without breaking cross-references?▼

Specification edits without breaking cross-references require a 4-step workflow: load the spec, analyze impact, apply changes, and verify consistency. This process automatically traces ripple effects across architecture docs to prevent stale links.

What is impact analysis in specification version-control?▼

Impact analysis in specification version-control is an automatic mapping step that identifies all downstream cross-reference changes before edits are committed. It enforces mandatory user approval to ensure no stale references slip into architecture docs.

How do I propagate changes across multiple PRD-like architecture docs?▼

To propagate changes across multiple PRD-like architecture docs, initiate a sequential edit session that loads the files, traces the impact across sections, applies the modifications, and runs a verification pass for documentation consistency.

Does the specification editing workflow require manual approval before applying changes?▼

Yes, the specification editing workflow requires explicit user approval before applying changes. Guardrails enforce a mandatory approval gate after impact analysis and before the apply step to ensure safe modifications to requirements.

What are the limitations of automatic impact tracking for requirements docs?▼

A limitation of automatic impact tracking is its reliance on a strict 4-step micro-file architecture via references/step-XX files. Deviating from this load, impact, apply, and verify sequence breaks context preservation and cross-reference checks for requirements.