development-workflow

Manage the software development lifecycle by defining requirements with EARS notation, creating technical designs, and enforcing contribution guidelines through structured pull request processes. This framework ensures clarity and consistency across implementation planning and quality assurance.

EARS notation is a structured method for defining software requirements within spec-driven development. Use EARS notation when starting a new feature to generate clear requirement specifications, which then inform detailed technical designs and track implementation tasks.

Standardize commit messages and branching strategies by applying contribution guidelines that enforce Conventional Commits. This framework standardizes issue creation, branching, commit messages, and pull request processes to maintain consistency across code changes.

Implement quality gates and a Definition of Done by applying robust quality checklists within the development workflow. This ensures high standards are met during the quality assurance process before finalizing code changes and completing pull requests.

Yes, you can generate a feature specification scaffold for spec-driven development. Use the development workflow framework to quickly create requirement, design, and task documents, then follow established contribution guidelines for all related code changes.

The best way to structure technical design and implementation planning is using a spec-driven development approach. Define requirements using EARS notation, create detailed technical designs, and track implementation tasks to ensure comprehensive lifecycle management.