Development Workflow - 開發工作流程

Guide TDD-driven feature workflows with layered tests and incremental commits.

11|2|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/recca0120/code-quest --skill development-workflow-recca0120
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Development Workflow - 開發工作流程
Source: https://github.com/recca0120/code-quest/tree/main/.claude/skills/dev-workflow
Command: npx skills add https://github.com/recca0120/code-quest --skill development-workflow-recca0120

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams reduce wasted effort and uncertainty by providing a clear, repeatable development workflow that prioritizes planning, testing, and small iterative commits.

Core Features & Use Cases

  • TDD + Feature-First + Incremental cycle: guides you through Feature Planning → E2E/Integration/Unit tests → Minimal Implementation → Refactor → Review & Commit.
  • User-story-driven execution: defines user stories with explicit acceptance criteria so work stays aligned with expected outcomes.
  • Test layering strategy: recommends writing Feature tests first (RED), then Integration tests, then Unit tests for deterministic logic coverage.
  • Safe refactoring discipline: enforces “refactor without changing expectations” to keep tests as the contract.
  • Practical examples and checks: includes scenario patterns like adding functionality, reproducing a bug with a failing test, then fixing and committing in small steps.

Quick Start

Ask the AI to create a new feature plan and acceptance criteria for my change, then outline the exact E2E, integration, and unit test sequence and the minimal implementation steps to turn RED into GREEN.

Frequently Asked Questions about Development Workflow - 開發工作流程

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

FAQPage Schema
How do I implement TDD with feature planning and incremental delivery?

Test layering strategy requires writing E2E tests first for feature validation, then integration tests for module interactions, and unit tests for deterministic logic to ensure comprehensive coverage from broad to narrow scopes.

What is the best way to structure git commits during refactoring?

Git commits during refactoring should be small and frequent, keeping test expectations unchanged to maintain the contract, ensuring continuous integration while safely improving code structure without altering functionality.

How does the RED GREEN REFACTOR discipline apply to bug fixing?

RED GREEN REFACTOR for bug fixing involves reproducing the bug with a failing test, writing minimal implementation to turn it green, then refactoring safely while keeping test expectations unchanged as the contract.

Do I need acceptance criteria before writing E2E and integration tests?

Acceptance criteria must be defined first to drive user-story-driven execution, ensuring E2E and integration tests align with expected outcomes before writing minimal implementation paths to turn tests green.