@arsxxi/iterative-dev-workflow 1.0.0 → 1.0.2

package/commands/phase-2-step-4.md

@@ -1,55 +1,67 @@
----
-description: "Phase 2 Step 4: High-Fidelity Design"
-argument-hint: [feature-slug or description]
----
-
-# Phase 2 Step 4: High-Fidelity Design
-
-## Purpose
-Create High-Level Visualizations for the Component Architecture of the chosen design, using Mermaid.js syntax.
-
-## Steps
-
-1. **Check for the previous result** from Step 3 (Quality Attribute). If it's empty or not generated, DO NOT PROCEED TO EXECUTE THIS STEP — remind the user.
-
-2. **Remind the user to double-check Step 3's result before proceeding.** Present this to the user:
-
-   > Step 3 gave you the chosen design according to the Quality Attributes you designed
-   > previously. Make sure to double-check the results from Step 3 and do your own assessment of
-   > the results given by the AI agent in Step 3. Make sure you select the correct design, not
-   > just bias from the AI's results.
-
-3. **Ask the user to explain their chosen design.** Present this to the user:
-
-   > Briefly explain the design you've selected from the previous phase, and explain from your
-   > opinion why you selected that design. Or if you have your own thoughts/modification, let the
-   > AI agent know here.
-
-   Then stop and wait for the user's explanation. Do not proceed to the analysis/diagram below
-   until they've explained their chosen design.
-
-4. **Analyze the chosen design.** Once the user has explained their chosen design, do a deep
-   dive and meticulous analysis on that chosen design.
-
-5. **Create the System Context Diagram.** Using Mermaid.js syntax, create a System Context
-   Diagram that defines the boundaries of the current solution (feature, system, etc.) we are
-   working on, and shows how the design sits within the whole app.
-
-Once this diagram is done, stop. The User Journey diagram is a separate step -
-`/phase-2-step-5` - run after you've reviewed this one.
-
-## Hard constraints
-
-- AVOID overengineering in the architecture itself — the diagrams should reflect a simple,
-  maintainable structure.
-- Name every box/component in the diagrams using plain-language intent, not jargon.
-
-## Output
-- The user's explanation of their chosen design (and any modifications)
-- Analysis of the chosen design
-- System Context Diagram (Mermaid.js)
-
-## Trigger
-```
-$ARGUMENTS = "feature-slug or description"
-```
+---
+description: "Phase 2 Step 4: High-Fidelity Design"
+argument-hint: [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. `/phase-2-step-4 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 → stop and tell the user to run `/kickoff` first. Don't proceed.
+
+# Phase 2 Step 4: High-Fidelity Design
+
+## Purpose
+Create High-Level Visualizations for the Component Architecture of the chosen design, using Mermaid.js syntax.
+
+## Steps
+
+1. **Check for the previous result** from Step 3 (Quality Attribute). If it's empty or not generated, DO NOT PROCEED TO EXECUTE THIS STEP — remind the user.
+
+2. **Remind the user to double-check Step 3's result before proceeding.** Present this to the user:
+
+   > Step 3 gave you the chosen design according to the Quality Attributes you designed
+   > previously. Make sure to double-check the results from Step 3 and do your own assessment of
+   > the results given by the AI agent in Step 3. Make sure you select the correct design, not
+   > just bias from the AI's results.
+
+3. **Ask the user to explain their chosen design.** Present this to the user:
+
+   > Briefly explain the design you've selected from the previous phase, and explain from your
+   > opinion why you selected that design. Or if you have your own thoughts/modification, let the
+   > AI agent know here.
+
+   Then stop and wait for the user's explanation. Do not proceed to the analysis/diagram below
+   until they've explained their chosen design.
+
+4. **Analyze the chosen design.** Once the user has explained their chosen design, do a deep
+   dive and meticulous analysis on that chosen design.
+
+5. **Create the System Context Diagram.** Using Mermaid.js syntax, create a System Context
+   Diagram that defines the boundaries of the current solution (feature, system, etc.) we are
+   working on, and shows how the design sits within the whole app.
+
+Once this diagram is done, stop. The User Journey diagram is a separate step -
+`/phase-2-step-5` - run after you've reviewed this one.
+
+## Hard constraints
+
+- AVOID overengineering in the architecture itself — the diagrams should reflect a simple,
+  maintainable structure.
+- Name every box/component in the diagrams using plain-language intent, not jargon.
+
+## Output
+- The user's explanation of their chosen design (and any modifications)
+- Analysis of the chosen design
+- System Context Diagram (Mermaid.js)
+
+## Trigger
+```
+$ARGUMENTS = "project name"
+```

package/commands/phase-2-step-5.md

@@ -1,22 +1,34 @@
----
-description: "Phase 2 Step 5: User Journey"
-argument-hint: [feature-slug or description]
----
-
-# Phase 2 Step 5: User Journey
-
-## Purpose
-Create a User Journey Diagram using Mermaid.js syntax for the chosen design from Step 4 (High-Fidelity Design).
-
-## Steps
-
-1. **Check for the previous result** from Step 4 (High-Fidelity Design). If it's empty or not generated, DO NOT PROCEED — remind the user.
-2. **Create the User Journey Diagram** using Mermaid.js syntax, mapping the user's interaction flow through the system.
-
-## Output
-- User Journey Diagram (Mermaid.js)
-
-## Trigger
-```
-$ARGUMENTS = "feature-slug or description"
-```
+---
+description: "Phase 2 Step 5: User Journey"
+argument-hint: [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. `/phase-2-step-5 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 → stop and tell the user to run `/kickoff` first. Don't proceed.
+
+# Phase 2 Step 5: User Journey
+
+## Purpose
+Create a User Journey Diagram using Mermaid.js syntax for the chosen design from Step 4 (High-Fidelity Design).
+
+## Steps
+
+1. **Check for the previous result** from Step 4 (High-Fidelity Design). If it's empty or not generated, DO NOT PROCEED — remind the user.
+2. **Create the User Journey Diagram** using Mermaid.js syntax, mapping the user's interaction flow through the system.
+
+## Output
+- User Journey Diagram (Mermaid.js)
+
+## Trigger
+```
+$ARGUMENTS = "project name"
+```

package/commands/phase-3.md

@@ -1,33 +1,45 @@
----
-description: "Phase 3: Implementation Plan"
-argument-hint: [feature-slug or description]
----
-
-# Phase 3: Implementation Plan
-
-## Purpose
-Write a comprehensive implementation plan based on the proposed plan and extensive architecture and design from Phase 1 and Phase 2.
-
-## Steps
-
-1. **Check for the previous result** from the previous step. If it's empty or not generated due to certain reason, then DO NOT PROCEED TO EXECUTE THIS STEP. Don't forget to remind the user if this happened.
-2. **Write a comprehensive implementation plan** based on the proposed plan (Phase 1: Analyze) and extensive architecture and design (Phase 2: Design - the chosen design, ATAM trade-offs, Quality Attribute results, System Context Diagram, and User Journey Diagram).
-
-## Constraints
-
-AVOID overengineering, PREFER simple, low-complexity implementations with the GOAL of high maintainability, AVOID jargons when naming function/methods/class/components/system, instead PRIORITIZE using layman's terms or prefer naming with the actual intentions of the code, the GOAL is ease of developer understanding and maintainability.
-
-## Iteration rule
-
-If, while writing the implementation plan, you find a problem that is actually a Design problem
-(not an implementation detail) - e.g. the architecture from Phase 2 doesn't actually support
-something needed - STOP and tell the user clearly, and recommend circling back to Phase 2. Do
-not silently work around a design flaw in the plan.
-
-## Output
-- A comprehensive implementation plan, written to `.workflow/<slug>/03-implement.md`
-
-## Trigger
-```
-$ARGUMENTS = "feature-slug or description"
-```
+---
+description: "Phase 3: Implementation Plan"
+argument-hint: [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. `/phase-3 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 → stop and tell the user to run `/kickoff` first. Don't proceed.
+
+# Phase 3: Implementation Plan
+
+## Purpose
+Write a comprehensive implementation plan based on the proposed plan and extensive architecture and design from Phase 1 and Phase 2.
+
+## Steps
+
+1. **Check for the previous result** from the previous step. If it's empty or not generated due to certain reason, then DO NOT PROCEED TO EXECUTE THIS STEP. Don't forget to remind the user if this happened.
+2. **Write a comprehensive implementation plan** based on the proposed plan (Phase 1: Analyze) and extensive architecture and design (Phase 2: Design - the chosen design, ATAM trade-offs, Quality Attribute results, System Context Diagram, and User Journey Diagram).
+
+## Constraints
+
+AVOID overengineering, PREFER simple, low-complexity implementations with the GOAL of high maintainability, AVOID jargons when naming function/methods/class/components/system, instead PRIORITIZE using layman's terms or prefer naming with the actual intentions of the code, the GOAL is ease of developer understanding and maintainability.
+
+## Iteration rule
+
+If, while writing the implementation plan, you find a problem that is actually a Design problem
+(not an implementation detail) - e.g. the architecture from Phase 2 doesn't actually support
+something needed - STOP and tell the user clearly, and recommend circling back to Phase 2. Do
+not silently work around a design flaw in the plan.
+
+## Output
+- A comprehensive implementation plan, written to `.workflow/<slug>/03-implement.md`
+
+## Trigger
+```
+$ARGUMENTS = "project name"
+```

package/commands/phase-4.md

@@ -1,29 +1,41 @@
----
-description: "Phase 4: Postmortem"
-argument-hint: [feature-slug or description]
----
-
-# Phase 4: Postmortem
-
-## Purpose
-Reflect on the iteration to improve the next one.
-
-## Prerequisites
-- Phase 3 (Implement) is complete
-
-## Steps
-
-1. **What went well?** — capture successful patterns
-2. **What could be better?** — identify friction and slowdowns
-3. **What will we do differently?** — concrete improvements for next iteration
-4. **Update workflow** — if a process change is needed, update the relevant command files
-
-## Output
-- Postmortem document
-- Action items for next iteration
-- Updated workflow documentation (if needed)
-
-## Trigger
-```
-$ARGUMENTS = "feature-slug or description"
-```
+---
+description: "Phase 4: Postmortem"
+argument-hint: [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. `/phase-4 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 → stop and tell the user to run `/kickoff` first. Don't proceed.
+
+# Phase 4: Postmortem
+
+## Purpose
+Reflect on the iteration to improve the next one.
+
+## Prerequisites
+- Phase 3 (Implement) is complete
+
+## Steps
+
+1. **What went well?** — capture successful patterns
+2. **What could be better?** — identify friction and slowdowns
+3. **What will we do differently?** — concrete improvements for next iteration
+4. **Update workflow** — if a process change is needed, update the relevant command files
+
+## Output
+- Postmortem document
+- Action items for next iteration
+- Updated workflow documentation (if needed)
+
+## Trigger
+```
+$ARGUMENTS = "project name"
+```

package/commands/session-transcript.md

@@ -1,57 +1,69 @@
----
-description: "Session Transcript"
-argument-hint: [optional: feature-slug]
----
-
-# 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. **Determine the feature slug.** Use `$ARGUMENTS` if provided. If not provided, use the project root directory name or "session" as fallback.
-
-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 slug was provided, use `aichat.md`.
-
-## Trigger
-```
-$ARGUMENTS = "optional: feature-slug"
-```
+---
+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 feature slug 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,30 +1,42 @@
 {
   "name": "@arsxxi/iterative-dev-workflow",
-  "version": "1.0.0",
+  "version": "1.0.2",
   "description": "A structured 4-phase iterative development workflow for AI coding agents.",
-  "keywords": ["opencode-plugin", "opencode", "workflow", "methodology"],
+  "keywords": [
+    "opencode-plugin",
+    "opencode",
+    "workflow",
+    "methodology"
+  ],
   "license": "MIT",
   "author": {
     "name": "Clio",
-    "url": "https://github.com/Arsxxi"
+    "url": "https://github.com/arsxxi/iterative-dev-workflow"
   },
-  "homepage": "https://github.com/Arsxxi/Iterative-dev-workflow",
+  "homepage": "https://github.com/arsxxi/iterative-dev-workflow",
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/Arsxxi/Iterative-dev-workflow.git"
+    "url": "git+https://github.com/arsxxi/iterative-dev-workflow.git"
   },
   "bugs": {
-    "url": "https://github.com/Arsxxi/Iterative-dev-workflow/issues"
+    "url": "https://github.com/arsxxi/iterative-dev-workflow/issues"
   },
   "main": "./.opencode/plugins/iterative-dev-workflow.mjs",
   "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"