dev-workflow

Manage a structured software delivery workflow from requirement intake to engineering review.

6|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/hubvue/skills --skill dev-workflow-hubvue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-workflow
Source: https://github.com/hubvue/skills/tree/main/productivity/dev-workflow
Command: npx skills add https://github.com/hubvue/skills --skill dev-workflow-hubvue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the execution of a traditional, structured software development lifecycle, ensuring all phases from requirement intake to engineering review are followed with durable artifacts.

Core Features & Use Cases

  • End-to-End Workflow Management: Guides a task through intake, research, planning, implementation, testing, bug fixing, and review.
  • Artifact-Driven Process: Emphasizes creating and updating documentation at each stage (e.g., task.md, plan.md, test-report.md).
  • Use Case: When a new feature request comes in, this Skill can manage the entire process of defining requirements, designing the solution, breaking it into tasks, implementing, testing, and finally getting it reviewed by engineering.

Quick Start

Initiate the development workflow by providing the initial product requirement.

Frequently Asked Questions about dev-workflow

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

FAQPage Schema
How do I manage a structured software delivery workflow from requirement intake to engineering review?

A structured software delivery workflow is managed by guiding tasks through intake, research, planning, implementation, testing, and review. This process enforces artifact-first principles and traditional role alignment to ensure durable project outputs.

What is an artifact-first development process and how does it help software delivery?

An artifact-first development process emphasizes creating and updating durable documentation at each lifecycle stage. It generates files like task.md, plan.md, and test-report.md to maintain structured project records and ensure incremental updates.

How do I break down product requirements into implementation tasks for a development team?

Product requirements are broken down into implementation tasks through a structured software delivery workflow encompassing technical planning and task breakdown. This process aligns engineering roles and produces detailed artifacts for each development phase.

Does this software delivery workflow handle bug fixing loops and testing reports?

Yes, the software delivery workflow handles bug fixing loops and testing reports by managing the full lifecycle. It enforces artifact creation during testing, ensuring test-report.md is generated and updated until the engineering review phase.

When do I need a formal engineering review process for software delivery?

A formal engineering review process is needed when following a structured software delivery workflow to ensure durable project outputs. It marks the final phase after implementation and bug fixing, validating all generated artifacts and technical plans.