Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From pr-review
Orchestrates the complete feature development pipeline from brainstorming through PR review — interactive spec/design then automated alignment, planning, implementation, and PR review.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pr-review:feature-pipelineThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Orchestrate the complete feature development pipeline from brainstorming through PR review. Steps 1-2 are interactive (user present for Q&A), steps 3-9 are fully automated (user walks away).
Orchestrate the complete feature development pipeline from brainstorming through PR review. Steps 1-2 are interactive (user present for Q&A), steps 3-9 are fully automated (user walks away).
/feature-pipeline {description of the product feature}
/feature-pipeline {description} --slug user-auth
/feature-pipeline {description} --spec-only
/feature-pipeline {description} --max-iterations 300 --priority normal
Read and follow the orchestrator instructions exactly:
Orchestrator file: agents/feature-pipeline-orchestrator.md (relative to this plugin's root)
The orchestrator will:
IMPORTANT: Read the orchestrator file using the path ${CLAUDE_PLUGIN_ROOT}/agents/feature-pipeline-orchestrator.md and follow it exactly.
npx claudepluginhub dbinky/dbinky-skill-set --plugin spec-to-designGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.