From n8n-autopilot
Guided interview that turns a rough automation idea into a structured PRP use-case description for n8n workflow building. Asks about inputs, outputs, concrete examples, external systems, volume, and failure handling.
How this skill is triggered — by the user, by Claude, or both
Slash command
/n8n-autopilot:stack-intake "<one-line idea>" (optional — the interview fills in the rest)"<one-line idea>" (optional — the interview fills in the rest)This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Most people can describe **what they want** ("when a lead comes in, research it and tell me if it's
Most people can describe what they want ("when a lead comes in, research it and tell me if it's
worth chasing") but not how to wire it in n8n. This skill bridges that: a friendly, classic
interview that draws out inputs, outputs, and concrete examples, then writes a PRP-style use-case
description that /n8n-autopilot:build-stack-v2 can decompose into a
real workflow stack. You do the n8n thinking; the user only describes their world.
n8nac-cheatsheet / n8n-orchestration-patterns skills, not the user.Use AskUserQuestion for the closed choices (trigger family, volume, error policy, HITL) so the user
just clicks; use plain conversation for the worked example and free descriptions.
$ARGUMENTS if given.)If the user is stuck on a question, offer 2–3 concrete examples to react to rather than leaving it open.
When the sections are covered, synthesize (do not just transcribe) into this structure and write it to
docs/stack-prps/<stack-slug>.prp.md (create the dir; <stack-slug> = kebab-case of the goal). Convert
the user's prose into n8n-flavoured signals where you confidently can, but never invent requirements
they didn't state — mark genuine gaps as OPEN:.
# <Stack name> — Use-Case PRP
> Intake interview <date>. Feeds /n8n-autopilot:build-stack-v2.
## Goal
<one-paragraph outcome>
## Trigger & input
- **Starts via:** <schedule / webhook / form / email / chat / manual>
- **Incoming data:** <fields>
- **Example input:**
```
<the user's one real case, trigger → output, in clear steps>
<one item vs list; rough count; implication for fan-out / batching>
<stop-and-alert / skip-and-continue / retry, per the user's answer>
<any approval/review steps, or "none">
<your read: likely leaves, where a fan-out/fan-in applies, error/large-data boundaries, the entry orchestrator>
## Hand off
After writing the file, show the user a short summary and offer the next step verbatim:
> PRP written to `docs/stack-prps/<slug>.prp.md`. Run it with:
> `/n8n-autopilot:build-stack-v2 "<paste the Goal + key sections, or 'see docs/stack-prps/<slug>.prp.md'>"`
Do **not** auto-run build-stack-v2 — building deploys workflows to the instance; that needs an explicit
go from the user. If they confirm, pass the PRP content as the `description` arg to build-stack-v2.
## Limits
- This skill only **plans** — it never touches the n8n instance and writes nothing but the PRP file.
- The quality of the stack depends on the worked example. If the user can't give one concrete case,
say so in the PRP (`OPEN: no concrete example`) rather than guessing the behavior.
npx claudepluginhub neurawork-git/n8n-autopilot --plugin n8n-autopilotDesigns visual n8n workflows with trigger selection, node mapping, data transformations, error handling, and webhook integration. Activates when users mention n8n workflows or automation.
Converts discovery call transcripts into actionable n8n Automation Blueprints via fact extraction and interactive questions. For turning client requirements into engineer-ready workflow specs.
Builds and deploys n8n workflows end-to-end via a 3-phase pipeline: research, write/validate, deploy/test/inspect.