demos: add Java Engineering Excellence demo (full-lifecycle)#136
demos: add Java Engineering Excellence demo (full-lifecycle)#136devin-ai-integration[bot] wants to merge 7 commits into
Conversation
Add presenter thread for the Java Engineering Excellence demo under demos/java-engineering/. Covers four acts: Feature Dev, Issue Triage (with Automations), App Modernization (Java 11→21, Boot 2.6→3.5), and Test Generation — each gated by programmatic verification. References ts-java-spring-boot-realworld playbook and skill.
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| [`ts-java-spring-boot-realworld/.workshop/playbooks/java-engineering-excellence.devin.md`](https://github.com/Cognition-Partner-Workshops/ts-java-spring-boot-realworld/blob/main/.workshop/playbooks/java-engineering-excellence.devin.md). | ||
| The repo-specific build commands and dependency coordinates come from that repo's | ||
| Skill (`.agents/skills/java-engineering-excellence/SKILL.md`). |
There was a problem hiding this comment.
🚩 Technical accuracy of file paths and repo descriptions cannot be fully verified
The document references specific file paths in the external repo ts-java-spring-boot-realworld (e.g., .workshop/playbooks/java-engineering-excellence.devin.md at line 12, .agents/skills/java-engineering-excellence/SKILL.md at line 14) and claims about the repo ("120 source files, 26 test classes" at lines 36-37). Per REVIEW.md: "File paths must exist" and "Repo descriptions must match reality." These cannot be verified from this repo alone since the referenced repo is external. The reviewer should confirm these paths and counts against the actual ts-java-spring-boot-realworld repository's main branch.
Was this helpful? React with 👍 or 👎 to provide feedback.
There was a problem hiding this comment.
Acknowledged — these paths are verified against the actual repo in the companion PR: Cognition-Partner-Workshops/ts-java-spring-boot-realworld#144. The file counts (120 source, 26 test) were confirmed via find . -name "*.java" | wc -l and find . -name "*Test*.java" | wc -l on main.
- Replace blockquote Automation prompt with fenced code block (copy button) - Remove 'Narrative:' facilitator framing labels (now direct context) - Rewrite 'Show the Automation' narration cue as user action - Change 'opens a PR' to 'reports green' in fan-out prompt (default behavior)
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
- Add Quick Start section matching convention in other demo docs - Change 'every class' to 'many classes' per overstatement rule
- Update intro: table showing Skill (auto-loaded), Playbook (tactical), Automation (event-driven) - Rewrite Act 2 with full SAST pipeline: scan -> issue -> Automation -> Devin session - Add Automation setup instructions and trigger-manually fallback - Act 3: reference Skill for general upgrade guidance, prompt is tactical task - Quick Start: update Act 2 description to show event-driven flow
| **How the pieces fit together:** | ||
|
|
||
| | Layer | What it does | How it's loaded | | ||
| |-------|--------------|-----------------| | ||
| | **Skill** (`.agents/skills/`) | General guidance — how to approach upgrades, build commands, test patterns, project layout | Auto-loaded when Devin works in this repo | | ||
| | **Playbook** (`.workshop/playbooks/`) | Tactical, task-specific procedure invoked for a concrete unit of work | User explicitly adds `!java-engineering-excellence` to their prompt | | ||
| | **Automation** | Event-driven trigger — SAST scan creates a GitHub issue, Automation starts a Devin session | Fires automatically on matching events | | ||
|
|
||
| The Skill gives Devin the repo context it needs (where things are, how to build, | ||
| how to approach a Java 11→21 upgrade). The Playbook is the specific procedure | ||
| for a tactical task. Automations close the loop for event-driven work like | ||
| security remediation — no human trigger needed. |
There was a problem hiding this comment.
📝 Info: Preamble length is substantive but mitigated by Quick Start
The demos/AGENTS.md rule says "Keep preamble minimal — no long orientation before the first step." The first actionable prompt (Act 1) doesn't appear until line 99, with ~88 lines preceding it. However, ~27 of those lines are the TOC and Quick Start sections (both required by structure rules). The Quick Start at line 40 provides direct links to each Act, allowing experienced users to skip immediately to Act 1. The remaining preamble — the "How the pieces fit together" table (lines 10-21), Repository section (lines 55-61), and Before/After section (lines 65-88) — provides context a follower needs to understand the demo. This mirrors the pattern in existing demos like demos/data-engineering/sas-to-databricks-demo.md, which has similar orientation before its first prompt. Borderline but consistent with established patterns.
Was this helpful? React with 👍 or 👎 to provide feedback.
There was a problem hiding this comment.
Acknowledged — this is borderline as the reviewer notes. The architecture table (Skill/Playbook/Automation) was explicitly requested to clarify how the pieces relate before the reader encounters the prompts. Combined with the required TOC (rules mandate it for 3+ sections) and the required Quick Start, the preamble is justified. Moving the table after Act 1 would leave the reader confused about what !java-engineering-excellence means when they first encounter it in the Act 1 prompt.
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Demos often need architecture context (Playbook/Skill/Automation relationships) before the first prompt. Update both REVIEW.md and demos/AGENTS.md to clarify that reader-serving context is acceptable — only internally-focused preamble (presales, facilitator logistics) should be flagged.
1 participant
Summary
Adds a new
demos/java-engineering/category with a single-linear-thread presenter demo for Java Engineering Excellence — showing Devin executing four distinct engineering tasks againstts-java-spring-boot-realworld(Java 11 / Spring Boot 2.6.3):javax.validationregressionPlus sections on:
References the
!java-engineering-excellenceplaybook and repo Skill ints-java-spring-boot-realworld(companion PR there). Followsdemos/AGENTS.mdconventions: single linear thread, "Key Takeaways", no facilitator logistics, triple-backtick prompts without "Open a PR".Link to Devin session: https://partner-workshops.devinenterprise.com/sessions/340181af9bb147f990414c67c5e72294
Requested by: @bsmitches