dev

Evaluate Git branch workflow state and route to dev-plan or dev-step.

1|2|Updated Jul 5, 2024
One-click install
npx skills add https://github.com/uuta/dotfiles --skill dev-uuta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev
Source: https://github.com/uuta/dotfiles/tree/main/skills/dev
Command: npx skills add https://github.com/uuta/dotfiles --skill dev-uuta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill orchestrates a TDD-based development workflow by evaluating the current workflow state and routing to the appropriate skill (dev-plan or dev-step) to maintain momentum and clarity.

Core Features & Use Cases

  • Workflow state evaluation: checks the current Git branch and reads docs/{branch_name}/dev-workflow.yaml to determine plan and execute status.
  • Smart routing: guides users to the next step, whether to create a plan (dev-plan) or start implementation steps (dev-step) based on status.
  • Progress summary: presents a concise status and recommended next action to keep development on track.

Quick Start

Activate the dev skill to begin automated routing for your feature branch and receive guided prompts for planning or stepping through tasks.

Frequently Asked Questions about dev

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

FAQPage Schema
How do I automate TDD workflow routing for Git feature branches?

Automate TDD workflow routing by evaluating the current Git branch and reading docs/{branch_name}/dev-workflow.yaml to route to plan creation or step execution. This maintains development momentum by guiding teams to the exact next action required.

What is a dev-workflow.yaml schema used for in TDD development?

A dev-workflow.yaml schema tracks plan and execute status for TDD development. Stored in docs/{branch_name}/, it allows workflow orchestration tools to evaluate current progress and determine whether to route users to planning or implementation steps.

How do I start TDD-driven development from a Git feature branch?

Start TDD-driven development by activating the orchestration skill on your feature branch. It checks your workflow state and prompts you to either create a Markdown-based plan artifact or begin executing the next implementation step.

Does TDD workflow orchestration require Markdown plan artifacts?

Yes, TDD workflow orchestration requires Markdown-based plan artifacts to function correctly. These documents define the development steps and are evaluated alongside the dev-workflow.yaml file to route progress accurately.

What's the best way to track progress across TDD planning and execution steps?

Track progress by reading the dev-workflow.yaml file on your current Git branch. The orchestration skill summarizes this state and presents a concise recommended next action to keep development on track.