Skip to content

gustavo-meilus/superpipelines / plugins/superpipelines/skills/deleting-a-pipeline-step

deleting-a-pipeline-step

Verified

Remove a step from an existing named Superpipelines workflow while preserving topology continuity.

Deleting a Pipeline Step — Removal Workflow

Workflow Phases

PHASE 1: GAP ANALYSIS

  • Analyze the impact of removal on predecessors and successors.
  • If a Blocking-gap is found (no alternative input source), STOP. The user must provide an alternative source or cancel the deletion.

PHASE 2: MUTATION DESIGN (REWIRE)

  • For through-gaps or entry-gaps, present a rewire plan to the user (e.g., "Wire A directly to C").
  • Dispatch pipeline-architect in STEP-DELETE mode to stage all changes.
  • All mutations (file removals and topology updates) MUST be staged in edit-{ts}/. NEVER delete directly from production paths during design.
  • Architect completion manifest gate: After the architect returns, read the STEP-DELETE completion manifest. It MUST cover every file the architect was tasked with touching and use only edited, copied-unchanged, or deleted.
    • If any expected markdown artifact (*.md) is listed as copied-unchanged, STOP before Phase 3. Emit a blocking error naming the file and explain that unchanged markdown in STEP-DELETE staging indicates an architect partial exit.
    • If any expected file is missing from the manifest, STOP before Phase 3. The staging set is incomplete and cannot be audited as a coherent delta.
  • Staged markdown modification guard: Independently diff every staged *.md file against its production original before Phase 3. If the staged file has a production source and is byte-identical to that source, STOP before Phase 3 with a blocking error naming both paths. This guard is independent of the manifest and catches partial exits even when the manifest is wrong or missing detail.
  • Pre-audit residual-reference scan: Prefer the Phase 3 delta auditor as the authoritative gate. If a manual grep is run as an additional pre-audit smoke check, it MUST explicitly include markdown files (for example, --include="*.md") so .md artifacts cannot be silently skipped.

PHASE 3: DELTA AUDIT

  • Dispatch pipeline-auditor in DELTA mode on the staged topology, entry skill, and neighbor steps.
  • SEV-0 or SEV-1 findings block deletion. A fragmented pipeline is a critical failure. Re-audit until the delta is clear.

PHASE 4: HUMAN APPROVAL

  • Present a "Deletion Manifest" showing exactly which files will be removed and which edges will be rewired.
  • Wait for explicit APPROVE. On CANCEL, discard all staged changes and do NOT delete artifacts.

PHASE 5: ATOMIC PROMOTION

  • Execute file removals (agents/skills) and write updated topology.json and tasks.md.
  • Update the registry.json to reflect the removal.
  • Version Stamp: Update plugin_version in topology.json and the registry entry to the current superpipelines version.

Red Flags — STOP

  • "The pipeline will work without rewiring — it's obvious." → STOP. Obvious assumptions are the leading source of silent runtime failures.
  • "I'll skip the human gate; deletion is a simple task." → STOP. Deletion is irreversible; the human gate is the final recovery point.
  • "I'll delete the files first, then update the topology." → STOP. This results in a broken pipeline if the topology update fails.

Rationalization Table

<rationalization_table>

ExcuseReality
"The step is terminal, why audit?"Removing a terminal step can still break final status reporting or cleanup logic.
"Rewiring is over-engineering."A broken dependency chain blocks every subsequent pipeline run. Rewiring is essential maintenance.
"I can recover from git if I'm wrong."Relying on git recovery for basic workflow errors indicates a failure of the safety protocol.
</rationalization_table>

Reference Files

  • sk-pipeline-paths/SKILL.md — Path resolution.
  • sk-pipeline-state/SKILL.md — Run state tracking.
  • adding-a-pipeline-step/SKILL.md — Insertion workflow.
  • updating-a-pipeline-step/SKILL.md — Modification workflow.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall