six-step-sop

The six-step SOP automates feature development from branch creation through verification, guiding you through acceptance criteria, SPEC planning, TDD implementation, and commit-ready verification within standard Git workflows.

A feature development SOP structures the complete process: branch naming, acceptance criteria drafting, SPEC documentation, test-driven implementation, code creation, and final verification to ensure quality and reduce implementation drift.

Use the SOP's planning steps to define acceptance criteria, create BRIEF.md and SPEC.md documents outlining requirements and design, then proceed to TDD and implementation with clear scope and expectations.

Yes, the six-step SOP applies to standard Git workflows with explicit branch naming scope, integrating into your existing version control practices while adding structured steps for feature planning and verification.

Verification confirms your implementation is commit-ready by validating tests pass, code meets specs, and all documentation is complete, ensuring quality before merging back to your main branch.

Use a feature development SOP when teams need consistent quality, clear documentation, and reduced drift across multiple features—particularly in collaborative environments where explicit planning and verification prevent implementation issues.