repo-practicing-trunk-based-development

What problem does it solve?

This Skill solves the common pain points of disorganized git workflows, including excessive unnecessary branching, frequent merge conflicts, slow integration cycles, and complicated branching strategies that delay feature delivery and increase team collaboration overhead.

Core Features & Use Cases

• Trunk Based Development core rules: Clear guidance that 99% of work happens directly on the main branch with small, frequent commits, eliminating the need for most feature branches.
• Branch justification framework: Explicit, validated criteria for the only 4 scenarios where branches are allowed (experimental high-risk work, external contributions, compliance/audit requirements, parallel maintenance versions) to prevent unnecessary branch creation.
• Feature flag and environment branch guidance: Best practices for hiding incomplete work on main using feature flags instead of branches, and rules to prevent accidental commits to deployment-only environment branches.
• Use Case: For a team building a new user authentication feature that will take 3 days to complete, use this Skill to commit incremental changes directly to main behind a feature flag instead of creating a long-lived feature branch, reducing merge conflict risk and keeping the entire team aligned on the latest codebase.

Quick Start

Use the trunk based development skill to plan your team's git workflow for the new payment processing feature, ensuring all incremental commits go to the main branch with feature flags for any incomplete work.