Skip to content

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

adding-a-pipeline-step

Verified

Add a new step, capability, or agent to an existing named Superpipelines workflow.

Adding a Pipeline Step — Mutation Workflow

Workflow Phases

PHASE 1: INSERTION DESIGN

  • Identify the insertion point (Before/After/Parallel/Append) and affected neighbors.
  • Apply the 4D Method to define the new step's intent, inputs, and outputs.
  • Determine the component type: Skill-only, Skill + Agent, or Reuse Existing.

PHASE 2: ARCHITECTED STAGING

  • Dispatch pipeline-architect in STEP-ADD mode to generate new artifacts.
  • All new artifacts MUST be written to {ROOT}/superpipelines/temp/{P}/edit-{ts}/ for staging. NEVER write directly to production paths during design.

PHASE 3: TOPOLOGY VALIDATION

  • Verify the staged topology.json for:
    • Unique Step ID.
    • Valid depends_on references.
    • Schema compatibility between predecessor outputs and new step inputs.
  • Failures: Return to the Architect with specific error logs.

PHASE 4: DELTA AUDIT

  • Dispatch pipeline-auditor in DELTA mode on all staged files (components, topology, and entry skill).
  • If the audit returns SEV-0 or SEV-1 findings, remediate and re-audit. Do NOT proceed to promotion until the delta is clear.

PHASE 5: PROMOTION & REGISTRATION

  • Present the updated topology and audit results for human approval (AskUserQuestion).
  • Upon APPROVE, move staged files to their final absolute paths in agents, skills, and pipeline directories.
  • Update the registry.json lists to include new components.
  • Version Stamp: Update plugin_version in topology.json, the registry entry, and the new agent's frontmatter to the current superpipelines version.

Red Flags — STOP

  • "The audit found minor issues, let's promote anyway." → STOP. SEV-0/1 findings are hard blockers for promotion.
  • "I'll write directly to production paths to save time." → STOP. Direct writes bypass the mutation safety protocol.
  • "The insertion point looks obvious, skip validation." → STOP. Topology validation catches silent edge mismatches.

Rationalization Table

<rationalization_table>

ExcuseReality
"Staging is extra overhead."Staging allows for a rollback if the audit or human review fails. Direct writes are permanent and destructive.
"Topology validation is redundant."Manual inspection often misses transitive dependency breaks caused by insertion.
"Minor audit findings won't break it."Even SEV-1 findings can cause context leakage or state corruption during execution.
</rationalization_table>

Reference Files

  • sk-pipeline-paths/SKILL.md — Path resolution.
  • sk-4d-method/SKILL.md — Brief refinement.
  • creating-a-pipeline/SKILL.md — Core scaffolding rules.
  • deleting-a-pipeline-step/SKILL.md — Removal workflow.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 321kUpdated 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: 197kUpdated 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