integral-productivity-engineering

Start a new Integral-Productivity repo against the org standard. Routes by work-type (mcp-server / typescript-sdk / claude-plugin / omnifocus-plugin) to the right template and scaffolding skill, then verifies the new repo classifies under devops-excellence's tier model.

Scaffold and maintain MCP servers at Integral Productivity. Use when building or updating an IP MCP server -- covers IP-standard project structure, Vercel deployment, dual-transport pattern (stdio + Streamable HTTP), auth conventions, and tool/service module organization. Invokes anthropic-skills:mcp-builder for base MCP guidance then layers IP conventions on top. Renamed from `ip-mcp-builder` when moved out of the skills monorepo into the integral-productivity-engineering plugin (the `ip-` prefix is redundant inside an IP-only plugin; `bootstrap-` aligns with the org vocabulary established by `pnpm bootstrap-repo` and the sibling `bootstrap-private-sdk`).

Scaffold a TypeScript SDK published to GitHub Packages and consumed by one or more in-org projects. Use this skill whenever someone is: creating a new private SDK for an Integral-Productivity service (REST/GraphQL/gRPC wrapper), extracting a shared client from a project that has grown a second consumer, or setting up GitHub Packages publication for an existing TypeScript library. Captures the non-obvious gotchas — scope/org naming, cross-platform lockfiles, SAML SSO on PATs, stacked-PR pitfalls — that cost hours of debugging on the glassfrog-sdk-ts bootstrap. IMPORTANT: invoke this skill BEFORE running `npm init` or copy-pasting another SDK's package.json — the order of the scaffold steps matters, and most of the friction is preventable upfront.

Router for cold-starting a new Integral-Productivity repo against the org's standard. Use when: the user mentions building a new IP repo (phrases like "new MCP server", "new SDK", "new IP repo", "new claude plugin", "new omnifocus plugin", "scaffold a new <work-type>", "create a new repo for X"); OR the current working directory is an Integral-Productivity repo whose `.github/workflows/` does not call reusable workflows from `Integral-Productivity/devops-excellence` and whose root has no CLAUDE.md (the empty-IP-repo signal). Walks the tier/work-type decision tree, recommends the right `template-*` repo and `type-<workType>` topic per ADR-025 and ADR-027, delegates the application scaffold to the matching sibling skill (bootstrap-mcp-server, bootstrap-private-sdk), and verifies the new repo classifies via `classifyRepo()` post-creation. Never duplicates application-scaffold knowledge — always delegates.