@arsxxi/iterative-dev-workflow 1.0.1 → 1.0.2

package/commands/session-transcript.md

@@ -1,71 +1,69 @@
----
-description: "Session Transcript"
-argument-hint: [optional: project name]
----
-
-## Step 0 — find which project this is for
-
-Before anything else, figure out which project this command applies to:
-
-1. If you were given a project name after the slash (e.g. `/session-transcript my-project`), use it.
-2. Otherwise, look at the subfolders under `.workflow/`:
-   - Exactly one folder → use it. Tell the user which project you picked (e.g. "Working on
-     `my-project`"), so it's never a silent guess.
-   - Two or more folders → ask the user once which project this is for. To make the question
-     useful, show the first line of each project's `00-context.md`, not just the folder name.
-   - No folders → fall back to the project root directory name as the project name (this is the
-     one case where no project is in progress yet — a transcript may legitimately exist outside
-     of `.workflow/`).
-
-# Session Transcript
-
-## Purpose
-Record this session's conversation as-is, in chronological order (who said what), as a standalone factual record — separate from the workflow's phase deliverables (which only contain final results, not the discussion that led to them).
-
-## Steps
-
-1. **Scan the project root.** Do NOT create any new folders. Determine the project root directory (where `.git/` or `package.json` or similar marker exists). Save the transcript directly in the project root.
-
-2. **Scan the project root.** Do NOT create any new folders. Determine the project root directory (where `.git/` or `package.json` or similar marker exists). Save the transcript directly in the project root.
-
-3. **Reconstruct this session's conversation in chronological order**, turn by turn, labeled by
-   who said it (`User` / `Agent`). Use the actual wording from the conversation - do not
-   summarize, paraphrase, condense, or skip turns.
-
-4. **Be honest about context limits.** You can only transcribe what's actually present in your
-   current context window for this session. If earlier turns were compacted, truncated, or are
-   otherwise not available to you, say so explicitly at the top of the file (e.g. "Transcript
-   starts partway through the session - earlier turns were not available in context") instead of
-   inventing or guessing what was said.
-
-5. **Check for an existing transcript file.** If `aichat-<slug>.md` already exists from a
-   previous run, do not overwrite it - append this session's transcript below the existing
-   content, under a new dated section, so multiple sessions accumulate in one file.
-
-## Output format
-
-```markdown
-# Session Transcript
-
-## Project: <project-name>
-
-## Session: <date/time if known, otherwise "session N">
-
-### User
-<verbatim text of the turn>
-
-### Agent
-<verbatim text of the turn>
-
-### User
-<verbatim text of the turn>
-
-...
-```
-
-Write the result to `aichat-<slug>.md` in the project root. If no project name was provided, use `aichat.md`.
-
-## Trigger
-```
-$ARGUMENTS = "optional: project name"
-```
+---
+description: "Session Transcript"
+argument-hint: [optional: project name]
+---
+
+## Step 0 — find which project this is for
+
+Before anything else, figure out which project this command applies to:
+
+1. If you were given a project name after the slash (e.g. `/session-transcript my-project`), use it.
+2. Otherwise, look at the subfolders under `.workflow/`:
+   - Exactly one folder → use it. Tell the user which project you picked (e.g. "Working on
+     `my-project`"), so it's never a silent guess.
+   - Two or more folders → ask the user once which project this is for. To make the question
+     useful, show the first line of each project's `00-context.md`, not just the folder name.
+   - No folders → fall back to the project root directory name as the project name (this is the
+     one case where no project is in progress yet — a transcript may legitimately exist outside
+     of `.workflow/`).
+
+# Session Transcript
+
+## Purpose
+Record this session's conversation as-is, in chronological order (who said what), as a standalone factual record — separate from the workflow's phase deliverables (which only contain final results, not the discussion that led to them).
+
+## Steps
+
+1. **Scan the project root.** Do NOT create any new folders. Determine the project root directory (where `.git/` or `package.json` or similar marker exists). Save the transcript directly in the project root.
+
+2. **Reconstruct this session's conversation in chronological order**, turn by turn, labeled by
+   who said it (`User` / `Agent`). Use the actual wording from the conversation - do not
+   summarize, paraphrase, condense, or skip turns.
+
+3. **Be honest about context limits.** You can only transcribe what's actually present in your
+   current context window for this session. If earlier turns were compacted, truncated, or are
+   otherwise not available to you, say so explicitly at the top of the file (e.g. "Transcript
+   starts partway through the session - earlier turns were not available in context") instead of
+   inventing or guessing what was said.
+
+4. **Check for an existing transcript file.** If `aichat-<slug>.md` already exists from a
+   previous run, do not overwrite it - append this session's transcript below the existing
+   content, under a new dated section, so multiple sessions accumulate in one file.
+
+## Output format
+
+```markdown
+# Session Transcript
+
+## Project: <project-name>
+
+## Session: <date/time if known, otherwise "session N">
+
+### User
+<verbatim text of the turn>
+
+### Agent
+<verbatim text of the turn>
+
+### User
+<verbatim text of the turn>
+
+...
+```
+
+Write the result to `aichat-<slug>.md` in the project root. If no project name was provided, use `aichat.md`.
+
+## Trigger
+```
+$ARGUMENTS = "optional: project name"
+```

package/commands/session-transcript.toml

@@ -1,2 +1,2 @@
-description = "Session Transcript — write verbatim chronological transcript to project root as aichat-<slug>.md"
-prompt = "Run Session Transcript. Determine project name from $ARGUMENTS if provided, otherwise use project root directory name. Scan the project root — do NOT create any new folders. Reconstruct conversation chronologically, labeled by User/Agent — verbatim, no summarization. If context is truncated, say so. If aichat-<slug>.md exists, append under new dated section instead of overwriting. Output: write to aichat-<slug>.md in project root. Reference: $ARGUMENTS"
+description = "Session Transcript — write verbatim chronological transcript to project root as aichat-<slug>.md"
+prompt = "Run Session Transcript. Determine project name from $ARGUMENTS if provided, otherwise use project root directory name. Scan the project root — do NOT create any new folders. Reconstruct conversation chronologically, labeled by User/Agent — verbatim, no summarization. If context is truncated, say so. If aichat-<slug>.md exists, append under new dated section instead of overwriting. Output: write to aichat-<slug>.md in project root. Reference: $ARGUMENTS"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@arsxxi/iterative-dev-workflow",
-  "version": "1.0.1",
+  "version": "1.0.2",
   "description": "A structured 4-phase iterative development workflow for AI coding agents.",
   "keywords": [
     "opencode-plugin",
@@ -25,11 +25,18 @@
   "exports": {
     ".": "./.opencode/plugins/iterative-dev-workflow.mjs"
   },
+  "bin": {
+    "iterative-dev-workflow-install": "./bin/install-opencode-commands.mjs"
+  },
+  "scripts": {
+    "postinstall": "node ./bin/install-opencode-commands.mjs || true"
+  },
   "files": [
     "AGENTS.md",
     ".opencode/",
     "commands/",
-    "skills/"
+    "skills/",
+    "bin/"
   ],
   "publishConfig": {
     "access": "public"