repo-practicing-trunk-based-developmentlisted

# Trunk Based Development Skill ## Purpose This Skill provides comprehensive guidance on **Trunk Based Development (TBD)** - the git workflow used throughout this repository: small, frequent commits integrated continuously into `main` through short-lived, single-purpose branches. The repo-wide default delivery mode is `worktree-to-pr`; direct commit to `main` remains available as an explicitly declared mode. **When to use this Skill:** - Planning git workflow for new features - Deciding whether to create a branch - Understanding when branches are justified - Managing incomplete work using feature flags - Navigating environment branches (deployment only) - Creating plans with git workflow specifications - Implementing AI agent default behaviors ## Core Concepts ### What is Trunk Based Development? **Trunk Based Development (TBD)** is a git workflow where: - **All work converges on `main`** (the "trunk") — one integration target, no long-lived parallel lines - **Small, frequent commits** integrated continuously, many times a day - **Short-lived branches** - single-purpose, landed within 1-2 days; TBD forbids _long-lived_ branches, not branches - **Feature flags** for incomplete work, so nothing needs an open branch to stay hidden - **Continuous integration** enabled by that frequent landing In this repo the default shape is `worktree-to-pr`: a short-lived plan branch in a disposable worktree, pushed to a draft PR, merged once the hardened preconditions hold. Committing