agentleFS
dariopalminiodariopalminio/agile-sddf-extension/skills/git-tbd-for-sdd/SKILL.md

git-tbd-for-sdd

Skill0 starsChanged 2 months agoMITView on GitHub

Apply Trunk-Based Development with SDD integration. Short-lived

  • Commits and pushes

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Place it in .husky/pre-commit or a CI job.

    line 98

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Git TBD for SDD

Trunk-based development with a spec-first overlay for SDD (Specification-Driven Development). Branches are short-lived, main is the only integration point, and specs merge before the code that implements them.

Use this skill when: deciding how to branch, commit, open a PR, cut a release, or handle a hotfix.

Skip this skill when: working locally with no intent to push, or on throwaway experiments.

Core rules

  1. main is the only integration point. Every branch merges back to main.
  2. Branches are short-lived — hours to 2–3 days. Never more than a week.
  3. Branch prefixes are contractual:
    • feat/* → code + the spec it implements only
    • spec/* → docs/specs/** only
    • docs/* → docs/** except docs/specs/
    • epic/* → temporary integration branch, ≤ 6 weeks; features branch from it and PR back to it, not to main
  4. A new spec merges to main before its implementation branch starts.
  5. Specs discovered mid-feature go to docs/specs/_inbox/. Promotion to canonical is a deliberate act in a spec/* branch.
  6. Releases are cut from main or from a short-lived release/* branch — never from a feature branch.

Branch model

main ──●──●──●──●──●──●──●──►  (trunk, always deployable)
       ╲  ╲     ╱     ╱
        feat feat  release/*
        (hours–days)

Two flows you will use daily

Feature (code):

git switch main && git pull
git switch -c feat/STORY-NNN-slug
# code + the STORY-NNN spec only
git commit -m "feat(scope): ..."
git push -u origin feat/STORY-NNN-slug   # PR → main

Spec (before the feature):

git switch main && git pull
git switch -c spec/STORY-NNN-draft
# write docs/specs/.../STORY-NNN/story.md
git commit -m "docs(spec): add STORY-NNN"
git push -u origin spec/STORY-NNN-draft  # PR → main

References

Load only the file you need. Each is standalone.

TopicLoad when…File
Branch modelOnboarding, or redesigning the flowreferences/branch-model.md
Spec Branch (SDD + TBD)Separating spec authoring from implementationreferences/spec-branch.md
Commit conventionsWriting a commit messagereferences/commits.md
PR disciplineOpening or reviewing a PRreferences/pr.md
Release from trunkCutting a release without a branchreferences/release-from-trunk.md
Release branchesMaintaining frozen versions with hotfixesreferences/release-branches.md
Hotfix flowFixing production urgentlyreferences/hotfix.md
Feature flagsMerging incomplete work safelyreferences/feature-flags.md
RollbackReverting a bad releasereferences/rollback.md
Epic branchesBatching features with joint regression before mainreferences/epic-branch.md

Enforcement (optional but recommended)

Reject any spec/* branch that touches files outside docs/specs/:

BRANCH=$(git rev-parse --abbrev-ref HEAD)
if [[ "$BRANCH" == spec/* ]] && git diff --name-only main | grep -qv '^docs/specs/'; then
  echo "spec/* only touches docs/specs/"; exit 1
fi

Place it in .husky/pre-commit or a CI job. One-directional, cheap, effective.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.