fix(bundle-builder): generate umbrella SKILL.md as discoverable entry point #53

Merged

jasper merged 1 commit from fix/bundle-builder-umbrella-entry into main

2026-06-13 14:53:30 -04:00

magnus commented

2026-05-29 23:16:04 -04:00

Owner

Summary

Fixes #52 — the bundle-builder never generated an umbrella SKILL.md at the bundle root, making generated workflow bundles invisible to the agent during auto-detection.

Changes

Three files in the workflow-architect bundle:

`skills/bundle-builder/SKILL.md` (+58/-4)

Added Step 0 to the file creation order: generate an umbrella SKILL.md at <bundle-name>/SKILL.md with:
- Frontmatter: name, description with broad trigger conditions, tags (workflow, bundle:generated, archetype)
- Body: Mermaid flowchart, phase table (Phase / Load this skill / When), navigation instructions, heuristics
Write via write_file, then register via skill_manage(action="create")
Updated Output Structure diagram to show SKILL.md at root with annotation
Updated Cleanup to verify umbrella registration and recommend skill_view(name="<bundle-name>")

`SKILL.md` (+9/-2)

Added "Umbrella SKILL.md" as first item in What You Get list
Extended Loading Protocol step 5 to mention umbrella registration and auto-detectability

`AGENTS.md` (+14/-0)

Added Registration section explaining umbrella and sub-skill registration via skill_manage()

Why

Without the umbrella, a generated bundle is an invisible collection of sub-skills. The agent can only load them if told exact names. With the umbrella, the agent auto-detects "oh, the user is starting their morning routine — I should load that bundle" based on trigger conditions in the umbrella description. This makes workflow-architect-generated bundles actually useful in day-to-day sessions.

QA

Umbrella template includes: frontmatter (name, description, tags), body (flowchart, phase table, navigation, heuristics)
Registration step included for umbrella
Output structure diagram updated
Cleanup verifies umbrella loads
All three bundle files patched consistently

[Jasper - AI agent on behalf of Magnus Hedemark]

## Summary Fixes #52 — the `bundle-builder` never generated an umbrella `SKILL.md` at the bundle root, making generated workflow bundles invisible to the agent during auto-detection. ## Changes Three files in the `workflow-architect` bundle: ### `skills/bundle-builder/SKILL.md` (+58/-4) - Added **Step 0** to the file creation order: generate an umbrella `SKILL.md` at `<bundle-name>/SKILL.md` with: - Frontmatter: name, description with broad trigger conditions, tags (`workflow`, `bundle:generated`, archetype) - Body: Mermaid flowchart, phase table (Phase / Load this skill / When), navigation instructions, heuristics - Write via `write_file`, then register via `skill_manage(action="create")` - Updated **Output Structure** diagram to show `SKILL.md` at root with annotation - Updated **Cleanup** to verify umbrella registration and recommend `skill_view(name="<bundle-name>")` ### `SKILL.md` (+9/-2) - Added "Umbrella SKILL.md" as first item in **What You Get** list - Extended Loading Protocol step 5 to mention umbrella registration and auto-detectability ### `AGENTS.md` (+14/-0) - Added **Registration** section explaining umbrella and sub-skill registration via `skill_manage()` ## Why Without the umbrella, a generated bundle is an invisible collection of sub-skills. The agent can only load them if told exact names. With the umbrella, the agent auto-detects "oh, the user is starting their morning routine — I should load that bundle" based on trigger conditions in the umbrella description. This makes workflow-architect-generated bundles actually useful in day-to-day sessions. ## QA - [x] Umbrella template includes: frontmatter (name, description, tags), body (flowchart, phase table, navigation, heuristics) - [x] Registration step included for umbrella - [x] Output structure diagram updated - [x] Cleanup verifies umbrella loads - [x] All three bundle files patched consistently [Jasper - AI agent on behalf of Magnus Hedemark]

magnus added 1 commit

2026-05-29 23:16:04 -04:00

fix(bundle-builder): generate umbrella SKILL.md as discoverable entry point 77f9d16ef3

Add Step 0 to the bundle-builder file creation order: generate and
register an umbrella SKILL.md at the bundle root before any sub-skills
are created. The umbrella provides the auto-detectable entry point
with broad trigger conditions, Mermaid flowchart, phase table, and
navigation instructions.

Also update:
- workflow-architect SKILL.md: list umbrella in 'What You Get' and
  update Loading Protocol step 5 to mention registration
- workflow-architect AGENTS.md: add Registration section explaining
  how umbrella and sub-skills are registered via skill_manage()

Closes #52

magnus force-pushed fix/bundle-builder-umbrella-entry from 77f9d16ef3 to 9372e4d1ee

2026-06-13 14:53:27 -04:00

Compare