skills.rest
nikbrunner
nikbrunnerCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

dev-flow

Automate the end-to-end development lifecycle with five phase documents.

Updated Jun 17, 2025
Search Tags:#workflow#planning#development#documentation#routing#execution#phases
One-click install
npx skills add https://github.com/nikbrunner/dots --skill dev-flow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-flow
Source: https://github.com/nikbrunner/dots/tree/main/common/.agents/skills/dev-flow
Command: npx skills add https://github.com/nikbrunner/dots --skill dev-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The development lifecycle is often fragmented; this skill provides a structured five-phase workflow (assess, plan, implement, review, close) with linked phase documents and direct phase routing to keep teams aligned and on schedule.

Core Features & Use Cases

  • Phase-guided workflow: a clear path through assessment, planning, implementation, review, and closure for projects of any size.
  • Self-contained knowledge: phase documents (1-assess.md to 5-close.md) and a central SKILL.md provide guidance and repeatable processes.
  • Quick initiation: start from the overview or jump directly to any phase using /dev:flow <phase> to accelerate onboarding and consistent practices.

Quick Start

Invoke dev-flow with no argument to view the overview, or specify a phase such as /dev:flow assess to begin.

Frequently Asked Questions about dev-flow

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

FAQPage Schema
How do I structure an end-to-end development workflow with clear phases?▼

A five-phase development workflow guides teams through assessment, planning, implementation, review, and closure. It uses linked phase documents and direct phase routing to maintain alignment and scheduling across software projects.

What's the best way to document the software development lifecycle for repeatable processes?▼

Documenting the software development lifecycle is best handled through self-contained phase documents and a central SKILL.md file. This setup provides repeatable guidance from project assessment through closure for any software project size.

How do I jump directly to a specific phase in a development workflow?▼

You can jump directly to a specific development workflow phase by using the /dev:flow command followed by the phase name, such as /dev:flow assess. This allows quick initiation and consistent practices without starting from the overview.

Can I use a phased development workflow for software projects of any size?▼

Yes, a phased development workflow applies to software projects of any size. It guides teams through assessment, planning, implementation, review, and closure, scaling the process to fit both small and large project scopes.

Why does a fragmented development lifecycle cause scheduling and alignment issues?▼

A fragmented development lifecycle lacks structured phase routing and documentation, causing misalignment and schedule slippage. Providing a clear five-phase path with linked documents keeps teams coordinated from assessment to closure.

Related Skills

Explore More Software Engineering Skills→
gwttgwtt
17

setup-engine

Configure Godot engine projects with versions, languages, and technical preferences.

Community
Advanced
ngocsangyemngocsangyem
14

meow:shipping

Guide software shipping with ship pipelines, canary deployments, and rollback protocols.

Community
Intermediate
tutran27tutran27

vc-feasibility-test

Validates unverified libraries or APIs via empirical probes and verdicts.

Community
Advanced
ArchitectVS7ArchitectVS7

github-project-management

Orchestrate GitHub project management workflows with AI swarms for issue tracking and sprint planning.

Community
Advanced