n8n-studio:start

Coordinate end-to-end n8n workflow development with tmux panes and RALF retry cycles.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/icednut/n8n-studio --skill n8n-studio-start
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: n8n-studio:start
Source: https://github.com/icednut/n8n-studio/tree/main/skills/start
Command: npx skills add https://github.com/icednut/n8n-studio --skill n8n-studio-start

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of repeatedly creating, modifying, and debugging n8n workflows with a consistent, end-to-end development process instead of ad-hoc changes.

Core Features & Use Cases

  • Eight-step workflow development orchestration: coordinates request classification, planning/spec writing, design, TDD-style development, optional refactoring, verification with an RALF retry loop, and finalization with PR creation.
  • Tmux-based sub-agent execution: runs each sub-stage in a named tmux pane and relays results back to the Team Lead to continue automatically.
  • Stateful iterative verification (RALF up to 3 cycles): executes integrated acceptance scenarios and triggers targeted re-entry into earlier stages when verification fails.
  • Use Case: When you say you want a new Slack/DM feature or you need to fix a webhook-to-Google-Sheets issue, this skill standardizes the entire cycle from spec through PR.

Quick Start

Tell the AI to “n8n-studio [describe the development/modification/bugfix request]” to generate the spec, design, tests, update the workflow, verify with retries, and create a GitHub PR.

Frequently Asked Questions about n8n-studio:start

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

FAQPage Schema
How do I manage n8n workflow development from spec to GitHub PR?

n8n workflow development from spec to GitHub PR is managed through an eight-step orchestration cycle that coordinates spec writing, design, TDD development, verification with retries, and PR creation. It uses a multi-pane tmux model to standardize the entire end-to-end process.

How does TDD work for n8n workflow integration testing?

TDD for n8n workflow integration testing works by executing acceptance scenarios and verifying them with a RALF retry loop up to three cycles. When verification fails, it triggers targeted re-entry into the planner, designer, or developer stages to fix the workflow.

Can I use tmux to orchestrate multi-agent n8n workflow tasks?

Yes, you can use tmux to orchestrate multi-agent n8n workflow tasks by running each development sub-stage in a named tmux pane. The system dispatches tasks to these panes and relays results back to the Team Lead to continue the cycle automatically.

What is the best way to fix a webhook-to-Google-Sheets issue in n8n?

Fixing a webhook-to-Google-Sheets issue in n8n is best handled by standardizing the cycle from spec through PR. The orchestration model classifies the bugfix request, updates the workflow, runs integration verification, and retries failed stages automatically.

What are the limitations of the RALF retry cycle in n8n workflow verification?

The limitation of the RALF retry cycle in n8n workflow verification is that it runs for a maximum of three cycles. If verification still fails after three targeted re-entries into the earlier development stages, the iterative loop stops.