dev1-start

Explore repository structure and create a feature workspace for design handoff.

50|37|Updated Oct 8, 2025
One-click install
npx skills add https://github.com/browseros-ai/BrowserOS-agent --skill dev1-start-browseros-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev1-start
Source: https://github.com/browseros-ai/BrowserOS-agent/tree/main/.claude/skills/dev1-start
Command: npx skills add https://github.com/browseros-ai/BrowserOS-agent --skill dev1-start-browseros-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps product teams and engineers begin a new feature by performing a lightweight, high-level exploration of the repository to understand the stack, project layout, and immediate design direction.

Core Features & Use Cases

  • High-level survey of the codebase to identify stack, dependencies, and module layout.
  • Create a dedicated feature workspace at .llm/<feature_name>/ and write a tmp_context.md with the request, timestamp, and current directory.
  • Produce a concise handoff to the design phase, preparing for the next step in the /dev workflow.

Quick Start

Create the feature workspace and begin the initial exploration of the repository to prepare for design.

Frequently Asked Questions about dev1-start

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

FAQPage Schema
How do I start feature development with a codebase exploration?

To start feature development, you perform a high-level codebase exploration to identify the stack, dependencies, and module layout, then create a dedicated workspace and temporary exploration record to prepare for the design phase.

What is the best way to scope a new feature in a monorepo?

Scoping a new feature in a monorepo involves reading project docs, examining languages and dependencies, mapping top-level packages, and outlining initial design directions to create a concise exploration record.

How do I create a feature workspace for initial project exploration?

Creating a feature workspace involves generating a dedicated directory at .llm/<feature_name>/ and writing a tmp_context.md file containing the feature request, timestamp, and current directory for structured handoff.

Can I use this exploration workflow for any repository stack?

Yes, this exploration workflow applies to new feature initiatives across monorepos regardless of the specific stack, reading project docs and examining languages to map the project layout and prepare for design.

How does the handoff trigger work after codebase exploration?

The handoff trigger works by producing a concise exploration record and preparing a path for the next step in the development workflow, specifically triggering /dev2-design <feature_name> to transition into the design phase.