UC004: Initialize a Repository - No Scaffolding

Overview

Property	Value
ID	UC004
Level	User Goal
Primary Actor	Developer
Trigger	Developer wants this generator's guidelines and Claude Code integration without its CI/build-tool opinions, to choose their own CI system and build tool afterwards
Precondition	Empty target repository exists
Success Guarantee	Target repository populated with guidelines, AI-assistant configuration, and one worked ADR example — no CI workflow, build tooling, or prescriptive ADRs
Related Rules	BR-001, BR-002, BR-003, BR-004, BR-005, BR-008, BR-009, BR-011, BR-015, BR-016

Related Features:

• features/UC004-cpp.feature
• features/UC004-go.feature
• features/UC004-java.feature

Goal

• What problem does this use case solve?
• Populates an empty Git repository with guidelines, .claude/ AI-assistant configuration, and one worked ADR example, so a developer gets this generator's quality baseline without also receiving prescriptive CI/build-tool choices
• Lets a developer pick their own CI system and build tool after repo init, instead of the one this generator would otherwise choose for them (see UC001)
• What does it explicitly NOT do (scope boundary)?
• Generate a CI/CD workflow file
• Generate build tooling (Makefile, language build configuration)
• Generate a language-specific source tree
• Generate the real, prescriptive ADRs UC001 generates (a single worked example is generated instead)
• Modify or update existing repositories (see UC002)

Transaction Boundary

No transaction. Generator writes files. All files are written in case of success. In case of failure only a subset of files will exist in the target folder.

Sequence Diagram

Not applicable

Further Details

For main success scenario, extensions (alternate flows), and BDD scenarios be referred to the corresponding feature file (BDD specification and executable test).