init-work-branch

Create a feature branch, wire submodules, and generate a design document from setup.yaml.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/NagasakaH/dev-process --skill init-work-branch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: init-work-branch
Source: https://github.com/NagasakaH/dev-process/tree/main/.claude/skills/development/init-work-branch
Command: npx skills add https://github.com/NagasakaH/dev-process --skill init-work-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates initial development setup by creating a feature branch, wiring submodules, and generating a design document from a setup.yaml.

Core Features & Use Cases

  • Feature branch creation: generate a ticket-based feature branch and switch to it.
  • Submodule management: attach related and target repositories as submodules for synchronized work.
  • Design document generation: produce a setup-driven design document from the YAML description.
  • Use Case: when kicking off a new task, run this skill to prepare the repository and docs in one step.

Quick Start

Execute init-work-branch with a prepared setup.yaml to create the feature branch, add submodules, and generate the design document.

Frequently Asked Questions about init-work-branch

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

FAQPage Schema
How do I automate feature branch creation and development environment setup from a YAML file?

Automating feature branch creation and environment setup requires a valid setup.yaml to define the configuration. The process validates the YAML fields, generates a ticket-based feature branch, wires related repositories as submodules, and outputs a design document.

How do I bootstrap a new development task with submodule wiring and design documentation?

Bootstrapping a development task with submodule wiring and design documentation involves reading a setup.yaml to attach target repositories as submodules. This synchronizes related repositories and generates a setup-driven design document in one step.

What is the best way to generate a design document from a setup.yaml for a new feature branch?

Generating a design document from a setup.yaml is best handled by validating the configuration fields first, then creating the feature branch and attaching submodules. The YAML description directly drives the produced design documentation.

Does this branch setup automation work without any external dependencies?

This branch setup automation operates without external dependencies, relying solely on the provided setup.yaml. It validates the required YAML fields internally before creating the feature branch and adding target repositories as submodules.

Can I use this setup to attach multiple target repositories as submodules for synchronized work?

You can use this setup to attach multiple target repositories as submodules for synchronized work. The setup.yaml configuration specifies the related and target repositories to wire directly into the newly created feature branch.

What happens if the setup.yaml fields are invalid when bootstrapping the feature branch?

When the setup.yaml fields are invalid, the feature branch bootstrapping process halts after the validation step. The setup requires all specified fields to be valid before it proceeds to create the branch, add submodules, and generate the design document.