bmad-method-quarkus 1.0.4 → 1.0.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (11) hide show
  1. package/package.json +1 -1
  2. package/src/bmm-skills/agents/bmad-quarkus-build/SKILL.md +25 -5
  3. package/src/bmm-skills/agents/bmad-quarkus-build/skills/quarkus-error-handling-i18n/SKILL.md +6 -2
  4. package/src/bmm-skills/agents/bmad-quarkus-build/skills/quarkus-hexagonal-core/SKILL.md +106 -38
  5. package/src/bmm-skills/agents/bmad-quarkus-build/skills/quarkus-kafka-messaging/SKILL.md +42 -12
  6. package/src/bmm-skills/agents/bmad-quarkus-build/skills/quarkus-observability-otel/SKILL.md +191 -13
  7. package/src/bmm-skills/agents/bmad-quarkus-build/skills/quarkus-openapi-tmforum/SKILL.md +7 -8
  8. package/src/bmm-skills/agents/bmad-quarkus-build/skills/quarkus-security-standards/SKILL.md +132 -0
  9. package/src/bmm-skills/agents/bmad-quarkus-build/skills/quarkus-sql-jdbc-agroal/SKILL.md +30 -13
  10. package/src/bmm-skills/agents/bmad-quarkus-build/skills/quarkus-temporal-workflows/SKILL.md +616 -0
  11. package/src/commands/quarkus-all.md +6 -5
package/src/commands/quarkus-all.md CHANGED
@@ -18,17 +18,18 @@ For each story, invoke exactly **one** skill:
18
18
  bmad-quarkus-build → "Marcus, implement story <story-key>"
19
19
  ```
20
20
 
21
- That is the whole per-story cycle. **Do NOT run `bmad-create-story`, `bmad-dev-story`,
21
+ That is the whole per-story cycle. **Do NOT run `bmad-create-epics-and-stories`, `bmad-build`,
22
22
  or `bmad-code-review` as separate steps** — Marcus owns the full loop (story
23
23
  preparation → red-green-refactor implementation → self-review against the ACs) and
24
- routes into `bmad-build` plus whichever of the 7 Quarkus domain standards the story
24
+ routes into `bmad-build` plus whichever of the 9 Quarkus domain standards the story
25
25
  touches (`quarkus-hexagonal-core`, `quarkus-sql-jdbc-agroal`,
26
26
  `quarkus-error-handling-i18n`, `quarkus-openapi-tmforum`, `quarkus-grpc-services`,
27
- `quarkus-kafka-messaging`, `quarkus-observability-otel`). Splitting the cycle back into
27
+ `quarkus-kafka-messaging`, `quarkus-observability-otel`, `quarkus-security-standards`,
28
+ and `quarkus-temporal-workflows` on Temporal projects). Splitting the cycle back into
28
29
  three commands loses that routing and the native-image/hexagonal review that comes with it.
29
30
 
30
31
  Pass the story key in the invocation so Marcus dispatches directly instead of rendering
31
- his menu (his activation Step 8 skips the menu when the intent is already named).
32
+ his menu (his activation Step 9 skips the menu when the intent is already named).
32
33
 
33
34
  Marcus stays active across stories once activated — do not re-run his activation
34
35
  greeting for every story, just hand him the next story key.
@@ -139,7 +140,7 @@ When every eligible story is `done` or held, stop and report:
139
140
  ## Guardrails
140
141
 
141
142
  - **One `bmad-quarkus-build` invocation per story.** Never decompose it back into
142
- `bmad-create-story` → `bmad-dev-story` → `bmad-code-review`.
143
+ `bmad-create-epics-and-stories` → `bmad-build` → `bmad-code-review`.
143
144
  - Never mark a story `done` unless its tests actually pass and every AC is met. ACs in these
144
145
  stories are verbatim Gherkin — do not edit, reword, or renumber them.
145
146
  - Never start a story in a `[BUILD-PROHIBITED]`, `[BUILD-PROHIBITED in part]`,