specflow-spec-editorlisted

Execute spec changes against the spec tree — create new specs, edit existing specs, manage bidirectional links, update folder overviews, and run coherence checks. This is the skill that actually modifies spec files. Use this skill whenever a change plan needs to be executed against specs — whether that plan comes from the change-router, from specflow-bugs, from specflow-ingest, or from a direct human instruction. PROACTIVELY trigger when: the change-router has classified a request and the next step is editing specs; a bug diagnosis produces a change plan that requires spec modification; an ingest manifest has approved changes to apply; the user says "update the spec", "add this criterion", "create a new spec", "change the rule", "add a business spec", "link these specs", "update the overview", "wire implements", "deprecate this spec", "move this spec", or any instruction that means modifying files in .specflow/specs/ or .specflow/specs-business/. If someone says "edit" or "change" and the target is a spec fil
pedropacheco95/cortex · ★ 1 · Code & Development · score 74

Install: claude install-skill pedropacheco95/cortex

# Specflow: Spec Editor ## Purpose This skill executes spec changes. Every other Specflow skill either diagnoses, proposes, or routes — this one actually opens spec files, modifies them, and ensures the spec tree stays coherent afterward. **The editor is the only skill that writes to `.specflow/specs/` and `.specflow/specs-business/`.** Other skills read the spec tree; this one modifies it. This single point of mutation makes it possible to enforce consistency rules (coherence check, link integrity, overview freshness) in one place. ## When to Use This skill activates after a change has been classified and approved. It receives instructions from one of these sources: | Source | What it provides | Editor's job | |--------|-----------------|-------------| | **Change-router** | Classified request (Category 3-5) with affected specs identified | Execute the spec modification | | **specflow-bugs** | Change plan with specific rule/criterion edits | Apply the plan to the spec files | | **specflow-ingest** | Change manifest with drafted specs and modifications | Create/edit specs per the manifest | | **Human directly** | "Add a rule to this spec", "create a new spec for X" | Interpret and execute | ## Cortex Awareness When the project has a `.cortex/` directory: - **Check `governed_by:` before editing.** When a dev spec carries `governed_by:` (compass rule IDs, design §8.4 bridge 1), read the referenced `.cortex/compass/rules/R-*.md` files before modifying the spec — an e