[{"data":1,"prerenderedAt":138},["ShallowReactive",2],{"docs-\u002Fdocs\u002Fcustomization\u002Fcreate-workflow":3},{"id":4,"title":5,"body":6,"description":130,"extension":131,"meta":132,"navigation":133,"path":134,"seo":135,"stem":136,"__hash__":137},"docs\u002Fdocs\u002Fcustomization\u002Fcreate-workflow.md","Build your own workflow",{"type":7,"value":8,"toc":122},"minimark",[9,13,22,27,30,36,41,46,57,61,71,75,78,83,88,91,95,98,101,106,110,117],[10,11,5],"h1",{"id":12},"build-your-own-workflow",[14,15,16,17,21],"p",{},"User workflows live in ",[18,19,20],"code",{},"~\u002F.slo\u002Fuser_workflows\u002F"," and sit alongside the built-in Feature Specifications and Code-Test-Review workflows. The easiest way to create one is to ask Slo to do it for you.",[23,24,26],"h2",{"id":25},"ask-slo-to-build-the-workflow","Ask Slo to build the workflow",[14,28,29],{},"Describe what your workflow should do in plain language:",[31,32,33],"blockquote",{},[14,34,35],{},"\"Create a user workflow for our deployment process — it should check for open PRs, run the test suite, tag the release, and post to Slack.\"",[31,37,38],{},[14,39,40],{},"\"Build me a workflow that takes a raw bug report and produces a triage document with a severity rating, affected files, and a suggested fix.\"",[31,42,43],{},[14,44,45],{},"\"I want a workflow that reviews all open GitHub issues every Monday morning and produces a priority-ordered list for the team standup.\"",[14,47,48,49,52,53,56],{},"Slo uses its built-in ",[18,50,51],{},"create-user-workflow"," skill to scaffold the workflow, define the steps, and save it to ",[18,54,55],{},"~\u002F.slo\u002Fuser_workflows\u002F\u003Cyour-workflow-name>\u002F",".",[23,58,60],{"id":59},"what-slo-creates","What Slo creates",[62,63,68],"pre",{"className":64,"code":66,"language":67},[65],"language-text","~\u002F.slo\u002Fuser_workflows\u002F\n  your-workflow-name\u002F\n    WORKFLOW.md       ← orchestration steps\n    phases\u002F           ← one file per phase (optional)\n","text",[18,69,66],{"__ignoreMap":70},"",[23,72,74],{"id":73},"running-your-workflow","Running your workflow",[14,76,77],{},"Once created, trigger it like any built-in workflow — just describe the goal:",[31,79,80],{},[14,81,82],{},"\"Run the deployment workflow for the staging environment.\"",[31,84,85],{},[14,86,87],{},"\"Run the Monday triage workflow.\"",[14,89,90],{},"Slo recognises the intent and runs your workflow's phases in order.",[23,92,94],{"id":93},"composing-skills-inside-a-workflow","Composing skills inside a workflow",[14,96,97],{},"Workflows can reference skills by name or describe what each phase should do. Slo loads the relevant skills automatically for each step.",[14,99,100],{},"If a phase needs a specific skill, mention it in your workflow description:",[31,102,103],{},[14,104,105],{},"\"The second phase should use the code-review skill with a thorough audit.\"",[23,107,109],{"id":108},"editing-a-workflow-later","Editing a workflow later",[14,111,112,113,116],{},"Workflow files are plain markdown. Open ",[18,114,115],{},"~\u002F.slo\u002Fuser_workflows\u002F\u003Cworkflow-name>\u002FWORKFLOW.md"," and update the steps directly. You can also ask Slo to revise it:",[31,118,119],{},[14,120,121],{},"\"Update the deployment workflow to also create a GitHub release after tagging.\"",{"title":70,"searchDepth":123,"depth":123,"links":124},2,[125,126,127,128,129],{"id":25,"depth":123,"text":26},{"id":59,"depth":123,"text":60},{"id":73,"depth":123,"text":74},{"id":93,"depth":123,"text":94},{"id":108,"depth":123,"text":109},"Ask Slo to create a custom multi-step workflow tailored to your team's process.","md",{},true,"\u002Fdocs\u002Fcustomization\u002Fcreate-workflow",{"title":5,"description":130},"docs\u002Fcustomization\u002Fcreate-workflow","6kBdkvYDBJTaOSkNyTAWId5jpJun4VcPih6K_pBDErs",1782392848392]