skills.rest
dmitriyb
dmitriybCOMMUNITY
Explore all skills by this author →
GitHub

converge

Execute a spec-driven pipeline in Spex Machina to convert proposal changes into spec updates.

4|Updated Feb 24, 2026
Search Tags:#code changes#spec management#pipeline execution#automated update#Spex Machina
One-click install
npx skills add https://github.com/dmitriyb/spexmachina --skill converge-dmitriyb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: converge
Source: https://github.com/dmitriyb/spexmachina/tree/main/.claude/skills/converge
Command: npx skills add https://github.com/dmitriyb/spexmachina --skill converge-dmitriyb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the execution of a spec-driven pipeline within Spex Machina, simplifying the process of converting proposal changes into actual spec updates.

Core Features & Use Cases

  • Pipeline Execution: Automates the pipeline stages including validate, diff, impact, emit, adapter, and ingest.
  • Preconditions Checking: Ensures that the preconditions for pipeline execution are met before initiating the process.
  • User Confirmation: Requires user confirmation before applying changes to the tracker, ensuring careful consideration of changes.
  • Error Diagnosis: Diagnoses stage failures and provides actionable next steps, without auto-fixing issues.

Quick Start

Execute the 'converge' skill with a proposal stem to initiate the pipeline.

Frequently Asked Questions about converge

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

FAQPage Schema
How do I automate spec updates from code changes in Spex Machina?▼

You can automate spec updates by executing a spec-driven pipeline that converts proposal changes into tracker updates after validating preconditions and confirming with the user.

What pipeline stages are required to convert proposals into spec updates?▼

Converting proposals into spec updates requires passing through validate, diff, impact, emit, adapter, and ingest pipeline stages to identify affected beads and apply tracker changes.

Can I automatically apply proposal changes to the tracker without user confirmation?▼

No, the pipeline requires user confirmation before applying changes to the tracker, ensuring careful consideration of all spec modifications.

Does the converge pipeline auto-fix stage failures during spec execution?▼

No, the pipeline does not auto-fix stage failures during spec execution; it diagnoses failures and provides actionable next steps for manual resolution.

What happens if preconditions for pipeline execution are not met in Spex Machina?▼

If preconditions for pipeline execution are not met, the process halts before initiating the pipeline stages, preventing invalid proposal changes from affecting the spec tracker.

Related Skills

Explore More Software Engineering Skills→
davidrrowleydavidrrowley

azure-validate

Validate Azure deployment readiness with preflight checks and policy validations.

Community
Advanced
montoyaedumontoyaedu

start

Orchestrate BEADS workflows for GitHub Issues with agent swarm coordination.

Community
Advanced
s1366560s1366560
5

gitnexus-impact-analysis

Analyze code change impact by mapping upstream dependencies and affected execution flows.

Community
Intermediate
madebyarismadebyaris
192

sdd-evolve

Update specification files and changelog after implementation discoveries.

Community
Intermediate