dev-flow

Enforce task size gates and mandatory skill routing for code sessions.

10|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/cookys/autopilot --skill dev-flow-cookys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-flow
Source: https://github.com/cookys/autopilot/tree/main/skills/dev-flow
Command: npx skills add https://github.com/cookys/autopilot --skill dev-flow-cookys

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Start here before writing code — sizes task (S/L/H/Fix), sets up branch and session rules. It provides a disciplined lifecycle for feature work, bug fixes, and refactors by enforcing task sizing, session management, and mandatory skill routing before any changes are made.

Core Features & Use Cases

  • Establishes task size gates (S, L, Fix) to decide whether to proceed with direct commits or require planning.
  • Sets up branch/session rules and enables phase-based execution across code surfaces.
  • Coordinates with skill routing to ensure all affected modules are prepared before implementation.

Quick Start

Initiate this skill at the outset of a coding task to size the work, establish branch and session rules, and prep routing for subsequent skills.

Frequently Asked Questions about dev-flow

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

FAQPage Schema
How do I size coding tasks before starting a development session?

Task sizing categorizes work into S, L, H, or Fix levels to determine if direct commits are allowed or if planning and mandatory skill routing are required. This establishes size-based gates to enforce disciplined lifecycle management before any code changes are made.

What is mandatory skill routing in software development sessions?

Mandatory skill routing ensures all affected modules are prepared before implementation by coordinating branch rules and session start checks. It enforces L-1.6 routing requirements to guarantee phase-based execution across code surfaces is properly governed throughout the lifecycle.

How do I set up branch and session rules for a feature or bug fix?

Setting up branch and session rules involves initiating governance checks at the outset of a coding task to define lifecycle boundaries for feature work, bug fixes, and refactors. This coordinates branch rules and session start/end protocols before implementation begins.

When do I need task sizing gates for code refactoring?

Task sizing gates are needed before starting any feature work, bug fix, or refactoring session to decide whether to proceed with direct commits or require planning. They enforce size determination and mandatory routing to maintain disciplined development lifecycle governance.

Can I use session governance for planning sessions across multiple modules?

Yes, session governance applies to planning sessions across multiple modules by enforcing task sizing, setting up branch rules, and enabling phase-based execution. It ensures all affected modules are prepared and coordinates mandatory skill routing before changes are made.

What is the best way to close out a development session and finish a coding task?

The best way to close out a development session is through finish-flow orchestration, which coordinates lifecycle checks and session end protocols. This ensures all size-based gates and mandatory routing requirements are satisfied before the coding task is fully completed.