Bootstrap Prompt for Implementation

Prepare yourself for implementation tasks in this session. Do not change any code yet; the bootstrap only builds context. The concrete task will follow separately.

Always-on Instructions

The tool’s general project instructions already apply, such as AGENTS.md or CLAUDE.md. Do not reread them if the tool loaded them automatically. This bootstrap prompt only adds the “implementation” work mode.

Read Project Context

Read the following documents if they exist, and extract only the information that is relevant for implementation tasks:

• Repository root: README.md
• Architecture documentation under docs/, especially docs/architecture.md
• Semantic data model under docs/, especially docs/semantic_data_model.md
• Feature specifications under docs/
• Maven build configuration: pom.xml
• Java source code and resources: src/main/java, src/main/resources
• Tests and test resources: src/test/java, src/test/resources

Implementation Rules

• Always limit changes to the scope of the current task.
• Do not perform unsolicited refactorings, renames, or architecture changes.
• Follow existing code patterns in the project: naming conventions, package structure, error handling, test style, and documentation language.
• Create tests for relevant new or changed logic. Do not test trivial methods without behavior of their own.

Handling Uncertainty

• If information is missing or documents contradict each other, state that explicitly and ask.
• Only make assumptions if they are small, reversible, and clearly justified.
• Discuss unclear architecture, data model, or API decisions before implementing them.

Verification

Use the Maven Wrapper (./mvnw) if it exists in the repository. Otherwise use mvn.

After code changes, run at least:

• ./mvnw test or mvn test for unit tests
• ./mvnw clean verify or mvn clean verify for the full Maven build including integration tests

Report which Maven commands succeeded or could not be run.

AI-Driven Development Process

Work in this session according to this process:

1. The starting point is a feature specification or a clearly formulated task.
2. Before implementing, create a short implementation plan as Markdown.
3. Wait for explicit approval of the plan before changing code.
4. Then implement step by step and stay close to the approved plan.
5. After completion, briefly document what changed, which checks ran, and which risks remain.

Bootstrap Output

Briefly summarize which sources you read, which project rules are relevant, which Maven commands you will use for build and tests, and which open questions remain. Then wait for the concrete implementation task.