Stats
Actions
Tags
From micro-skill-pipeline
Gated micro-skill pipeline system. Auto-triggers when building, generating, or creating any multi-step output (documents, code, presentations, reports). Enforces a Scope-Plan-Build-Check-Deliver pipeline where each step has a pass/fail gate. Use this whenever the output quality matters and the task has more than one component.
How this skill is triggered — by the user, by Claude, or both
Slash command
/micro-skill-pipeline:micro-pipelineThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When this skill triggers, execute the following gated pipeline.
When this skill triggers, execute the following gated pipeline. One step at a time. Do NOT skip ahead.
references/01-scope.md. Extract constraints from the request.references/02-plan.md. Design the approach. Map components.references/03-build.md. Execute with micro-checks per component.references/04-check.md. Answer every gate question YES or NO. Any NO = fix before proceeding.references/05-deliver.md. Finalize and present output.Look for a failure-log.md in the current project root or skill directory.
If it exists, read it before starting. Every listed pattern is a mandatory check constraint.
failure-log.md.npx claudepluginhub stevesolun/micro-skills --plugin micro-skill-pipelineOrchestrates development pipeline by classifying tasks, coordinating skill execution order, adapting flow to context, and ensuring no critical steps are skipped.
Launches automated multi-skill pipelines chaining /research→/validate for idea to PRD, or /scaffold→/setup→/plan→/build for full projects from stack. Uses state files and stop hooks for sequencing.
Composes Claude Code skills into automated pipelines for multi-step workflows like feature development, bug fixes, content launches, and project bootstraps. Supports auto-detection, dynamic step selection, progress tracking, and CLI management.