@rasensio/aidlc-content 1.28.0 → 1.29.0

package/package.json

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

package/skills/00-overview.md

@@ -124,22 +124,24 @@ The `aidlc start` CLI automates this; when it is not available, create the insta
    scope_history: []
    ```
    For a worktree instance add `branch: <its-branch>`; for a no-code instance add `branch: null` (blocks Implementation entry until a branch exists). Omit the field entirely otherwise.
-4. For each phase the template defines within the scope, write `phase-<name>.yaml`:
+4. Read the phase list and each phase's artifacts with `aidlc templates show <template> --scope <scope>` — **do not guess them, and do not copy them from another instance**. Different templates require different artifacts, and an instance seeded with artifacts its template never asked for fails its gates on files nobody needs. If the CLI is unavailable, the definitions are in `@rasensio/aidlc-content`'s `templates/` directory.
+5. For each phase that command lists, write `phase-<name>.yaml`, using its artifact names verbatim:
    ```yaml
    phase: <phase-name>
    status: pending
    owner: null
-   entered_at: null
+   entered_at: null      # except the initial phase, which gets created_at
    completed_at: null
    completed_by: null
    skip_reason: null
    artifacts:
-     - name: <artifact>.md
+     - name: <artifact-name-from-templates-show>
        status: not-started
-   metrics: { elapsed_seconds: 0, artifact_count: 0 }
+   metrics: { elapsed_seconds: 0 }
    ```
-5. Fire the `on-instance-start` lifecycle actions (see **Lifecycle Actions**). Do not skip this — automation the user configured (branch creation, issue tracking, notifications) depends on it. When the instance was created via the worktree flow or as no-code, set `AIDLC_WORKTREE=1` in the action environment so the branch-creation action no-ops (the worktree flow already made its branch; a no-code instance must not get one).
-6. Report the instance name, phases, state path, and any actions that fired, then begin the initial phase with its skill.
+   The initial phase takes `entered_at: <the instance's created_at>`. It is the one phase no transition ever enters, so leaving it null means it completes with `elapsed_seconds: 0` and drops out of every lead-time figure.
+6. Fire the `on-instance-start` lifecycle actions (see **Lifecycle Actions**). Do not skip this — automation the user configured (branch creation, issue tracking, notifications) depends on it. When the instance was created via the worktree flow or as no-code, set `AIDLC_WORKTREE=1` in the action environment so the branch-creation action no-ops (the worktree flow already made its branch; a no-code instance must not get one).
+7. Report the instance name, phases, state path, and any actions that fired, then begin the initial phase with its skill.
 
 ## Lifecycle Actions