Turn your process into a workflow your AI runs on its own.
Stop explaining the same thing over and over. Map out the process you repeat, pick a trigger, and your AI follows the steps whenever you ask, or automatically after a commit, deploy or error.
- 1 Map your processThe steps you keep explaining, in order. Drag them onto the canvas or describe them in a sentence.
- 2 Pick the triggerOn request, or automatically after a commit, deploy or error, or on a schedule.
- 3 That’s itFrom then on, your AI follows your process every time, and you never explain it again.
Work with AI without repeating yourself. Stop explaining the same thing every time.
Explaining the same process. Again.
Every chat starts from scratch. You retype the same daily steps, and each time you forget a different detail.
With workflows
- Map the process once
- One line kicks it all off
- Works for everyone on the team
Your AI skips the step that matters.
Tests ran, the push went out, but the security review never happened. Nobody noticed until something broke.
With workflows
- Steps run in your order
- Skipped steps always come with a reason
- Waits for tests before moving on
Your best skills go unused.
You installed great skills, but the AI decides whether to use them. Sometimes at the wrong time. Sometimes never.
With workflows
- You decide when each skill runs
- Faundr, project and plugin skills
- Or only when you invoke it
From your words to steps your AI follows. Set it up once.
Drag pieces onto the canvas, or just describe how you do it and let /faundr:workflow turn it into a draft. You review, tweak and approve.
Before: what you had to explain every time
"For bugs: reproduce it first, write a failing test, fix the root cause and don’t stop until every test passes. Then tell me what it was."
After: all you type
you › fix the broken login
Your AI recognizes the workflow and runs all 5 steps in order, without you explaining a thing.
Trigger · runs when
You ask about a bug or an error
Or automatically, when a new test fails
- TaskReproduce the errorTriggers the error before touching any code.
- Skill/tddWrites a test that fails because of the bug.
- TaskFix the root causeFixes the problem where it starts.
- Wait untilAll tests passMoves on only when the full suite is green.
- EndExplain the causeWraps up with a one-line explanation of the bug.
On request, or automatically at the right moment. You choose how each workflow starts.
The trigger decides when the workflow starts, with 8 moments to choose from. It works for that skill you use constantly, too: tie it to a moment and it runs automatically, so you don’t have to remember. Works with Faundr skills, project skills, your personal skills and any plugin’s.
When you ask
- Your request matches a topicYou ask about a bug, a test or an error.runs/tdd Plugin
You pick the topics. Words like “bug,” “new screen” or “ship.” If one shows up in your request, the workflow starts.
you › the pay button disappeared, is that a bug?
Automatically, at key moments
- Before editing specific filesThe agent is about to touch supabase/migrations/**.runs/review-db Project
- After a commitReviews what changed and looks for anything that could break.runs/review-pr Personal
- After a push or deployOpens the site and tests login and checkout.runs/check-prod Project
- When a new error appearsA new build, type or test error appeared.runs/faundr:error-fix Faundr
- At the end of each replyThe reply touched the UI.runs/faundr:design Faundr
- When a session startsA new session opens with a recap of where you left off.runs/faundr:resume Faundr
- On a scheduleEvery Friday at 5 pm (Brasília time).runs/weekly-report Personal
Prefer to decide in the moment? Select “only you, in the terminal.” When the moment comes, your AI sends a one-line reminder and waits for you to start it.
Bring your own skills into the workflow. Faundr works with them like its own.
Faundr doesn’t have a research skill? Connect the one you already use. Your project has its own security rules? Connect the skill you wrote for them. It becomes a piece of the workflow, and Faundr calls it at the right step, alongside its own.
- /research Personal
Researching a topic in trusted sources
- /security-audit Plugin Connected · Security
Auditing routes, logins or database rules
- /tdd Personal Connected · Tests
Writing tests or fixing a bug test-first
- /review-pr Project Connected · Quality
Reviewing what changed before a merge
- /debug Plugin Connected · Errors
Something is broken, throwing or slow
- /write-copy Project
Writing or improving page copy
- Any skill becomes a piece. From your repo, your personal folder or any plugin. /faundr:skills reads them all and puts them in the canvas palette, next to Faundr’s.
- Called at the right step. Tie it to a trigger, like a commit, a deploy or a new error, or put it between two steps. Faundr runs it when the workflow gets there.
- Your skills stay yours. Only each skill’s name, description and where it comes from leave your computer. Never its instructions.
Decide how much Faundr automates. Turn each step on or off.
Everything Faundr does automatically is mapped out: 9 automatic moments and 33 skills. Don’t want the Project overview updated every day? Turn that step off and it’s skipped in this project.
- Verify it worksCode changed but nothing was verified
- Review the UI designUI changed and the project has a design.md
- Handoff noteAfter 4 files or 20 min of edits
- Verify the feature is doneThe checklist was just completed
- Update the Project stackThe stack changed since the last review
- Update the Project overviewOverview is more than 24 hours old
See exactly which step your AI is on. Follow along without opening the terminal.
Your dashboard tracks the process as the AI works: what’s done, what got skipped and why, and when it needs your input.
- 1Run testsauto-checked: command passedDone
- 2/faundr:securityauto-checked: skill was calledDone
- 3Update the changelogno user-facing changes in this releaseSkipped
- 4Ship now or wait for the review?Waiting on you
Your AI does what you ask. With a workflow, it does it your way.
On its own, the AI figures out how to work, chat by chat. With a workflow, your process becomes a playbook it always follows, right on cue.
FAQ
Do I need to code to build a workflow?
No. Describe how you do it in plain language and /faundr:workflow builds the draft. Or drag pieces onto the canvas. Each one is named for what it does (task, skill, command, wait for you).
Does it work with non-Faundr skills?
Yes. /faundr:skills finds your repo’s skills, your personal ones and those from your installed plugins. You choose when each one runs and who can invoke it. Skills that find problems, like a security audit, also send their findings to your dashboard, tagged “via /name.”
Can the AI change my workflows on its own?
No. It can only create drafts. Approving, editing, disabling and deleting are up to the project owner, in the dashboard.
Does it use more tokens?
Triggers are detected locally, without AI. The steps use your AI plan like any other request. The “end of each reply” trigger runs after every reply, so the dashboard warns you it costs more.
What if I turn off one of Faundr’s steps?
That step gets skipped in this project. Turn it back on any time; the diagram shows it grayed out.