· 6 min read
The Sequential Pipeline pattern chains agents in a fixed order, with each agent completing its work before handing off to the next. The output of stage one becomes the input for stage two, and so on through the entire pipeline. This creates a clear, traceable flow of work where every stage builds on the foundation laid by its predecessor.
Unlike parallel patterns, the Sequential Pipeline deliberately serializes execution. This is not a limitation but a feature. When tasks have genuine dependencies, forcing sequential execution prevents agents from working with incomplete information. Each agent in the pipeline can trust that all prerequisite work has been finished and verified before it begins.
The pattern is particularly well-suited to processes that follow a defined protocol, where steps must occur in a specific order for compliance, quality, or logical reasons. Every stage acts as both a processor and a quality gate, validating the incoming work before adding its own contribution.
Employee onboarding follows a strict dependency chain. You cannot schedule orientation meetings before confirming the start date. You cannot set up tool access before establishing the employee's role and team assignment. You cannot create a personalized learning plan before understanding the role requirements. Each step depends on information produced or confirmed in the previous step.
Onboarding failures typically stem from steps happening out of order or in isolation. A new hire arrives on day one to find their laptop was never ordered because IT was not notified after the offer was signed. Their manager did not prepare a first-week plan because HR never communicated the start date. These are coordination failures that a Sequential Pipeline eliminates by design.
The pipeline also provides accountability. Because each stage produces a documented output that the next stage consumes, it is easy to identify where a breakdown occurred. If the new hire's accounts were not provisioned, you can trace back to see whether the access requirements document was incomplete or whether the provisioning stage failed to execute.
Pre-Arrival Preparation Agent — Takes the signed offer details (role, team, start date, location, employment type) and produces a comprehensive pre-arrival checklist. This agent determines the required hardware and software, identifies the appropriate office or remote setup, generates the equipment procurement request, creates the initial account provisioning list based on the role's standard toolset, and drafts the welcome email with first-day logistics.
Access and Environment Agent — Receives the pre-arrival checklist and executes the technical provisioning steps. This agent creates accounts across required platforms (email, Slack, project management, code repositories, HR systems), configures appropriate permission levels based on role and team, sets up the development environment or workspace as needed, and produces an access credentials document for secure delivery to the new hire.
Knowledge Package Agent — Takes the role specification and team context to assemble a personalized onboarding knowledge package. This agent curates relevant documentation, identifies key processes and workflows the new hire needs to learn, creates a structured reading list prioritized by urgency, compiles a glossary of team-specific terminology and acronyms, and builds a FAQ addressing common questions for the specific role.
Schedule and Connection Agent — Receives the knowledge package and access details to build the first two weeks of the new hire's calendar. This agent schedules one-on-one introductions with team members and key stakeholders, blocks time for completing required training modules, arranges the formal orientation sessions, assigns an onboarding buddy, and creates a day-by-day agenda that balances learning with early contribution opportunities.
Follow-Up and Assessment Agent — Takes the complete onboarding plan and designs the check-in cadence for the first 90 days. This agent creates milestone assessments at 30, 60, and 90 days with specific evaluation criteria, generates feedback survey templates for both the new hire and their manager, identifies early warning signals of onboarding friction, and produces a closing report template that documents what worked and what should improve.
Step 1 — Offer-to-checklist conversion. The Pre-Arrival Preparation Agent receives the signed offer letter details and the team's standard onboarding requirements. It produces a detailed checklist: "Order MacBook Pro 16-inch, provision AWS developer access, assign desk 4B-12, draft welcome email to be sent three days before start date." Every item has an owner and a deadline relative to the start date.
Step 2 — Technical provisioning. The Access and Environment Agent works through the checklist systematically. It creates the Google Workspace account, adds the hire to the appropriate Slack channels, provisions repository access at the correct permission level, sets up the VPN credentials, and configures the project management tool with the team's board views. It produces a provisioning completion report noting any items that could not be auto-provisioned and require manual intervention.
Step 3 — Knowledge curation. The Knowledge Package Agent reviews the role description and team documentation to assemble a tailored onboarding library. For a new product manager, this might include the product strategy document, competitive landscape overview, recent user research summaries, the sprint planning guide, and a stakeholder map. Each item is annotated with why it matters and when to read it during the first two weeks.
Step 4 — Calendar construction. The Schedule and Connection Agent cross-references the knowledge package timeline with team members' availability to build the onboarding calendar. Day one includes the welcome meeting, security training, and a team lunch. The first week balances documentation review with introductory one-on-ones. The second week introduces the new hire to ongoing projects with low-stakes initial tasks.
Step 5 — Assessment framework. The Follow-Up and Assessment Agent designs the feedback loops. It creates specific 30-day milestones ("Can independently run a sprint planning session"), 60-day milestones ("Has shipped one feature end-to-end"), and 90-day milestones ("Owns a product area with minimal supervision"). Each milestone includes evaluation rubrics and suggested conversation guides for the manager.
Step 6 — Complete onboarding package delivery. The pipeline outputs the full onboarding package: the provisioning status report, the knowledge library with reading schedule, the two-week calendar with all meetings booked, the 90-day milestone plan, and an onboarding health dashboard that tracks completion of each planned activity.
The final onboarding package would contain the following deliverables:
Pre-Arrival Status Report — Equipment order confirmation (MacBook Pro shipped, arriving two days before start date), welcome email draft approved by hiring manager and scheduled for delivery, desk assignment confirmed with facilities, parking pass activated.
Provisioning Completion Log — Fifteen accounts created and verified: Google Workspace, Slack (added to #engineering, #product-team, #company-all), GitHub (contributor access to three repositories), Jira (product-team board), Figma (viewer access), AWS (read-only staging environment). Two items flagged for manual action: VPN token requires in-person activation, and legacy CRM access needs manager approval via IT ticket.
Personalized Knowledge Package — Twenty-two documents organized into three priority tiers. Tier 1 (read before day one): company handbook, team charter, product vision document. Tier 2 (read during week one): competitive analysis, user persona profiles, technical architecture overview. Tier 3 (read during week two): quarterly OKRs, historical retrospective summaries, vendor relationship guide.
Two-Week Calendar — Day-by-day agenda with forty-two scheduled events including eight one-on-ones, three training sessions, two team ceremonies, daily morning check-ins with the onboarding buddy, and designated focus blocks for documentation review.
90-Day Assessment Framework — Three milestone reviews with specific criteria, five pulse-check survey templates, a manager conversation guide for each check-in, and escalation triggers (if the new hire reports confusion about role expectations at the 30-day mark, escalate to HR business partner).