Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By crouton-labs
Orchestrates a structured feature development workflow from requirements gathering through design, planning, parallel implementation, code review, validation, and testing, with session persistence across Claude sessions.
Start new feature - define spec and gather context
Create technical design from requirements
After /rpi/plan - execute with parallel subagents
After /rpi/design - create implementation plan from requirements and design
Explore and discuss the problem space (optional first step)
Technical design subagent. Use in the /rpi:rpi pipeline workflow.
Planning subagent for feature development. Use in the /rpi:rpi pipeline workflow.
Requirements gathering subagent. Use in the /rpi:rpi pipeline workflow.
Read-only review subagent. Spawns its own subagents to investigate code quality, correctness, and structural issues. Validates findings are real, then returns a structured fix list to the orchestrator. Dispatch multiple in parallel with different concern assignments.
Test planning subagent. Reads spec and implementation plan, decides if tests are needed, and writes a meaningful test plan. Spawned by the planning-lead.
Validate technical designs against requirements for coverage, feasibility, and architectural soundness. Use after creating a design.
Validate implementation plans against requirements and design. Use after creating a plan to ensure full coverage and no ambiguities.
Validate requirements documents for EARS compliance, completeness, and consistency. Use after creating requirements.
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
No model invocation
No model invocation
Executes directly as bash, bypassing the AI model
Executes directly as bash, bypassing the AI model
Runs pre-commands
Contains inline bash commands via ! syntax
Runs pre-commands
Contains inline bash commands via ! syntax
Share bugs, ideas, or general feedback.
Bridge Claude Code to the crtr CLI — slash commands that orient the agent to installed crtr skills/plugins and load skill bodies on demand. Requires the `crtr` binary on PATH (install via `npm i -g @crouton-kit/crouter`).
Create configurable hooks from markdown rule files
X (Twitter) posting, engagement, and growth tools — skills, commands, and northlight integration
CLI tool for running Claude Code SDK sessions with configurable modes
Developer utilities (notifications, command creation)
npx claudepluginhub crouton-labs/crouton-kit --plugin rpiDevelopment workflow automation including feature development, code quality, and PR management
Spec-driven development for big features. When features get too big, plan mode gets too vague—leading to hallucinations during implementation. ShipSpec replaces vague plans with structured PRDs, technical designs, and ordered tasks that keep Claude grounded.
Full feature development workflow from spec to completion
Requirements-driven development workflow with quality gates for practical feature implementation
End-to-end development workflow: design → draft-plan → orchestrate → review → pr-create → pr-review → pr-merge
Harness-native ECC operator layer - 60 agents, 232 skills, 75 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses