rpw-building

Run a compact activity-research workflow for high-volume sources (HN/GitHub style)

Full lifecycle development orchestrator with adaptive execution modes

Lightweight implementation-first workflow with explicit safety and verification gates

Validate your development environment — checks all required tools and offers install help. Start here.

Run a consistent release flow for `rpw-agent-marketplace` with built-in guardrails.

Analyze plugin structure — skill coverage, test coverage, component organization, and improvement suggestions

Analyze project health — open/blocked/stale issues, dependencies, velocity, and recommendations

Enable the single required plugin stack for this marketplace with no profiles and no customization flow.

Re-run session orientation — shows current git state, beads status, project files, and suggests the next best activity.

You are a Build Worker. You implement exactly one task bead using strict TDD.

You are a Debug Lead. You diagnose bugs systematically and recommend targeted fixes.

You are a Minion. You execute simple, well-defined tasks quickly and accurately.

You are a strict privacy and security reviewer. Your job is to be a HARD DENY GATE — zero tolerance for any content that could expose private information in public repositories.

You are a project management specialist for Claude Code plugin development.

You are a Research Lead. You plan research, dispatch Research Workers for parallel source exploration, and synthesize findings.

You are a Research Worker. You investigate one specific source or subtopic and return a structured summary.

You are a PR Security Guard. You review diffs for security issues with zero tolerance for secrets or vulnerabilities.

You are a Simplifier. You reduce complexity, remove dead code, and improve readability in recently changed files.

Auto-dispatch subagents for research, debugging, and minion tasks outside /build sessions. Teaches the agent to recognize request patterns and spawn the right subagent type.

Configure Cursor with the /build command from rpw-building. Use when setting up Cursor to use the build workflow, or when the user asks to add/configure the build command in Cursor.

Build and deploy Databricks Apps using the bash-over-REST starter template. Use when scaffolding, configuring, deploying, or iterating on Databricks Apps with Lakebase connectivity.

Reusable APP_ENV env-file pattern for local development. Commit template.env, keep dev/test/prod env files local-only, and load the selected file at app startup.

Use when MCP servers fail due to missing .env, authentication errors, or env var issues. Provides tips for MCP environment setup when .env may be missing or incomplete.

Use when setting up Python projects, installing packages, running Python scripts, or managing dependencies - enforces UV package manager workflow with automatic virtual environment handling, replacing pip and manual venv management

Use when creating or modifying MCP servers in this repo. Enforces secret-free configs, uv/uvx entrypoints, and .env.example patterns.

Use when building Raycast extensions, especially with Python/uv dependencies, encountering venv corruption, authentication issues, or path race conditions - provides critical patterns from production fixes including .gitignore, lazy initialization, and validation

Naming conventions, dispatch patterns, and guardrails for spawning Build Workers and other subagents

Use when setting up versioning for a project, comparing versions between components, or implementing version checks. Enforces git-hash-based versioning standard across all projects.

3 hooks across 2 events