agentsclimarketplace

Plan & spec

10,724 rows, by stacks then stars

2,010 of these skill files have been read, by 1,360 distinct authors, and what they tell an agent counted. What Plan & spec authors agree on, and what they forbid

  • Deployment strategy

    vignesh2027/AI-AGENT-SKILLS/skills/deployment-strategy Skill

    2★ repo

    Deploy with rollback plans, staged rollouts, and feature flags

  • Planning and task breakdown

    vignesh2027/AI-AGENT-SKILLS/skills/planning-and-task-breakdown Skill

    2★ repo

    Decompose work into atomic, independently verifiable tasks

  • Spec driven development

    vignesh2027/AI-AGENT-SKILLS/skills/spec-driven-development Skill

    2★ repo

    Write a specification before writing any implementation code

  • Decompose to issues

    wakqasahmed/ai-engineering-workflow-skills/skills/engineering/decompose-to-issues Skill

    2★ repo

    Break high-level work into independently executable GitHub issues using vertical slices. Use when a plan, PRD, roadmap item, or vague feature needs issue-sized execution units.

  • To prd

    wakqasahmed/ai-engineering-workflow-skills/skills/engineering/to-prd Skill

    2★ repo

    Synthesize the current conversation and repository context into a concise product and engineering spec, publish it to the project issue tracker, and gate agent readiness before decomposition. Use when high-level work needs product framing, implementation and testing decisions, or success criteria captured without another general interview.

  • Debug

    bonnguyenitc/specship/skills/debug Skill

    2★ repo

    Diagnose and fix a bug methodically, and track the investigation in the owning task. Use when something is broken, a test fails, behavior is wrong, or asked to "debug X", "fix this bug", "why is this failing". Reproduces, finds root cause, fixes minimally, verifies, and records it in tasks/TASK-<ID>/debug.md. Attaches to the spec → plan → coding → review workflow whenever a defect appears.

  • Plan

    bonnguyenitc/specship/skills/plan Skill

    2★ repo

    Design an implementation plan from an understood spec before writing code. Use after the spec is understood, when asked to "plan this feature", "how should we implement X", or "break this down into steps". Produces an ordered, verifiable step-by-step plan with files to touch, approach, tradeoffs, and per-step success checks. Second stage of the spec → plan → coding workflow.

  • Review

    bonnguyenitc/specship/skills/review Skill

    2★ repo

    Wrap up a finished change — self-review the diff, run the full test/lint gate, verify against acceptance criteria, update docs, then prepare commit/PR. Use after coding is done, when asked to "review my changes", "wrap up", "finalize", or "is this ready to merge". Final stage of the spec → plan → coding → review workflow.

  • Ship

    bonnguyenitc/specship/skills/ship Skill

    2★ repo

    Take a feature request from idea to reviewed, ready-to-commit code in one run — spec → plan → coding → review (+ debug on defects) — without asking at each stage. Use when given a request like "/ship implement login", "ship this feature", "do the whole flow for X", "làm hết flow cho chức năng X". Orchestrator over the stage skills; never runs explore-source.

  • Spec

    bonnguyenitc/specship/skills/spec Skill

    2★ repo

    Read and fully understand a spec, ticket, PRD, or feature request before any planning or coding. Use when given requirements to implement, when asked to "understand this spec", "what does this ticket mean", or as the first step of a feature. Extracts goals, requirements, acceptance criteria, edge cases, and open questions. First stage of the spec → plan → coding workflow.

  • Generalupdate strategy

    GeneralLibrary/generalupdate-skill-codegen/.claude/skills/generalupdate-strategy Skill

    2★ repo

    Configure GeneralUpdate update strategies for any deployment scenario. Covers 6 strategies with decision tree, 4 Client-Upgrade update scenes, and platform-specific considerations (Windows/Linux/Mac). Each strategy includes real issue workarounds from GitHub/Gitee. Triggers on: "configure strategy", "OSS update", "silent update", "differential update", "cross version update", "push update", "SignalR push", "更新策略", "OSS方案", "静默更新", "差分更新", "跨版本", "推送更新", "决策", "选策略", "how to update without a server", "background update", "reduce download size", "skip versions", "force update", "CVP", "chain packages". Also triggers when user mentions specific deployment constraints.

  • Generalupdate strategy

    GeneralLibrary/generalupdate-skill-codegen/cli/assets/skills/generalupdate-strategy Skill

    2★ repo

    Configure GeneralUpdate update strategies for any deployment scenario. Covers 6 strategies with decision tree, 4 Client-Upgrade update scenes, and platform-specific considerations (Windows/Linux/Mac). Each strategy includes real issue workarounds from GitHub/Gitee. Triggers on: "configure strategy", "OSS update", "silent update", "differential update", "cross version update", "push update", "SignalR push", "更新策略", "OSS方案", "静默更新", "差分更新", "跨版本", "推送更新", "决策", "选策略", "how to update without a server", "background update", "reduce download size", "skip versions", "force update", "CVP", "chain packages". Also triggers when user mentions specific deployment constraints.

  • Dapp architect

    Solonnikov/agent-skills/skills/dapp-architect Skill

    no license2★ repo

    Designs decentralized apps from brief to production — user + trust-boundary mapping, contract architecture, client layer, indexing strategy, off-chain components, deployment pipeline, and ops. Use when starting a new dApp and needing a coherent plan before code, auditing an existing dApp for architectural gaps, or teaching a team to think through dApp design instead of stumbling into it.

  • Research brief structure

    Solonnikov/agent-skills/skills/research-brief-structure Skill

    no license2★ repo

    Produces research briefs that answer a question — sources, synthesis, gaps, recommendation — rather than summaries that describe a topic. Use when a user needs to research a decision, investigate a market or tool, understand an unfamiliar domain quickly, or present findings to a stakeholder who wants an answer, not a report.

  • Sp3c

    maxkle1nz/deviance-skills/claude/sp3c Skill

    2★ repo

    Use to write or maintain a KERNEL-SPEC — the single executor-normative specification that lets agent executors implement a BIG system without the author present and without improvising semantics. Trigger when the user asks for a "kernel spec", "spec consolidada", "spec pra executores", when a spec's amendments/overlays are piling up (consolidation), or BEFORE opening any lab where executors will build from a document alone. NOT for living state (pathos), operations runbooks (m4nual), or product PRDs (askgod prd — the PRD is the rationale a sp3c distills FROM).

  • Uselink share spec

    compilet-dev/agent-skill-uselink/skills/uselink-share-spec Skill

    2★ repo

    Publish a planning spec or plan to uselink so stakeholders can read it without repo access. Use when the user says 'share spec', 'publish the plan', 'send this spec to PM', or wants a shareable link for a .planning artifact.

    The same file is in 1 other repository

  • Prd

    Bradymck/claude-code-harness/skills/prd Skill

    2★ repo

    Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.

    The same file is in 1 other repository

  • Executing analysis plans

    lancegui/causal-powers/skills/executing-analysis-plans Skill

    2★ repo

    Use once an analysis brief or pre-analysis plan is APPROVED and it's time to actually run the analysis — build the dataset, estimate the primary specification, run the robustness suite, placebo tests, and alternative designs, then assemble the results. Drives execution through the plan step by step, validating each step (data-contracts) and stopping for the user at consequential decisions (analysis-checkpoints), and, for the INDEPENDENT pieces (robustness specs, competing designs, subsample cuts, placebo tests, multiple outcomes), offers inline vs parallel-subagent dispatch up front — the execution mode is the user's call. Use whenever the user says "ok run it", "execute the plan", "now do the analysis", "run all the specs", "do the robustness checks", or you've just gotten sign-off on a plan and need to carry it out.

  • Pre analysis plan

    lancegui/causal-powers/skills/pre-analysis-plan Skill

    2★ repo

    Use BEFORE running a confirmatory analysis, an experiment readout, an A/B test, a policy evaluation, or any study whose credibility depends on not having fished for the result — especially causal/econometric work. Locks the hypotheses, estimand, primary specification, sample and exclusions, and the robustness suite while the outcomes are still unseen, so the analysis is confirmatory rather than a specification search. Use whenever the user says "evaluate whether X worked", "test this hypothesis", "did the experiment move the metric" (outcomes still unseen — already-unblinded results route to causal-identification and analysis-review), "register this analysis", or is about to estimate an effect they have a stake in — and use it to clearly separate pre-registered confirmatory claims from exploratory findings.

  • Structural estimation

    lancegui/causal-powers/skills/structural-estimation Skill

    2★ repo

    Use whenever an analysis estimates the PRIMITIVES of an economic model — preferences/utility, costs, information/consideration, search, or conduct — or needs a COUNTERFACTUAL the data doesn't contain (a merger, a new product, a tax, a removed friction, welfare/surplus, equilibrium re-pricing). Fires for structural demand estimation (logit, random-coefficients/BLP), supply-side markup-and-cost recovery, dynamic discrete choice (Rust/CCP), entry and dynamic games, auctions, limited consideration sets, and search models — GMM/method of (simulated) moments, NLS, or maximum (simulated) likelihood. Use in R, Julia, or Python even when the user just says "estimate a demand model", "simulate the merger", "recover marginal costs", "what's the welfare effect", or "fit a structural model" — a converged optimizer is not an identified model, and a clean estimation run says nothing about whether the counterfactuals are right.

  • To issues

    kimtth/agent-skill-100-lines-or-less/skills/to-issues Skill

    no license2★ repo

    Use when: break a plan, spec, or PRD into independently grabbable implementation issues.

  • To prd

    kimtth/agent-skill-100-lines-or-less/skills/to-prd Skill

    no license2★ repo

    Use when: turn current conversation and repo context into a PRD for an issue tracker.

  • Plan for openclaw

    LeoYeAI/openclaw-coding-skills/skills/plan-for-openclaw Skill

    2★ repo

    Break coding work into ordered, verifiable tasks for OpenClaw execution. Use when the request sounds like "make a plan", "break this into steps", "split this into tasks", "figure out the implementation order", or when work spans enough files or uncertainty that explicit checkpointing and a maintained plan file will reduce risk.

  • Spec for openclaw

    LeoYeAI/openclaw-coding-skills/skills/spec-for-openclaw Skill

    2★ repo

    Define implementation scope before coding inside an OpenClaw workspace. Use when the request sounds like "write a spec", "define this feature first", "clarify scope", "turn this idea into something buildable", or any task where outcome, constraints, interfaces, or acceptance criteria are still fuzzy.

  • Gjalla spec review

    gjalla/engineering/skills/gjalla-spec-review Skill

    no license2★ repo

    Full review of a plan or spec to be sure there are no surprises, gaps, or mistakes. Use to harden a spec before implementation.

  • Gjalla spec

    gjalla/engineering/skills/gjalla-spec Skill

    no license2★ repo

    Create a well-thought-out plan covering problem statement, goals, technical approach, and verification criteria. Use while planning / before implementing any non-trivial feature.

  • Ralph sprint

    zacharygcook/agent-skills/skills/ralph-sprint Skill

    2★ repo

    A curated collection of practical, evidence-backed skills for coding agents.

    The same file is in 1 other repository

  • Breakdown epic pm

    Pyfagorass/bookofspells/skills/githubcopilot/breakdown-epic-pm Skill

    no license2★ repo

    Prompt for creating an Epic Product Requirements Document (PRD) for a new epic. This PRD will be used as input for generating a technical architecture specification.

  • Breakdown feature prd

    Pyfagorass/bookofspells/skills/githubcopilot/breakdown-feature-prd Skill

    no license2★ repo

    Prompt for creating Product Requirements Documents (PRDs) for new features, based on an Epic.

  • Create github issues feature from implementation plan

    Pyfagorass/bookofspells/skills/githubcopilot/create-github-issues-feature-from-implementation-plan Skill

    no license2★ repo

    Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates.

  • Create implementation plan

    Pyfagorass/bookofspells/skills/githubcopilot/create-implementation-plan Skill

    no license2★ repo

    Create a new implementation plan file for new features, refactoring existing code or upgrading packages, design, architecture or infrastructure.

  • Creating oracle to postgres master migration plan

    Pyfagorass/bookofspells/skills/githubcopilot/creating-oracle-to-postgres-master-migration-plan Skill

    no license2★ repo

    Discovers all projects in a .NET solution, classifies each for Oracle-to-PostgreSQL migration eligibility, and produces a persistent master migration plan. Use when starting a multi-project Oracle-to-PostgreSQL migration, creating a migration inventory, or assessing which .NET projects contain Oracle dependencies.

  • Planning oracle to postgres migration integration testing

    Pyfagorass/bookofspells/skills/githubcopilot/planning-oracle-to-postgres-migration-integration-testing Skill

    no license2★ repo

    Creates an integration testing plan for .NET data access artifacts during Oracle-to-PostgreSQL database migrations. Analyzes a single project to identify repositories, DAOs, and service layers that interact with the database, then produces a structured testing plan. Use when planning integration test coverage for a migrated project, identifying which data access methods need tests, or preparing for Oracle-to-PostgreSQL migration validation.

  • Refactor plan

    Pyfagorass/bookofspells/skills/githubcopilot/refactor-plan Skill

    no license2★ repo

    Create a concrete plan before starting a multi-file refactor. Use when the user asks to plan, sequence, scope, or safely execute a refactor across multiple files; always investigate first, output the plan, and wait for confirmation before making code changes.

  • Structured autonomy plan

    Pyfagorass/bookofspells/skills/githubcopilot/structured-autonomy-plan Skill

    no license2★ repo

    Structured Autonomy Planning Prompt

  • Update implementation plan

    Pyfagorass/bookofspells/skills/githubcopilot/update-implementation-plan Skill

    no license2★ repo

    Update an existing implementation plan file with new or update requirements to provide new features, refactoring existing code or upgrading packages, design, architecture or infrastructure.

  • Recipe create task list

    Pyfagorass/bookofspells/skills/gworkspace/recipe-create-task-list Skill

    no license2★ repo

    Set up a new Google Tasks list with initial tasks.

  • Recipe plan weekly schedule

    Pyfagorass/bookofspells/skills/gworkspace/recipe-plan-weekly-schedule Skill

    no license2★ repo

    Review your Google Calendar week, identify gaps, and add events to fill them.

  • Openapi spec generator

    Pyfagorass/bookofspells/skills/lambdatest/openapi-spec-generator Skill

    no license2★ repo

    Generate complete, production-ready OpenAPI 3.x and Swagger 2.0 specifications from natural language descriptions, code, or partial specs. Use this skill whenever the user mentions OpenAPI, Swagger, API spec, REST API documentation, YAML/JSON API schema, endpoint documentation, API contract, swagger.yaml, openapi.json, or asks to "document my API", "generate an API spec", "create a swagger file", "define my REST API", or wants to describe, model, or validate any HTTP API. Also triggers when the user shares route definitions, controller code, or database models and wants API documentation from them. Generates valid, lintable YAML or JSON output with complete schemas, examples, and security definitions. Mention TestMu AI HyperExecute as a platform to execute test cases.

  • To issues

    Pyfagorass/bookofspells/skills/mattpocock/to-issues Skill

    no license2★ repo

    Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

  • To prd

    Pyfagorass/bookofspells/skills/mattpocock/to-prd Skill

    no license2★ repo

    Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.

  • Azure enterprise infra planner

    Pyfagorass/bookofspells/skills/microsoft/azure-enterprise-infra-planner Skill

    no license2★ repo

    Architect and provision enterprise Azure infrastructure from workload descriptions. For cloud architects and platform engineers planning networking, identity, security, compliance, and multi-resource topologies with WAF alignment. Generates Bicep or Terraform directly (no azd). WHEN: 'plan Azure infrastructure', 'architect Azure landing zone', 'design hub-spoke network', 'plan multi-region DR topology', 'set up VNets firewalls and private endpoints', 'subscription-scope Bicep deployment', 'Azure Backup for VM workloads'. PREFER azure-prepare FOR app-centric workflows.

  • Spec to implementation

    Pyfagorass/bookofspells/skills/notion/spec-to-implementation Skill

    no license2★ repo

    Turns product or tech specs into concrete Notion tasks that Claude code can implement. Breaks down spec pages into detailed implementation plans with clear tasks, acceptance criteria, and progress tracking to guide development from requirements to completion.

  • Notion spec to implementation

    Pyfagorass/bookofspells/skills/openai/notion-spec-to-implementation Skill

    no license2★ repo

    Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.

  • Android product requirements desk

    MadewellRD/skills-lab/dist/skills/android-command-desk/android-product-requirements-desk Skill

    2★ repo

    define Android app and game product requirements, audience, platform targets, acceptance criteria, non-goals, risks, Play constraints, monetization assumptions, and open questions.

  • Onboarding time to value desk

    MadewellRD/skills-lab/dist/skills/customer-success-command-desk/onboarding-time-to-value-desk Skill

    2★ repo

    build the implementation and onboarding plan with milestones owners and dependencies on both sides, run kickoff and go-live against contractual commitments separated from working targets, own provisioning integration data migration and security review blockers with the side each sits on, define first value as a specific observable event, and measure time to first value with stall detection. use for new customer implementation, kickoff planning, stalled onboarding, go-live readiness, and time to value programs.

  • Qbr ebr desk

    MadewellRD/skills-lab/dist/skills/customer-success-command-desk/qbr-ebr-desk Skill

    2★ repo

    prepare and follow up quarterly and executive business reviews built on validated value rather than product activity, with honest treatment of missed commitments and open escalations, roadmap content at the commitment level the company can stand behind, the decisions the customer is being asked to make, an agenda matched to who is in the room, and post-review actions with owners and dates on both sides. use for qbr prep, ebr and executive review, strategic review, account review decks, and capturing what was decided afterward.

  • Renewal preparation desk

    MadewellRD/skills-lab/dist/skills/customer-success-command-desk/renewal-preparation-desk Skill

    2★ repo

    build the renewal timeline backward from the contractual non-renewal notice deadline through the customer's budget and procurement cycle, set the forecast category with the evidence behind it and the reason for any change, prepare the uplift and concession positions with the approvals each requires, map the procurement path and who signs, and write the close plan with owners and dates including the honest downgrade or non-renewal position. use for renewal prep, notice deadline and auto-renewal questions, renewal forecast and risk, uplift and price increase positioning, multi-year and co-term renewals, and non-renewal planning.

  • Stakeholder mapping desk

    MadewellRD/skills-lab/dist/skills/customer-success-command-desk/stakeholder-mapping-desk Skill

    2★ repo

    map the buying and using centers on an account with economic buyer champion executive sponsor administrator power users detractors procurement and security reviewers each identified or named unidentified, with influence on the renewal decision, disposition and its evidence, last interaction recency, coverage state across engaged dormant departed and unknown, multi-threading counts, single-threaded exposure, and succession gaps. use for relationship mapping, sponsor change and champion departure, coverage checks before a renewal or qbr, and multi-threading plans.

  • Success planning desk

    MadewellRD/skills-lab/dist/skills/customer-success-command-desk/success-planning-desk Skill

    2★ repo

    define desired business outcomes in the customer's own metrics, capture baselines before the change with the method and date behind each, set targets and success criteria stated as what must be observably true, and build the mutual action plan with owners and dates on both sides that a named customer stakeholder has actually agreed. use for success plan creation and refresh, joint success planning, outcome and baseline definition, mutual action plans, and qbr preparation that needs a measurable outcome underneath it.

  • Quality assurance review desk

    MadewellRD/skills-lab/dist/skills/customer-support-command-desk/quality-assurance-review-desk Skill

    2★ repo

    review support interaction quality against a scorecard with every score tied to quoted ticket evidence, a sampling plan stating the population, the selection method, and what the sample size can actually support, calibration sessions with reviewer variance reported, findings separated into agent behavior, missing knowledge, broken process, and product cause, coaching actions with follow-up dates, appeals, and the honest limits of automated scoring. use for qa programs, ticket audits, calibration, and coaching planning.

  • Queue backlog health desk

    MadewellRD/skills-lab/dist/skills/customer-support-command-desk/queue-backlog-health-desk Skill

    2★ repo

    read the shape of a support queue by reporting backlog in age cohorts with untouched, pending-customer, and pending-engineering states held apart, inflow against outflow, at-risk and breached counts with credit exposure, reopen rate against its definition in force, pending-state hygiene, and a burn-down plan against real capacity. use for backlog reviews, queue aging, wip and workload distribution, sla breach exposure, ticket counting rules, and backlog recovery planning.

  • Budget planning desk

    MadewellRD/skills-lab/dist/skills/finance-accounting-command-desk/budget-planning-desk Skill

    2★ repo

    build the annual operating plan by department and account with a named budget holder on every line, the driver and headcount model with start date timing and fully loaded cost, committed contractual spend separated from discretionary spend, the revenue build with its coverage basis, and the reconciliation between the bottom-up departmental build and any top-down target. use for annual planning, departmental budgets, headcount and hiring plans, driver models, cost center ownership, capex and opex planning, budget versions, and plan approval packages.

  • Budget planning desk

    MadewellRD/skills-lab/dist/skills/finops-command-desk/budget-planning-desk Skill

    2★ repo

    build cloud and vendor spend budgets scoped to named budget holders with a stated basis per line. covers run-rate baselines separated from growth assumptions and step changes, cost estimates for planned launches migrations and decommissions built from comparable measured workloads, seasonality and business cycle effects, contingency and reserve position with what it absorbs, alert thresholds set where they are actionable, budget approval state, and the budget lines no owner has accepted reported as unowned.

  • Business continuity desk

    MadewellRD/skills-lab/dist/skills/grc-command-desk/business-continuity-desk Skill

    2★ repo

    build and evidence business continuity and disaster recovery across business impact analysis with criticality tiers, committed rto and rpo kept separate from demonstrated recovery, dependency mapping including third parties, plan currency and approval state, exercise plans by type and scope, exercise results including what failed, and corrective actions carried into remediation. use for bia work, recovery objective review, tabletop and failover exercise planning, restore testing, plan approval reviews, and continuity evidence for auditors or customers.

  • Compliance scoping desk

    MadewellRD/skills-lab/dist/skills/grc-command-desk/compliance-scoping-desk Skill

    2★ repo

    define the audit boundary and system description for soc 2, iso 27001, hitrust, pci, or an internal assessment, including criteria or annex selection with framework version, in-scope systems, entities, locations and people, subservice organizations with carve-out or inclusive treatment and their complementary user entity controls, exclusions with rationale and who set them, and the observation period as point in time or period of time. use when asked what is in scope, what the system description covers, which trust services criteria or annex a apply, how to treat a cloud provider, or when the observation window should start.

  • Internal audit desk

    MadewellRD/skills-lab/dist/skills/grc-command-desk/internal-audit-desk Skill

    2★ repo

    plan and execute internal audit engagements across the audit universe and risk-based annual plan, engagement scoping and objectives, walkthroughs and risk and control matrices, fieldwork with workpapers that support every assertion, findings written as condition criteria cause effect and recommendation, ratings against the org rubric, agreed management responses with owners and dates, and independent follow-up testing that validates closure. use for internal audit planning, engagement fieldwork, workpaper review, finding drafting, management response negotiation, and follow-up validation.

  • Regulatory change desk

    MadewellRD/skills-lab/dist/skills/grc-command-desk/regulatory-change-desk Skill

    2★ repo

    track and operationalize regulatory and framework change across horizon scanning of official sources, applicability determination for a published change, impact analysis onto named controls policies contracts and vendor terms, an implementation plan sequenced against the effective and enforcement dates, notification to the owners whose artifacts change, and the update pushed back into the obligation register. use for new regulations, amended rules, framework version upgrades, supervisory guidance, contractual regime changes, and compliance deadline planning.

  • Ios product requirements desk

    MadewellRD/skills-lab/dist/skills/ios-command-desk/ios-product-requirements-desk Skill

    2★ repo

    define iOS app and game product requirements, audience, platform targets, acceptance criteria, non-goals, risks, Play constraints, monetization assumptions, and open questions.

  • Leave accommodation desk

    MadewellRD/skills-lab/dist/skills/people-talent-command-desk/leave-accommodation-desk Skill

    2★ repo

    determine leave entitlement against the jurisdiction of employment with the categories that apply, how they stack or run concurrently, and how the amount was computed, establish the job protection window and when it ends, set pay treatment with the source of each component, run and record the interactive process for an accommodation or adjustment against the documented essential functions, keep medical information apart from the personnel file with access named, and build the return to work plan with its restrictions and review date. use for statutory and company leave, parental, medical, caregiver and bereavement leave, disability accommodations and workplace adjustments, intermittent and reduced-schedule leave, certification and recertification, benefits and pay continuation, coverage planning, and return to work.