dev-workflow

Coordinate multi-phase development workflows across grill, brainstorming, planning, execution, and wrap-up.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/ebal5/agent-skills --skill dev-workflow-ebal5
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-workflow
Source: https://github.com/ebal5/agent-skills/tree/main/skills/dev-workflow
Command: npx skills add https://github.com/ebal5/agent-skills --skill dev-workflow-ebal5

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

開発作業のフローをオー케ストレーションで制御し、worktree内外の作業環境に対応しつつ、実処理を既存スキルへ委譲して全体の進行を安定させます。

Core Features & Use Cases

  • フロー順序の制御と作業のオーケストレーション
  • worktreeの安全制約の適用と状態検証
  • 既存スキルとの連携による委譲

Quick Start

Initiate a full development workflow to coordinate grill, brainstorming, planning, execution, and wrap-up while ensuring worktree safety.

Frequently Asked Questions about dev-workflow

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

FAQPage Schema
How do I orchestrate a multi-phase development workflow with git worktrees?

You can orchestrate multi-phase development workflows by coordinating brainstorming, planning, execution, and wrap-up phases. This skill manages the flow sequence and delegates actual processing to existing skills while applying git worktree safety constraints and state validation.

What is the best way to ensure safe gating and consistent handoffs across development phases?

Safe gating and consistent handoffs are ensured by orchestrating phase transitions and validating state before proceeding. The skill coordinates handovers between existing skills and enforces git worktree safety constraints throughout the development workflow.

Can I use this development workflow orchestration with my existing skills and commit plugins?

Yes, this skill requires integration with the superpowers suite, commit plugins, and handover patterns. It delegates execution to existing skills rather than replacing them, ensuring your current tools work within the orchestrated workflow.

When do I need to apply worktree safety constraints during development orchestration?

Worktree safety constraints are applied at start-of-work decisions and right after EnterWorktree when the first task begins. These constraints ensure safe gating and consistent handoffs across all phases of the orchestrated development workflow.

What are the limitations of orchestrating development flow with worktree-based environments?

This skill relies on existing skills for actual execution and requires integration with the superpowers suite and commit plugins. It coordinates flow but does not perform processing itself, meaning its effectiveness depends on the quality of integrated skills and handover patterns.