solo-pipeline
SolidUse when "run pipeline", "automate research to PRD", "full pipeline", "research and validate", "scaffold to build", "loop until done", "chain skills", or need multi-skill automation. Do NOT use for single skills (use the skill directly).
Install
Quality Score: 87/100
Skill Content
Details
- Author
- fortunto2
- Repository
- fortunto2/solo-factory
- Created
- 7 months ago
- Last Updated
- today
- Language
- Shell
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
full-pipeline
Orchestrates the user's full end-to-end workflow in order — gstack office-hours, autoplan, autoresearch-plan, superpowers writing-plans and subagent-driven-development, autoresearch-impl, code-review, and qa — invoking each skill in sequence and handing its output forward as the next step's input. At two fixed checkpoints (after the plan is locked, and after implementation lands) it judges whether the change touches database schema and if so invokes supabase:supabase-postgres-best-practices before continuing. Use whenever the user wants to "run the whole pipeline", "go from idea to shipped", "do the full flow", or asks Claude Code to chain their office-hours → autoplan → superpowers → qa workflow automatically instead of invoking each skill by hand.
pipeline
Use when the user asks to take a substantial feature from an initial idea through implementation in one mostly autonomous run.
task-pipeline
Use when work changes the repository — feature, fix, refactor, migration, integration, rewrite, adoption or hardening; фича, фикс, рефактор, миграция, интеграция, доработать, починить, внедрить, перевести — or when the output is a finding that lands in it: audit/аудит, bug hunt/проверь ошибки, production check/проверь прод, PR review/ревью PR — or on 'run this through the pipeline' / 'прогони по конвейеру', 'full cycle, the full cycle' / 'полный цикл', /task-pipeline. Runs a substantial task through an intake grill, docs study, brainstorm, spec, plan, build, tests, deploy, post-deploy, docs/wiki sync and acceptance with explicit gates. 'checkup' / 'чекап' reports unconfirmed releases; 'setup' audits existing docs. Not for: answering a question, explaining code, a typo or a one-line edit, a mechanical rename, reconnaissance that lands nothing — say 'без пайплайна' / 'quick' to opt out.