@jenga-ai/agent 1.0.1 → 1.1.1

package/skills/skillify/assets/init-new/assets/directory_structure.txt

@@ -1,10 +1,14 @@
 project/board/epics
 project/board/stories
 project/board/tasks
+project/instructions
 project/configs
 project/data
 project/queue
 project/rapports/problems
 project/rapports/analysis
 project/logs
-documentation
+project/documentation
+project/documentation/plans
+project/documentation/summaries
+project/documentation/examples

package/skills/spinoff/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: spinoff
-description: Capture a diverging topic mid-conversation. Collects context, optionally runs /brainstorm for prerequisites, saves a /todo entry, and returns focus to the primary thread.
+description: Capture a diverging topic mid-conversation. Collects context and a mandatory origin, optionally runs /brainstorm for prerequisites, saves an /idea entry, and returns focus to the primary thread.
 keywords:
   - spinoff
   - diverge
@@ -22,27 +22,32 @@ metadata:
    - Pre-fill the prompt with a one-sentence summary of what the agent detected as the diverging subject (if known).
    - Example: *"It looks like we started discussing [detected topic]. Is that the diverging thread you'd like to capture, or would you like to describe it differently?"*
 
-2. **Collect context** — Summarise the relevant context gathered so far in the current conversation that relates to the diverging topic. This summary will pre-fill the `/todo` description so no context is lost.
+2. **Collect context** — Summarise the relevant context gathered so far in the current conversation that relates to the diverging topic. This summary will pre-fill the `/idea` description so no context is lost.
+
+   **Capture the Origin (mandatory)** — Record:
+   - The EST id (task, story, or epic) that was in progress when the divergence happened, if any is currently being worked. If none is in progress (e.g. the divergence happened during a `/brainstorm`-only session with no active EST item), use `None` — this is a valid, expected case, not a gap to fill in later.
+   - A one-line summary of what the user was doing at the time of the divergence.
 
 3. **Check prerequisites** — Ask the user:
    > "Are the requirements for **[diverging topic]** clear enough to act on, or would you like to run `/brainstorm` first to flesh them out?"
 
    Offer these choices:
-   - **"Requirements are clear — save the todo now"** → go to step 5
+   - **"Requirements are clear — save now"** → go to step 5
    - **"Run /brainstorm first"** → go to step 4
 
-4. **Run /brainstorm (if chosen)** — Invoke the `/brainstorm` skill, passing the diverging topic and collected context as the opening prompt. After `/brainstorm` completes, use the refined output as the todo description.
+4. **Run /brainstorm (if chosen)** — Invoke the `/brainstorm` skill, passing the diverging topic and collected context as the opening prompt. After `/brainstorm` completes, use the refined output as the idea description.
 
-5. **Save the /todo** — Populate `skills/todo/assets/todo_handoff_template.md` with the context collected so far:
+5. **Save via `/idea`** — Populate `skills/idea/assets/idea_handoff_template.md` with the context collected so far:
    - **Mission title**: the diverging topic name (as confirmed in step 1)
    - **Goal / objective**: what the diverging topic aims to achieve
    - **Affected files or scope**: any files or modules identified during the conversation
    - **Intended approach**: the context/approach collected in step 2 (or the refined output from step 4)
    - **Epic/Story linkage**: include a reference if a relevant Epic or Story was identified, otherwise `None`
+   - **Origin**: the EST id (or `None`) and one-line context summary captured in step 2
 
-   Then invoke the `/todo` skill with the populated template. Since the template fields are pre-filled, `/todo` will skip any questions already answered.
+   Then invoke the `/idea` skill with the populated template. Since the template fields are pre-filled, `/idea` will skip any questions already answered. The entry lands in `project/ideas.md`, not `project/todo.md` — `/spinoff` no longer writes to the todo list directly.
 
 6. **Return focus** — Inform the user:
-   > "✅ Diverging topic saved as a todo. Returning focus to **[primary topic]**."
+   > "✅ Diverging topic saved as an idea. Returning focus to **[primary topic]**."
 
    Then resume the primary conversation thread exactly where it was paused.

package/skills/todo/SKILL.md

@@ -32,6 +32,8 @@ metadata:
    - None of the above
 
 4. **Update project documentation** — Add the mission to the appropriate files under `project/board/epics/` and `project/board/stories/` if applicable.
+   - If the mission involves implementing or modifying a skill, apply the **Skill Implementation Principle — Scripts Over Inline Logic** (see `CLAUDE.md` / `AGENTS.md`): note in the story/task's acceptance criteria that deterministic, repeatable steps must be offloaded to scripts under `skills/<name>/scripts/` (or `scripts/`) rather than encoded as inline agent instructions in `SKILL.md`.
+   - If the user indicates the mission is high-risk, or explicitly asks to flag it, set an elevated caution tier directly on the story or task frontmatter: `crucial_level` (one of `advisory`, `gated`, `locked` — see `templates/SCRUM_BOARD_SCHEMA.md` for valid values and their meaning), `crucial_set_by: user`, and `crucial_note` capturing the user's stated reason. This user-initiated flag is written immediately — it does not require the confirm-before-write gate, which applies only to scrum-master-*proposed* caution tiers (a separate, heuristic-driven path).
 
 5. **Add to `project/todo.md`** by running:
    ```