@rasensio/aidlc-content 1.39.0 → 1.40.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rasensio/aidlc-content",
-  "version": "1.39.0",
+  "version": "1.40.0",
   "type": "module",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

package/skills/03-entry-point.md

@@ -65,6 +65,7 @@ If `.aidlc/state/` is empty or missing, offer just three options: start somethin
 | Answer pending questions | Open the question file, re-render its open questions per the **Question Protocol** (`.aidlc/resources/rules/question-protocol.md`), record each answer in the file, then fold them into the artifact they were gathered for |
 | Triage the inbox | Follow the **aidlc-roadmap** skill (triage flow) |
 | Browse / promote the roadmap | Follow the **aidlc-roadmap** skill (browse/promote flow) |
+| Start a roadmap item in a new worktree | Follow the **aidlc-roadmap** skill (**Promote into a new worktree**). It ends by handing off to a new session; do not start the phase here |
 | Show status | Summarize each instance from its state files — name, template, current phase, completion %, and whether it looks stalled. When the roadmap is non-empty, append the per-status counts (e.g. "roadmap: 3 inbox, 5 backlog, 12 done") |
 | Review an artifact | Follow the **aidlc-review** skill |
 | Help / getting started | Follow the **aidlc-getting-started** skill |

package/skills/04-roadmap.md

@@ -3,7 +3,7 @@ name: aidlc-roadmap
 description: Captures roadmap items into .aidlc/roadmap/inbox/ at any moment — no instance, claim, or phase required — and browses, triages, promotes, or drops them
 phase: ideation
 priority: 90
-trigger: When the user says "idea:", asks to capture/record an idea or roadmap item, wants to browse the roadmap, or wants to triage, promote, or drop an item
+trigger: When the user says "idea:", asks to capture/record an idea or roadmap item, wants to browse the roadmap, or wants to triage, promote, or drop an item, or asks to start a roadmap item in a new worktree
 native_mode_hint:
   claude-code: >-
     This skill is an interactive inbox, not a phase artifact. Do not enter
@@ -170,6 +170,20 @@ Promotion is where the roadmap meets the lifecycle:
 5. Seed the instance with the item: Full scope → the item is raw material the Ideation phase refines into that phase's required artifact (`idea.md` for the feature templates, `research-question.md` for `spike`); Standard scope → the item is input context for Requirements.
 6. Set `promoted_to: <instance-name>`, move the file to `in-progress/`, and append the `history` entry.
 
+### Promote into a new worktree
+
+When the user asks for a worktree ("create a new worktree for roadmap `<file>`"), they want to work on the item in a separate session — for example one per pane of a session manager. Run the promote steps above with these changes, and do not stop to ask anything the item and config already answer:
+
+1. **Find the item** by file name, `id`, or title, in `backlog/` or `inbox/`. Asking for a worktree counts as choosing to skip triage. When more than one item matches, list them and ask which one.
+2. **Instance name**: the item's file name without its date prefix and extension (the item filed as `20260929-say-what-to-do-next` becomes `say-what-to-do-next`). Template and scope come from the config defaults, unless the item or the user names them.
+3. **Create the instance with** `aidlc start <template> --name <name> --scope <scope> --worktree --non-interactive`. Take the worktree path from the `Worktree:` line it prints. That command creates the branch and the worktree and fires `on-instance-start`; do not repeat any of it by hand.
+4. **Seed the instance inside the worktree** (`<worktree>/.aidlc/state/<name>/`), not the primary checkout. Copy the item into it per step 5 above. Keep the roadmap move (step 6) in the primary checkout, as always.
+5. **Hand off. Do not start the phase in this session.** The work belongs to the new session. End with the exact command that opens it:
+   ```
+   cd <worktree> && claude "/aidlc-continue <name>"
+   ```
+   For Codex, swap `claude` for `codex`. If the user names a session manager, give them the worktree path to point it at.
+
 When the instance completes, the `roadmap-done` lifecycle action moves the item to `done/` on its own — do not do it by hand, and do not remove that action to do it manually.
 
 ## Drop