skills.rest
doolin
doolinCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

software-development-workflow

Define an end-to-end software development workflow with assigned roles.

Updated Mar 29, 2026
Search Tags:#workflow#collaboration#ownership#branching#code-review#ci
One-click install
npx skills add https://github.com/doolin/dave-skills --skill software-development-workflow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: software-development-workflow
Source: https://github.com/doolin/dave-skills/tree/main/skills/software-development-workflow
Command: npx skills add https://github.com/doolin/dave-skills --skill software-development-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarifies roles and responsibilities across the software development lifecycle to reduce handoff friction and improve throughput by formalizing who owns requirements, design, coding, testing, review, and merging.

Core Features & Use Cases

  • Role-based ownership: Clearly assigns tasks to Developer, Claude, or Together at each step.
  • End-to-end lifecycle: Guides activities from understanding requirements through CI-green PR.
  • Process consistency: Enables repeatable, auditable software delivery with minimal ambiguity.

Quick Start

Set up the end-to-end workflow in your project by defining ownership for each step and wiring in CI checks.

Frequently Asked Questions about software-development-workflow

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

FAQPage Schema
How do I define a software development workflow with clear ownership for branching and code review?▼

You can define an end-to-end software development workflow that assigns specific ownership roles to the Developer, Claude, and Together for each step from requirements to CI-green PR merge.

What is role-based ownership in a collaborative coding workflow?▼

Role-based ownership clarifies responsibilities across the software development lifecycle by formally assigning tasks like coding, testing, and reviewing to specific roles, reducing handoff friction.

How do I set up a CI-ready code review process for my project?▼

Set up a CI-ready code review process by wiring CI checks into your branching workflow and assigning merge ownership to ensure only reviewed, passing code integrates.

Can I use this workflow to guide the full development lifecycle from requirements to merge?▼

Yes, the workflow guides the complete development lifecycle from understanding requirements through design, coding, testing, review, and merging to achieve a CI-green PR.

Do I need a SKILL.md file to implement this collaborative software workflow?▼

Yes, you need a SKILL.md file with frontmatter specifying the skill name and description, and it optionally supports scripts, references, and assets to execute the workflow.

When should I formalize roles and responsibilities in my code review process?▼

Formalize roles when handoff friction slows throughput and ambiguity exists over who owns requirements, coding, testing, or merging in your software delivery cycle.

Related Skills

Explore More Software Engineering Skills→
apifyapify
239

Template for a customizable Skill Unit.

Official
Basic
lygavlygav

coding-monitoring

Interpret SDLC states, PR status, and CI health from coding-monitor output.

Community
Intermediate
barrydobsonbarrydobson

devops

Advocate DevOps principles including CI/CD, IaC, automated testing, monitoring, and security scanning for delivery pipelines.

Community
Intermediate
ZeliperZeliper

orchestration-workflow

Manage multi-agent orchestration workflows across Plan and Execute modes.

Community
Advanced