dev

Orchestrate end-to-end feature workflows from exploration to PR creation.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Srajangpt1/dataeye --skill dev-srajangpt1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev
Source: https://github.com/Srajangpt1/dataeye/tree/main/packages/browseros-agent/.claude/skills/dev
Command: npx skills add https://github.com/Srajangpt1/dataeye --skill dev-srajangpt1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the full feature development lifecycle inside a repository so developers avoid manual handoffs across exploration, design, implementation, review, and PR creation. It reduces context switching, ensures artifacts are preserved, and enforces a repeatable pipeline for shipping features.

Core Features & Use Cases

  • Sequential Orchestration: Chains sub-skills for exploration, design choice, PRD drafting, implementation, review, fixes, and PR creation.
  • Artifact Persistence & Handoff: Writes work-in-progress and final artifacts to .llm/<feature_name>/ for traceability and downstream steps.
  • Interactive Pauses: Pauses for user input at decision points (design selection, PR approval) and resumes the pipeline automatically after responses.
  • Use Case: Use when adding a new feature to the browser extension or agent stack to generate a PRD, implement changes, run reviews, and open a Pull Request with minimal manual orchestration.

Quick Start

Invoke /dev with a concise feature description to start the orchestrated pipeline that explores the codebase, drafts a PRD, implements changes, runs reviews, and opens a PR.

Frequently Asked Questions about dev

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

FAQPage Schema
How do I automate end-to-end feature development from PRD generation to PR creation?

You can automate feature development by orchestrating sequential sub-skills for PRD generation, implementation, code review, and Pull Request creation. This pipeline chains these phases together, reducing manual context switching and handoffs when adding new features to your repository.

What is the best way to manage feature exploration and design selection inside a monorepo?

Managing feature exploration inside a monorepo is handled by an orchestrated pipeline that explores the codebase and pauses for interactive design selection. It drafts a PRD based on your input, then automatically resumes the workflow to proceed with implementation.

How does artifact persistence work during automated code review and implementation?

Artifact persistence saves work-in-progress and final outputs to a `.llm/<feature_name>/` directory during code review and implementation. This ensures traceability and provides downstream pipeline steps with seamless access to previously generated documents.

Can I use automated workflow orchestration for browser extension and agent stack projects?

Yes, automated workflow orchestration is explicitly applicable to browser extension and agent stack projects. It handles feature exploration, PRD generation, implementation, and PR creation tailored for these specific repository environments.

Do I need to manually approve Pull Requests when using automated feature development pipelines?

You must provide input at decision points, as the pipeline uses interactive pauses for steps like design selection and PR approval. It pauses for your response and automatically resumes the feature development workflow once you provide it.