tibursocampos/agent-dev-toolkit / core/skills/java-developer
java-developer
VerifiedImplement or fix small-to-medium Java features without full SDD (Spring Boot default). Use for isolated JVM/Spring Boot work or when invoking /java-developer.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.3 KB |
| reference.md | markdown | 459 B |
| references/execute-flow.md | markdown | 3.3 KB |
| references/must-not.md | markdown | 707 B |
| references/scope.md | markdown | 560 B |
references/execute-flow.md
View on GitHub# java-developer — execute flow
Read this file for procedural detail. Do not dump stack guideline packs into chat or child prompts — lazy-load **one** guideline file when that surface is in scope.
### Subagent-first (before implement)
Classify complexity → consult capability `subagents` → if medium/complex and `native`: spawn ≤2 children (scoped **paths** + **receipt**); **trivial** stays **in-parent**; if `subagents=none` or Agent unavailable → **fallback** **in-parent** (never hard-fail). Load `SPAWN.md` + `subagent-first.md`; do not paste guidelines into child prompts.
### 0. Workspace
Confirm target repo (`pom.xml` and/or Gradle `build.gradle` / `build.gradle.kts` / `settings.gradle*`). Read `AGENTS.md` / `README.md`. Default framework: **Spring Boot** unless the project clearly uses another stack (do not invent Quarkus/Micronaut as defaults). Summarize the user request and acceptance.
### 1. Guidelines (step 0.5)
Follow `{{TOOLKIT_ROOT}}/skills/_shared/developer-common/step-0.5-review-guidelines.md`: load only the `java-guidelines` files needed for this task. Confirm test stack aligned to the project (prefer **JUnit 5**, **Mockito**, **AssertJ** when greenfield).
### 2. Branch (step 3)
Baseline branch from user or repo default. Create/checkout `feature/<slug>` or `feat/<id>-<slug>` - never commit on `main` / `master` / `develop`.
### 3. Plan micro-steps
Checkpoint durable workflow progress at the workflow-defined boundaries; context usage does not add a stop gate.
### 4. Implement
Discover architectural patterns in the touched area first. Follow `structure-and-quality.md` §1: an operator order and the established project style outrank the toolkit style bar. Do not restyle existing members without an explicit yes. On greenfield / no clear comment-language mirror, ask before writing narrative comments/docs (identifiers stay English).
Match existing project patterns (Glob/Read similar types first). Prefer Spring Boot idioms: controllers/REST, services, repositories, DTOs, validation.
| Layer | Typical work |
|-------|----------------|
| Web | Controllers, filters, DTOs, validation |
| Service | Application services, domain rules |
| Persistence | Repositories, entities, migrations |
| Integration | Clients, messaging consumers/producers |
Apply `spring-boot-defaults.md` and `layered-structure.md` from `java-guidelines/` while writing - do not paste full bodies into chat.
### 5. Tests
Add or update tests for changed behavior. Prefer integration tests (`@SpringBootTest` / slice tests) for real flows when the project already uses them; unit tests for isolated logic.
### 6. Build and test
Maven:
```bash
./mvnw test
# or: mvn test
```
Gradle:
```bash
./gradlew test
```
Fix failures within scope. Ask before running the full multi-module suite if the repo is very large.
### 7. Pre-commit (step 3.5) and handoff
Run `{{TOOLKIT_ROOT}}/skills/_shared/developer-common/step-3.5-precommit-validation.md` when appropriate. Offer `/commit` - do not commit automatically.
Before push/PR, run `{{TOOLKIT_ROOT}}/skills/_shared/developer-common/step-7-checklist.md` and `{{TOOLKIT_ROOT}}/skills/_shared/java-guidelines/checklist.md`.
### 8. SDD escalation
If scope grows during work, stop and recommend:
```
/sdd-spec - [feature description]
# then
/sdd-plan - PRD/...
# then
/sdd-develop - PLAN/... - Step 1
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |