dd-feature-development-workflow

Orchestrates a ten-step design-first feature development workflow with TDD, CI validation, and git worktrees.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/marcocpt/trae_skills --skill dd-feature-development-workflow-marcocpt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dd-feature-development-workflow
Source: https://github.com/marcocpt/trae_skills/tree/main/dd-feature-development-workflow
Command: npx skills add https://github.com/marcocpt/trae_skills --skill dd-feature-development-workflow-marcocpt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It enforces a disciplined, design-spec-first process for building new features, preventing teams from writing code before requirements, design specs, and phased plans are confirmed, and ensuring every change is verified by CI before merging. ## Core Features & Use Cases - Ten-Step Gated Workflow: Strictly ordered stages from requirement confirmation, worktree creation, design spec, plan writing, TDD implementation, code sync, documentation check, lint/push, to merge cleanup, with hard gates blocking skipped steps. - Three-Subagent Parallel Reviews: Design specs, plans, and code are each reviewed by three parallel subagents covering coverage/scope, consistency/correctness, and verifiability/UI observability, with automatic fix-and-recheck loops. - State Persistence and Recovery: A JSON state file tracks current step, phase, commits, and merge status so interrupted sessions can resume without restarting from scratch. - Use Case: When adding a new UI-heavy feature to an iOS or web app, use this workflow to produce a design spec, visual prototype, test case matrix, phased TDD plans, and CI-verified commits before merging into develop. ## Quick Start Ask the assistant to start the feature development workflow for your new feature and answer the requirement questions it poses.

Frequently Asked Questions about dd-feature-development-workflow

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

FAQPage Schema
How do I enforce a design-spec-first workflow for new features?

Use a gated multi-step workflow that requires requirement confirmation, a written design spec, and phased plans before any production code changes. This workflow blocks coding until step 4 and uses hard gates to prevent skipping steps.

How to run TDD with XCUITest in a CI pipeline?

Write failing XCUITest cases locally but defer their execution to CI after committing and pushing, since UI tests depend on GUI sessions and accessibility permissions. Run only XCTest unit tests locally for fast red-green feedback.

When should I not use this feature development workflow?

Skip it for bug fixes, simple text edits, pure documentation changes, and one-off small changes. It is designed for design-driven work like new features, large refactors, and API migrations that justify the full ten-step process.

Can I resume an interrupted feature development session?

Yes, the workflow persists progress in a feature-development-state.json file inside the git directory, recording current step, phase, and commits. On recovery it inspects the branch and commits to infer progress instead of restarting from step zero.

Why does the workflow forbid git rebase when syncing upstream?

It enforces a merge-only policy using git merge --no-ff or --ff-only to preserve merge history and avoid rewriting shared commits. Conflicts are resolved on the feature branch, never directly on the develop branch.