skills.rest
hardness1020
hardness1020COMMUNITY
Explore all skills by this author →
GitHub

manage-work

Register work items, create feat/<slug> branches, and track progress via docs/workflow-state.yaml.

8|Updated Sep 22, 2025
Search Tags:#git#workflow#dashboard#branch#manage#docs-first
One-click install
npx skills add https://github.com/hardness1020/VibeFlow --skill manage-work-hardness1020
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: manage-work
Source: https://github.com/hardness1020/VibeFlow/tree/main/.claude/skills/manage-work
Command: npx skills add https://github.com/hardness1020/VibeFlow --skill manage-work-hardness1020

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires yaml, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Register and manage multiple work items through the VibeFlow docs-first workflow, enabling consistent branch creation, stage tracking, and timely closures.

Core Features & Use Cases

  • Register work items with a unique ID, assign a track, and create a feat/<slug> branch.
  • Track progress with a central manifest at docs/workflow-state.yaml and a real-time dashboard of in-flight work items.
  • Advance items through stages, route to the appropriate skill, and close items when DONE.
  • Ensure governance by updating docs and branch state consistently across the team.

Quick Start

Register a new work item with /manage-work register "<description>" <ID> <track> to begin tracking it through the pipeline.

Frequently Asked Questions about manage-work

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

FAQPage Schema
How do I manage git workflow branches and track work items end-to-end?▼

You can manage git workflow branches by registering work items to automatically create feat/<slug> feature branches and tracking their progress centrally. This coordinates items end-to-end through a docs-first workflow state manifest.

What is a docs-first workflow and how does it track project stages?▼

A docs-first workflow tracks project stages by maintaining state in a central docs/workflow-state.yaml manifest. It routes items through pipeline stages, providing real-time dashboard visibility and next-step guidance for in-flight work.

How do I create a feature branch from a new work item description?▼

To create a feature branch, register the work item using a description, unique ID, and track. This automatically generates a feat/<slug> branch and logs the item into the workflow-state.yaml manifest for tracking.

Can I use this workflow management approach for different project scales?▼

Yes, this workflow management approach applies across Micro, Small, Medium, and Large project tracks. It scales branch creation, stage advancement, and closure governance consistently regardless of the track size.

Do I need YAML to run a docs-first work item dashboard?▼

Yes, YAML is required as a dependency because the work item dashboard and manifest rely on docs/workflow-state.yaml. This file serves as the central source for tracking progress and stage routing across the team.

Related Skills

Explore More Product & Management Skills→
jinglemansweepjinglemansweep

jp-plan

Automates Git-based .plans phase directory creation with sequential numbering and metadata files.

Community
Advanced
kivo360kivo360
1

Orchestrating SPEC-First TDD Development

Orchestrate SPEC-first TDD workflows with SPEC, TEST, CODE, and DOC phases.

Community
Advanced
ComputerConnectionComputerConnection

z-combinator

Route startup founders through a 10-stage pipeline with gate evaluations.

Community
Advanced
jankneumannjankneumann
4

worktree

Manage per-change Git worktrees with a central registry and openspec naming.

Community
Advanced