dev-pipeline

Automate prototype creation from ideas through PRs and harden issues.

2|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/TheFJK/UberDev --skill dev-pipeline-thefjk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-pipeline
Source: https://github.com/TheFJK/UberDev/tree/main/plugins/uberdev/skills/dev-pipeline
Command: npx skills add https://github.com/TheFJK/UberDev --skill dev-pipeline-thefjk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, github, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of quickly developing minimal working prototypes by automating the pipeline process, from parsing ideas to creating PRs and harden issues.

Core Features & Use Cases

  • Prototype Development: Automates the creation of minimal working prototypes.
  • Parallel Subagents: Utilizes parallel subagents for efficient development.
  • Git Integration: Manages git operations for commit and integration.
  • Light Review: Includes a light review phase to ensure basic functionality.
  • PR and Issue Creation: Automatically creates PRs and harden issues for further development.
  • Use Case: Ideal for quickly testing a new feature or function, allowing developers to focus on core functionality without worrying about the full development process.

Quick Start

To start a new prototype, use the command: /uberdev:dev <idea description>

Frequently Asked Questions about dev-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate prototype development from idea to GitHub PR?

Automating prototype development involves parsing an idea, decomposing it into chunks, building via parallel subagents, and integrating the code. The pipeline commits the changes, runs a light review, opens a pull request, and auto-files a harden issue.

What is the best way to quickly build a minimal working prototype in git?

Building a minimal working prototype quickly requires a fast-lane pipeline that runs a scope gate to limit features. It then uses parallel subagents to construct the code, integrates the results, and commits them directly to your git repository.

Do I need GitHub integration to use a parallel subagent development pipeline?

Yes, GitHub integration is required. The pipeline relies on GitHub to automatically open pull requests after the integration and light review phases, and to file a harden issue for tracking future development and stabilization.

Can I use automated scope gating for rapid prototype feature testing?

Yes, a scope gate is used to strictly limit the prototype to minimal working functionality. This ensures rapid feature testing by preventing scope creep while parallel subagents build the defined chunks and integrate them automatically.

What happens after a parallel subagent code integration and light review?

After parallel subagents integrate the code and a light review verifies basic functionality, the pipeline commits the changes to git. It then automatically opens a pull request on GitHub and files a harden issue for future stabilization.

When should I avoid using an automated development pipeline for prototyping?

You should avoid this automated pipeline for production-ready development, as it is designed specifically for minimal prototypes. It runs only a light review and explicitly files a harden issue, indicating further manual hardening is required later.