Development Workflow Skill

End-to-end feature development workflows are orchestrated using a six-phase process covering requirements, YAML configuration, pseudocode review, test-driven development, implementation, and Bash execution. This enforces TDD and design-review discipline across diverse software projects.

Enforcing test-driven development and design reviews during sprints is achieved by applying a structured six-phase methodology. It separates pseudocode planning and TDD implementation from final code implementation, ensuring traceability and discipline throughout the software lifecycle.

YAML configuration drives the software feature development lifecycle by serving as config-driven input for repeatable executions. It initiates a six-phase workflow that coordinates requirements, testing, implementation, and single-entry Bash execution.

Yes, you can trigger a complete development workflow from requirements to execution with a single command. Preparing a user_prompt.md initiates the single-entry Bash execution pattern, running the entire six-phase feature development process automatically.

The six-phase development workflow requires no external dependencies or components. It operates as a standalone process to coordinate requirements, YAML configuration, pseudocode review, TDD, code implementation, and Bash execution for software teams.

Writing pseudocode before test-driven development implementation ensures design review discipline. This six-phase methodology separates initial logic planning from actual test writing, maintaining traceability and structure throughout the feature development cycle.