Loading...
Loading...
Onboarding a new developer is one of the most resource-intensive processes in a software organization. The hard part? It requires coordinating multiple tools, systems, and stakeholders just to get a new hire productive.
# PS-03: Autonomous Developer Onboarding Agent ## Background Onboarding a new developer is one of the most resource-intensive processes in a software organization. The hard part? It requires coordinating multiple tools, systems, and stakeholders just to get a new hire productive. Developers must: - Gain access to repositories - Set up tools - Read documentation - Understand architecture - Learn internal processes - Complete compliance tasks While companies use platforms like **GitHub**, **Slack**, **Jira**, and documentation systems like **Notion** or **Confluence**, the onboarding process still relies heavily on manual coordination. This leads to: - Delayed productivity - Repeated explanations - Inconsistent onboarding experiences - Incomplete checklists - Poor visibility into onboarding progress We need a smarter onboarding system — an **intelligent agent** that can autonomously guide new hires, personalize onboarding paths, track progress, and notify HR upon successful completion. --- ## Problem Statement Organizations lack an autonomous onboarding system that can guide new software developers through company processes, personalize their onboarding experience based on role and experience, track completion, and generate structured confirmation to HR — all using a structured company knowledge base. --- ## Objective Build an **Advanced Agentic Onboarding Platform** that: 1. **Guides** new employees step-by-step via a chat-based interface *(Mandatory)* 2. **Personalizes** onboarding based on: - Role (Backend / Frontend / DevOps) - Experience Level (Intern / Junior / Senior) - Tech Stack (Python / Node / Java, etc.) 3. **Uses** a provided structured knowledge base with retrieval (RAG-style) 4. **Completes** an onboarding checklist 5. **Sends** a structured completion email to HR *(Mandatory)* --- ## Target Users - New Interns - Software Engineers (Junior to Senior) - HR Teams - Engineering Managers - DevOps Teams --- ## Expected Solution Features ### 1. Personalized Onboarding Flow - Ask structured onboarding questions - Identify the employee persona (role, tech stack, experience level) - Dynamically generate a customized onboarding path ### 2. Knowledge Base Integration - Retrieve relevant company documentation (policies, setup guides, engineering standards) - Answer contextual queries accurately while referencing source documents - Avoid hallucinated information ### 3. Checklist Tracking - Maintain a structured onboarding checklist - Track completed tasks - Clearly indicate onboarding status (**In Progress** / **Completed**) ### 4. HR Notification System Upon completion, send a structured summary email including: - Employee name - Role and team - Completed items - Pending tasks (if any) - Timestamp of completion - Optional confidence score --- ## Constraints - **Must** implement chat-based onboarding interface - **Must** generate structured HR email - **Should** avoid hallucination beyond knowledge base - Focus on agent intelligence over number of integrations - Integration APIs may be mocked --- ## Example Workflows & Interactions ### Example Interaction > **User:** "Hi, I'm Riya. I've joined as a Backend Intern working on Node.js." **Agent should:** 1. Identify persona 2. Provide setup steps 3. Share backend docs 4. Guide environment setup 5. Provide a small starter task 6. Mark the checklist complete 7. Send the HR completion email ### Personalized Onboarding Flow Examples | Persona | Onboarding Steps | |---|---| | **Backend Intern (Node.js)** | Set up Node environment → Clone repository → Run local server → Review backend architecture doc → Read API standards → Complete starter bug fix | | **Frontend Senior (React)** | Review frontend architecture → Access design system → Understand deployment pipeline → Review PR guidelines | --- ## Bonus (Optional) - Provision or request access for GitHub, Slack, and Jira - Send an automated Slack welcome message - Assign Jira or GitHub starter tickets - Automatically verify local environment setup - Track checklist completion dynamically within the chat - Update the internal knowledge base with new FAQs generated during onboarding - Ingest PDFs instead of Markdowns in the vectorDB to align more with practical use - Use Model Context Protocol (MCP) style architecture for modular design --- ## Evaluation Criteria | Criteria | Weight | |---|---| | **Agent Intelligence** – Personalization quality, logical onboarding sequencing, context awareness | 30% | | **Knowledge Retrieval Quality** – Accurate document referencing, minimal hallucination | 20% | | **System Architecture** – Modular design, agent workflow clarity, scalability | 20% | | **Completion Reporting** – Professional HR email, structured reporting | 10% | | **Innovation** – Novel interaction design, adaptive learning behavior | 10% | | **Bonus Integrations** – GitHub / Slack / Jira automation, MCP usage | 10% | --- ## Deliverables 1. Working prototype 2. 5–7 minute demo video 3. Architecture diagram 4. Presentation (max 10 slides) 5. Sample onboarding walkthrough (Intern → Completed → HR email) --- ## Provided Dataset / Resources PS03`
An AI client and API for WordPress to communicate with any generative AI models of various capabilities using a uniform API. Built on top of the [PHP AI Client](https://github.com/WordPress/php-ai-client), it provides a WordPress-native Prompt Builder, an Admin Settings Screen for credentials, automatic credential wiring, a PSR-compliant HTTP client, and a client-side JavaScript API.
> This file provides instructions for AI agents that read AGENTS.md (GitHub Copilot, Cursor, Windsurf, Cline, Aider, OpenCode, and others).
This document collects ideas and instructions for implementing future improvements. Follow these when adding features or refactoring the code.
> This file must stay **in sync** with `CLAUDE.md`. Whenever you change one, mirror the same change in the other so both tools continue to work correctly.