control-plane

Publish static HTML pages and asset folders to the Paperclip-approved S3 and CloudFront website host. Use when asked to deploy, publish, host, or share a persistent Paperclip page, wireframe viewer, prototype, report, or other static site without using here.now.

Interact with the Paperclip control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, set up or manage routines (recurring scheduled tasks), or call any Paperclip API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for Paperclip coordination.

Generate the stable Paperclip release changelog at releases/vYYYY.MDD.P.md by reading commits, changesets, and merged PR context since the last stable tag.

The Paperclip way of converting a plan into executable tasks. Use whenever you are asked to plan, scope, or break down work inside a Paperclip company. Industry-agnostic guidance on how to translate a plan into assigned issues with the right specialty, dependencies, and parallelization so Paperclip's executor can pick up the work — it does not prescribe a plan format. Pair with the `paperclip` skill, which covers the mechanics of writing the plan document and reassigning the issue.

Manage a Paperclip company as a board member via chat. Covers onboarding (company creation, CEO setup, hiring plans), agent management, approvals, task monitoring, cost oversight, and work product review. Use this skill whenever the user wants to interact with their Paperclip control plane.

Run, verify, reseed, and repair a Paperclip isolated dev workspace service. Use when asked to start or fix a Paperclip project/worktree service and prove that it is managed by the Paperclip runtime, has the full bootstrapped cloned database, is healthy, accepts normal dev credentials, exposes populated app data, and is visible as running from both the control-plane and the served workspace app.

Create and develop external Paperclip plugins with the CLI-first workflow. Use when scaffolding a new plugin, working on a local plugin against a running Paperclip instance, or updating plugin authoring docs. Covers `paperclipai plugin init`, the local install loop via `paperclipai plugin install <path>`, worker/UI rebuild and reload semantics, and the required success checklist.

Run a single Terminal-Bench problem through Paperclip in a bounded, human-in-the-loop improvement cycle until the smoke passes, the board rejects the next fix, the iteration budget is exhausted, or a real blocker is named. Each iteration runs a bounded smoke against an isolated Paperclip App worktree, captures artifacts, diagnoses the exact stop point with `/diagnose-why-work-stopped`, requests board confirmation before any product fix, then reruns against the same worktree. Use whenever an issue asks to "run Terminal-Bench in a loop", "drive Terminal-Bench until it passes", "loop fix-git through Paperclip", or otherwise points at a Terminal-Bench task and asks for bounded iteration with diagnosis.

Developer/maintainer skill for adding a new issue-thread interaction kind to the Paperclip codebase end-to-end: shared contract, server service/routes, UI card, fixtures/Storybook, CLI/MCP/plugin SDK helpers, agent guidance, and tests. Use when a Paperclip contributor is asked to introduce a new interaction family (something analogous to `request_confirmation`, `request_checkbox_confirmation`, `ask_user_questions`, or `suggest_tasks`) or to extend the issue-thread interaction system with a new card type. Do NOT install this on production Paperclip agents — it is for repo work, not agent runtime behavior.

Write the Discord release announcement for a stable Paperclip release. Companion to `release-changelog` — that skill produces the file at `releases/vYYYY.MDD.P.md`; this one turns that file into a single copy-pasteable Discord post in dotta's voice and attaches it as the `discord_announcement` document on the release issue.