dev-process

Plan, design, and execute multi-file features through a gate-reviewed pipeline.

1|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/kyletabor/claude_plugins --skill dev-process
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-process
Source: https://github.com/kyletabor/claude_plugins/tree/main/dev-process/skills/dev-process
Command: npx skills add https://github.com/kyletabor/claude_plugins --skill dev-process

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a rigorous, gate-reviewed workflow for multi-file feature implementations, enabling architecture-first planning, structured exploration, and formal validation to reduce rework.

Core Features & Use Cases

  • Spec-driven architecture definition before coding
  • Parallel exploration and design with dedicated roles
  • Structured implementation pipeline from spec to tests
  • Gate reviews and mandatory verification for quality and traceability

Quick Start

Initiate a dev-process cycle for any multi-file feature request and follow the six-phase workflow.

Frequently Asked Questions about dev-process

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

FAQPage Schema
What is a gate-reviewed development workflow for multi-file features?▼

A gate-reviewed development workflow enforces architecture-first planning, parallel exploration, and formal validation across multi-file changes. It requires passing design specs and mandatory verification checkpoints before moving through implementation phases to ensure traceable outcomes.

How do I plan and execute complex cross-file changes using a structured development pipeline?▼

To execute cross-file changes, initiate a six-phase development pipeline starting with an architecture spec. Proceed through parallel exploration, defined implementation legs, and mandatory verification to ensure every complex PR is tested and traceable.

When should I use a spec-driven architecture approach for my software project?▼

Use a spec-driven architecture approach for architecture-heavy tasks, cross-file changes, and complex PRs. It reduces rework by enforcing concrete architecture definitions and formal validation before and during coding.

Does a structured development process work for simple single-file updates?▼

A structured development process is designed for architecture-heavy tasks and complex cross-file changes. It is not intended for simple single-file updates, as the six-phase gate review pipeline would add unnecessary overhead to minor modifications.

What's the best way to ensure traceable and tested outcomes for complex PRs?▼

The best way to ensure traceable outcomes for complex PRs is applying a gate-reviewed pipeline. This mandates a concrete architecture spec, dedicated exploration, structured implementation legs, and formal verification before completion.

Why does my multi-file feature implementation require a gate review before coding?▼

Multi-file feature implementation requires a gate review to establish a concrete architecture spec upfront. This structured exploration and design phase reduces rework by validating the design before any implementation legs begin.