The reusable contract and rules for a type of work.
StackOS Library / workflows
Complete workflows for real work.
A workflow gives AI a reusable execution contract from request to verified result. Browse each StackOS workflow and inspect the stages, state, tool boundaries, outputs, and recovery paths inside.
Quick answer
What is AI workflow automation?
AI workflow automation combines a reusable workflow contract with a concrete run plan for the current request. The workflow defines the operating boundary; the run records state, dependencies, scoped tools, outputs, recovery, and verification.
Learn how agentic workflows work →The concrete steps, state, grants, and outputs for this request.
Acceptance criteria and receipts show whether the result is complete.
Three places to start
Check what the job needs and produces.
Compare these workflows before choosing one. The prerequisites and steps below come from the same contracts as their detail pages.
Website SEO Analysis
A reviewed report with a list of pages checked, evidence for each finding, and recommended fixes in priority order. It explains missing data and coverage limits without changing the website.
Before you start
- A reachable website URL and the business problem you want the analysis to help with
- If relevant, priority pages or sections, target markets and anything the agent must leave outside the review
- Optional Search Console, analytics or research access, approved exports and a reporting period; public pages can support a useful analysis when those sources are unavailable
Steps and decisions
What the agent does
- Confirm the website, business goal, sections to inspect and reporting period. Choose representative pages and record what is outside the review.
- Inspect pages, navigation, links, metadata, robots rules and sitemaps. Add connected search or analytics data when available; otherwise work from the public site and record the gaps.
- Have the findings independently reviewed, resolve unsupported claims, and prioritize fixes by likely value, confidence and effort. Include dependencies and a way to check each fix.
- Save the report, list of inspected pages and supporting evidence so someone can check the conclusions and assign follow-up work.
What you provide or decide
- Example request: “Use Website SEO Analysis on [website URL]. Focus on our service pages and guides for UK small businesses. Check navigation, page content and indexing signals. Return findings with evidence, priorities and ways to verify a fix.”
- Name the business goal, important sections, target markets and anything outside the review. Add a reporting period if you want search or analytics data included.
- Connect available tools or supply approved exports. The agent can start from the public site and record the missing data. Review the findings before assigning fixes.
SEO Content Refresh
A reviewed page-edit plan, verified changes when authorized, or a later performance check. Each change keeps its source, review and verification record.
Before you start
- Existing page URLs and the reader or business problem to solve
- Current page content and available search or analytics evidence, from connected tools or approved exports
- To apply changes: an accepted edit plan, permission and a supported editing route. To assess changes: the earlier record, baseline and a comparable later data window.
Steps and decisions
What the agent does
- Confirm the pages, business goal and whether the job is to prepare edits, apply them or assess an earlier refresh. Review existing content and comparable search data.
- Find the reader or technical problem before proposing exact page and link edits. Have the proposal independently reviewed and resolve the findings before applying it.
- Apply only authorized changes, check each result, and keep records of completed, failed or uncertain edits. Inspect an uncertain result before retrying. Preparation stops with the reviewed plan.
- When assessing an earlier refresh, compare later data with the saved baseline and explain the measurement limits. Record inconclusive results when the data cannot support a conclusion, and leave the content unchanged.
What you provide or decide
- Example request: “Use SEO Content Refresh on [page URLs]. Readers should be able to try each method. Keep the URLs and useful links. Show the proposed edits and checks before changing the site.”
- Choose the job: prepare a plan, apply reviewed edits, or assess an earlier refresh. Preparation is the default; applying changes needs permission and a usable editing route.
- Provide current page content, the reader or business goal, and available search or analytics evidence. For an assessment, include the earlier change record and baseline.
- Check the actual edits and the later performance result separately. A page can be successfully updated while its search impact is still unknown.
Engineering Tracked Delivery
A change checked against the original request, with test results, independent review and a recorded release status. The record shows what was completed and what still needs attention.
Before you start
- Repository instructions and source access
- A desired outcome and acceptance boundary
- Authority for the requested file or system changes
Steps and decisions
What the agent does
- Clarify the request, affected users and systems, constraints, and what will count as a successful result.
- Inspect the existing code, choose an approach and checks, then plan tasks in dependency order. Review the plan before implementation.
- Implement authorized tasks, running independent work in parallel when useful. Test and independently review each result before starting dependent work, then check that the pieces work together.
- Compare the finished change with the original request, record test and review results, and state whether it was released or what remains. Close the work only when the evidence supports that status.
What you provide or decide
- Describe the desired outcome, constraints, and authority boundary.
- Review material design choices or production-risk gates.
- Inspect verification, review findings, and residual risk before release.
Agency Setup
One read-back-verified agency profile and, only when exactly selected, a no-launch finance setup handoff.
Brand Foundation Setup
A current brand profile and durable voice guide that future agents can retrieve, apply, test, and update without guessing.
Branding Content Production
A reviewed, evidence-backed piece in the project voice, with channel versions and publication governed by the request's explicit execution intent.
Client Project Setup
One read-back-verified client-project context record and, only when exactly selected, a no-launch finance setup handoff.
Communications Inbox Review
A bounded inbox review with selected messages summarized, classified, and turned into explicit follow-up only when authorized.
Communications Outbound Notification
One approved notification delivered to a named destination with an auditable source and receipt.
Customer Feedback Intake
One route-approved Slack thread containing the complete feedback packet and safe refs for investigation.
Delivery Task Handoff
A delivery-ready tracker task linked back to the approved support thread and handed to engineering without changing the product.
Engineering Tracked Delivery
A change checked against the original request, with test results, independent review and a recorded release status. The record shows what was completed and what still needs attention.
Finance Bookkeeping Preparation and Reconciliation
A reviewed, externally recorded close packet marked prepared/unposted, with matched and exception refs that can be handed to later workflows.
Finance Cashflow Management
A dated external thirteen-week forecast packet with safe evidence/proof refs, uncertainty, exception state, and tax-estimate handoff readiness.
Finance Payment Request
One external payment request linked to a safe Stripe invoice reference, with deterministic mutation recovery and separate owner-approved finalization and send gates; an instructed no-send…
Finance Payment Request Follow-Ups
A safe external follow-up or settlement decision record. Every invoice is suppressed, exception-bound, or eligible for one instructed contact through the selected Stripe resend or SMTP…
Finance Receipt Intake
One verified external receipt record with original evidence retained, safe proof refs, and an IMAP acknowledgement only after the host completes the common intake contract.
Finance Tax Estimates
An external tax-estimate packet with current IRS and FTB source refs, separate projected-annual-liability and current-installment states, CPA/EA review, owner approval, and safe cashflow…
GTM Account Research
A source-linked account brief focused on fit, timing, risks, and the next useful action.
GTM CRM Export Handoff
One approved bounded export with a safe job ref, a retained StackOS artifact when complete, and truthful pending, partial, or failed evidence.
GTM CRM Hygiene Pass
A reviewed hygiene report with narrowly approved corrections and an audit of every changed record.
GTM Customer Follow-Up
One approved message delivered through an exact communication target, with full provider-safe evidence and separately approved CRM follow-up records.
GTM Lead Enrichment And Scoring
A source-linked enrichment and scoring result with confidence, disqualification reasons, and no silent field invention.
GTM Marketing Program Lifecycle
A reviewed marketing-program plan with narrowly approved HubSpot changes, consent decisions isolated behind their own gate, and provider-safe execution evidence.
GTM Outbound Sequence Preparation
A reviewed, project-voiced outreach sequence and send-readiness packet without sending it implicitly.
GTM Pipeline Risk Review
An evidence-backed risk review with prioritized follow-up, owners, and uncertainty clearly separated from fact.
Issue Investigation
An evidence-backed conclusion in the canonical support thread: verified issue, bounded uncertainty, expected behavior, or not a product defect.
Landing Page And Creative Experiment
A launch-ready experiment that connects named variants, destination changes, tracking, guardrails, and one approved provider route.
Marketing Campaign Production
A coherent campaign package with approved messaging, generated assets, landing-page variants, a visual review, and a local evidence gallery.
Media Buying Budget Reallocation Review
An evidence-backed budget recommendation, explicit approval boundary, and observation plan; mutations occur only when separately approved.
Media Buying Campaign Launch
A provider-specific campaign plan that passes launch checks and creates external campaign objects only after approval.
Media Buying Creative Variant Generation
A focused candidate set tied to an experiment hypothesis, with generation and provider upload kept behind separate approvals.
Media Buying Performance Diagnosis
A source-linked diagnosis with ranked hypotheses, evidence gaps, and a recommendation for no change, budget review, creative work, or an experiment.
Project Memory Review
A bounded memory review that explains what the project knows, what remains uncertain, and the best next action.
Rich Telegram Reply
One Telegram reply whose text, media, buttons, and thread context match the approved response contract.
SEO Content Refresh
A reviewed page-edit plan, verified changes when authorized, or a later performance check. Each change keeps its source, review and verification record.
SEO Keyword Research
A reviewed opportunity map choosing refresh, link, create, overlap investigation, deferral or rejection with existing-page evidence and a clear validation handoff.
Telegram Callback Follow-Up
A context-aware follow-up that acknowledges the interaction and performs only the approved next action.
Website SEO Analysis
A reviewed report with a list of pages checked, evidence for each finding, and recommended fixes in priority order. It explains missing data and coverage limits without changing the website.