executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
bamboohr-sdk-patternsSelect and wrap BambooHR's official Python or PHP SDK, or a narrow direct HTTP adapter, with tenant isolation and typed errors. Use when implementing a reusable client or replacing an unverified community package. Trigger with "BambooHR SDK", "BambooHR client", or "BambooHR integration patterns".
Independent GitHub snapshot · Automated classification · Original documentation governs
Build a small application-owned adapter around a verified BambooHR transport. Keep BambooHR models and error details at the adapter boundary so upstream SDK regeneration or endpoint migration does not ripple through business logic.
BambooHR/bhr-api-python and BambooHR/bhr-api-php are official repositories.bamboohr/api 2.0.1 is published on Packagist.bamboohr-sdk 1.0.0, but public PyPI did not
expose that distribution on 2026-09-11 and the repository had no tag or
release. Treat it as source-visible, not registry-proven.Expose constructors for OAuth and API-key identities, not raw headers. Bind each client to one validated tenant subdomain. If OAuth refresh is enabled, persist rotated tokens through the caller-owned callback; the Python SDK does not store them across restarts.
getCompanyInformation,
listEmployees, and queryDatasetV2; do not expose an arbitrary URL method
to untrusted callers.Use Read, Glob, and Grep to establish the project's language and package state. Use Write/Edit only for the approved adapter and tests. This skill does not authorize package installation, remote registry mutation, or live tenant calls.
Require approval before adding a dependency, using an unreleased commit, making a tenant request, broadening OAuth scopes, or enabling debug logging around HR data. Never silently fall back from OAuth to an API key.
Return the chosen transport and exact version/commit, registry verification, adapter operations, auth and tenant boundary, error taxonomy, test results, and remaining publication or live-test approvals.
Read official evidence before choosing a transport.