RemiMyrset

new-package

Scaffold a new workspace package under packages/ or apps/ with the house shape (catalog deps, base tsconfig, source-direct exports, vitest) and add it to the AGENTS.md monorepo map. Use when the user says "new package", "add a package", "create an app", or "scaffold a package". Also use unprompted when code you are adding belongs in no existing workspace package.

Code & Development Listed

sync-template

Pull the roots template's shared mechanics into this repository. Bootstrap the script if missing, run the sync, review the staged diff, apply the printed follow-ups, run the done gate, and propose the commit. Use when the user says "sync from template", "pull template updates", "update the mechanics", or "sync roots". Never commits or pushes on its own.

first-run

Initialize a repository just created from the template by running the README "First run" checklist. Prove the done gate, name the project, fill the owner placeholders, apply the GitHub settings with gh, delete the section, and propose the commit. Use when the user says "first run", "initialize from template", "set up this repo", or "initialize this repo". Also use unprompted when README.md still contains a "## First run" section and this checkout is not the template itself. Never pushes.

release

Prepare a release with changelogen. Pre-flight checks, changelog preview, and the exact command for the human to run. Use only when the user explicitly asks, with "release", "cut a release", "ship a version", "tag a release". Never unprompted. The release itself (pnpm release) pushes commits and tags to the default branch, so the push guard denies it to agents; the human runs it.

new-spec

Create a new specification (capability or entity spec) in the right area with correct format and regenerated index. Use when the user says "new spec", "spec this endpoint/entity/behavior", or new externally observable behavior is being designed. Also use unprompted when a change adds or alters externally observable behavior (a route, command, flag, exit code, or invariant) that no existing spec covers.

Code & Development Listed

verify-docs

Run the full docs gate locally and fix what it finds. Generated-section drift, format violations, broken links, portability breaks. Use after any edit under docs/, README.md, or AGENTS.md, before committing docs changes, or when the user says 'check the docs' or 'verify docs'.

pr

Push the current feature branch and open a pull request. Verify first, check the branch name against the protected list, build the PR body from the repository template with the checklist ticked only where true, link the issue. Use when the user says "open a PR", "create a pull request", "push and PR", or "ship this branch". Never merges and never touches a protected branch.