Features and the workflow
How a feature moves through Skaftor's default delivery workflow, who approves each step, how send-backs work, and how to customise the workflow for your organisation.
A feature's page is the hub for everything about it. The header shows its current step and who it waits on, and a single next-step card tells you what to do. Approvers can "Approve" or "Request changes" right there; everyone else sees who it's waiting for.
The default workflow
New organisations start with the "Enterprise Delivery" workflow:
- Product Documentation — Product Manager. Requirements are drafted from the PRD.
- Requirements Approval — approved by the Product Manager.
- Blueprint Approval — the technical design, approved by the Tech Lead.
- Work Order Creation — Tech Lead. Done when the work-order plan is approved.
- Development — Developer (or a coding agent). Moves on when a pull request is opened.
- Pull Request Review — approved by the Tech Lead.
- Deployment Approval — approved by DevOps.
- QA Approval — approved by QA. A rejection returns the work to Development.
- Release PR — one pull request per repository into the release branch. A person merges them.
- Production Release — DevOps.
Security Review (DevOps) and Compliance Review (Admin) are optional steps you can switch on. An Admin can approve any step.
Send-backs
"Request changes" requires a note and returns the work to the step configured for it — for example, a QA rejection goes back to Development, and a bug work order is filed for the developer.
Customising the workflow
Admins edit the workflow in Settings › "Workflow": add, rename and reorder steps, choose "Who is responsible", "Who must approve before it moves on", and where a send-back returns to. You can add agent-driven steps — such as "Write the design", "Cut the work orders", "Deploy to <env>", "QA agent (browser)" — or your own organisation agents. Use "Check for problems", then publish a new version. Features already in flight keep the version they started on.
Running stages automatically
From a feature's menu choose "Run automatically". Each stage's work starts as soon as the one before it is approved; if something is held, use "Retry stage" or "Retry held work orders". Organisation-wide settings live in Settings › "Automatic runs".