Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From alp-river
Runs a multi-step pipeline that detects bug vs feature framing, sizes the task, then stops at natural seams for diagnosis or planning approval.
npx claudepluginhub alp82/alp-river --plugin alp-riverHow this command is triggered — by the user, by Claude, or both
Slash command
/alp-river:go Describe what you want doneThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Go Task: $ARGUMENTS Start the pipeline at Step 0 per WORKFLOW.md `## Pipeline`. The pipeline figures out the rest: - Step 0 Level 1 detects bug-framing vs outcome-framing from your text and restates accordingly. On affirmation, that detection sets the internal `TYPE_BIAS` (bug → `diagnose`; otherwise → `build`). - Classifier sizes the task to S/M/L/XL/XXL. - Stops fire at natural seams - after diagnosis (on `diagnose`) and after the approved plan (on L/XL). Each is a picker: Continue or Stop. End with the literal line `<!-- pipeline-complete -->` at the final stop or summary.
/planAnalyzes a task description, classifies its type (feature, bugfix, etc.), and generates a minimum-viable pipeline plan with ordered steps, dependencies, and done criteria. For multi-layer features, produces vertical slice tables with worker assignments.
/devClassifies a task description into a development type and executes the matching paradigm workflow, reading phase instructions sequentially and enforcing quality gates at boundaries.
/flowOrchestrates the full development cycle from idea to pull request — feature definition, contracts, planning, implementation, review, validation, and PR creation. Also supports a bug fix pipeline via --fix.
/start-taskStarts a new development task by assessing complexity, running pre-task checks, and guiding the user through an appropriate workflow.
/ingestGuided multi-phase workflow: classify, research, scope, then execute with human confirmation at each step. Loads task-specific skills based on type and domain.
/route-taskClassifies task from GitHub issue, Google Doc, URL, or local file using haiku agent, then launches suitable workflow (feature-dev or subagent-driven-dev). Supports --new-session flag.
Share bugs, ideas, or general feedback.
Task: $ARGUMENTS
Start the pipeline at Step 0 per WORKFLOW.md ## Pipeline. The pipeline figures out the rest:
TYPE_BIAS (bug → diagnose; otherwise → build).diagnose) and after the approved plan (on L/XL). Each is a picker: Continue or Stop.End with the literal line <!-- pipeline-complete --> at the final stop or summary.