Triage the AI.List feedback inbox — dedup, verify claims against shipped source, tag, assign, and move every triaged task out of "Open" so status is the state machine. Use when new ai-plugin feedback has accumulated on ClickUp, or on request ("triage the board", "any new issues?").
Draft and queue a BlueStep-branded release-update email across three products (the bluestep-tools plugin, the b6p CLI, and the gateway MCP) since the last-sent watermarks. Maintainer-only, repo-local, manual — reads watermarks over the gateway MCP, collects changes (CHANGELOG / gh / ClickUp), renders the email-safe…
Start a new spec-driven feature. Creates requirements.md, then design.md, then tasks.md with explicit user approval between each phase. Use when the user wants to plan a non-trivial change to this repo (the bspecs scaffolder).
Execute one task from a feature spec. By default delegates implementation to the spec-task-implementer subagent (isolated context); pass --inline to implement in the main session. Updates the task checkbox when done. Use after /spec-create has produced an approved tasks.md.
Compare a local component's state against what lives on the BlueStep platform, listing files that differ. Use when the user wants to know if they (or someone else) changed something on the platform side, or before a push to be sure nothing unexpected will be overwritten.
Pull a B6P component from the BlueStep platform into the local workspace using its DAV URL, and scaffold draft/README.md if missing. Use when the user wants to bring a component down for the first time or re-sync after platform edits.
Set up BlueStep (B6P) tooling in a project — new or existing — and activate the always-on platform rules. Non-destructive and idempotent — writes any missing per-project files (AGENTS.md with the rules, a one-line CLAUDE.md bridge, README.md, package.json, .gitignore, .prettierrc), skips files that already exist…
On-demand BlueStep (B6P) platform reference — BsJs/RelateScript patterns, conventions, and gotchas. Consult when implementing, reviewing, or documenting a BlueStep component. This file is the manifest of single-topic instruction files (reference/, conventions/, gotchas/) with a one-line "load when" trigger for each…
Scaffold an off-platform Vite/Preact SPA merge-report project — check Node 20, run create-vite (preact-ts), set base "./", wire the deploy-lib config block + repository field, then print the [PLATFORM] report-creation and GitHub-repo steps for the human to execute. Use when starting a new Vite/Preact single-page-app…
Send a bspecs tooling-change request (a rule, skill, subagent, hook, reference file, spec/module template, or a shipped AGENTS.md rule) upstream to the team's tracker. Use when you or the user notice something about the bluestep-tools plugin itself that should change — the plugin is a read-only shared install, so a…
Draft a standardized implementation comment for a ClickUp task after a fix or feature is shipped. Handles both org-propagated (component-based) and direct (code-only) changes.
★not rated 2 6d agoA39 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: