bluestep
01Plugin Claude Code
BlueStep platform tooling for Claude Code — spec-driven development skills, b6p CLI integration, subagents, hooks, and an on-demand platform reference.
Plugin Claude Code
BlueStep platform tooling for Claude Code — spec-driven development skills, b6p CLI integration, subagents, hooks, and an on-demand platform reference.
Agent Claude Code
Implements exactly ONE already-approved task from a feature spec in this repo (the bspecs scaffolder), in an isolated context. Invoked by /spec-execute to keep scoped source reads out of the main session. Reads the task's spec files and only the files the task references, makes the change, verifies, and returns a…
Settings file Claude Code
Agent settings declaring 1 allowed tools.
Skill Claude CodeCodex
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?").
Skill Claude CodeCodex
Short workflow for small tasks and bug fixes that don't warrant a full 3-phase spec. Use for clearly-scoped changes and bugs in this repo.
Skill Claude CodeCodex
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…
Skill Claude CodeCodex
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).
Skill Claude CodeCodex
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.
Skill Claude CodeCodex
Show progress of all feature specs in .claude/specs/. Use when the user wants a summary of what's in flight.
Instructions file
Claude Code instructions for Bluestep-Systems/bspecs, covering bspecs — bluestep tooling for spec-driven development, architecture, key behaviors, editing the plugin and running / testing.
Plugin Claude Code
Spec-driven BlueStep (B6P) development tooling for AI coding agents (Claude Code, Cursor, Codex): b6p platform CLI skills, the spec- workflow, BlueStep subagents, guardrail hooks, and an on-demand platform reference.
MCP server Claude CodeCodexCursor
MCP server "bluestep-gateway", hosted remotely at gateway.bluestep.net, as configured in Bluestep-Systems/bspecs.
Agent
Reviews BlueStep component code and returns a structured report grouped Critical / Warnings / Suggestions — try/catch coverage, Optional .get() safety, server/client boundary, console. left in, mergeTag/field usage, component-library vs hand-rolled UI, and a11y. Invoke after a coding task is done (typically suggested…
Agent
Documents a BlueStep component by filling in its draft/README.md from the code — Overview, Type, Fields used, Behavior, External dependencies, and known gotchas. Invoke after a coding task is done (typically suggested at a /spec-execute STOP), before code review. Edits the README ONLY — never adds inline comments…
Agent
Implements exactly ONE already-approved task from a feature spec, in an isolated context. Invoked by /spec-execute to keep heavy declaration/source reads out of the main session. Reads the task's spec files and the project's declaration files, writes the code, compiles each tsconfig folder, and returns a structured…
Hook
Runs before the agent uses a tool for Edit, Write and Bash tool calls, executing block-generated-files.sh, block-inline-frontend.sh and block-tsc.sh (3 commands). From Bluestep-Systems/bspecs.
Skill Claude CodeCodex
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.
Skill Claude CodeCodex
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.
Skill Claude CodeCodex
Push local changes for a component back to the BlueStep platform. Use when the user is ready to deploy local edits.
Skill Claude CodeCodex
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…
Skill Claude CodeCodex
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…
Skill Claude CodeCodex
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…
Skill Claude CodeCodex
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…
Skill Claude CodeCodex
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.