Verified:GitHub

hatch3r-board-init

Initialize GitHub Projects V2, Azure Boards, or GitLab Issue Boards with status and label structures.

26|4|Updated Feb 27, 2026

Search Tags:#project board #label taxonomy #hatch3r #Azure Boards #status workflow #GitHub Projects V2 #GitLab Issue Boards

One-click install

npx skills add https://github.com/hatch3r/hatch3r --skill hatch3r-board-init

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: hatch3r-board-init
Source: https://github.com/hatch3r/hatch3r/tree/main/skills/hatch3r-board-init
Command: npx skills add https://github.com/hatch3r/hatch3r --skill hatch3r-board-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the manual setup work required to create consistent project boards by automatically provisioning the correct status structure, label taxonomy, and board overview workflow for your chosen platform.

Core Features & Use Cases

Platform-aware board initialization: Configures GitHub Projects V2, Azure Boards, or GitLab Issue Boards using the platform detected from hatch.json.
Deterministic workflow-ready structure: Creates or connects a project, configures the status field/states, and establishes label or tag taxonomies that downstream hatch3r board commands rely on.
Team-oriented execution orchestration: Supports a planning phase with a single consolidated confirmation and a guarded execution phase with credential verification and resume behavior for GitHub.

Quick Start

Use the hatch3r-board-init skill to initialize board management for your repository by running npx hatch3r init.

Frequently Asked Questions about hatch3r-board-init

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

FAQPage Schema

How do I initialize a project board with a consistent status workflow and label taxonomy?▼

You can initialize a project board with a deterministic status workflow and label taxonomy by running npx hatch3r init, which detects your target platform from hatch.json and provisions the required structure for GitHub Projects V2, Azure Boards, or GitLab Issue Boards.

Can I connect an existing Azure Boards or GitHub Projects V2 board instead of creating a new one?▼

Yes, you can connect an existing Azure Boards or GitHub Projects V2 board instead of creating a new one. The skill supports both creating a new board and connecting to an existing one with optional migration behavior to align it with the hatch3r status structure.

What is the plan-confirm-execute flow for setting up a GitLab Issue Board?▼

The plan-confirm-execute flow is a two-phase process where the skill proposes a single consolidated plan for configuring your GitLab Issue Board, then performs guarded execution with credential verification only after you explicitly confirm the plan.

Does hatch3r-board-init require a hatch.json file for platform detection?▼

Yes, hatch3r-board-init requires a mandatory hatch.json file for platform detection. The skill reads this file to determine whether to target GitHub Projects V2, Azure Boards, or GitLab Issue Boards before performing identity verification and applying mutations.

Why does my project board initialization require credential and identity verification?▼

Credential and identity verification is required before executing board mutations to ensure only authorized users can apply the hatch3r status structure, label taxonomy, and board overview changes to your GitHub Projects V2, Azure Boards, or GitLab Issue Boards.