@exodus/openspec 1.2.2 → 1.2.3

package/dist/core/templates/workflows/apply-change.js

@@ -13,7 +13,7 @@ export function getApplyChangeSkillTemplate() {
    If a name is provided, use it. Otherwise:
    - Infer from conversation context if the user mentioned a change
    - Auto-select if only one active change exists
-   - If ambiguous, run \`openspec list --json\` to get available changes and use the **AskUserQuestion tool** to let the user select
+   - If ambiguous, check for a workspace manifest (\`cat openspec/workspace.yaml 2>/dev/null\`). If it exists, run \`(cd <scope.path> && openspec list --json)\` for each scope and \`ls openspec/changes/ 2>/dev/null\` for umbrella changes; otherwise run \`openspec list --json\`. Aggregate all results and use the **AskUserQuestion tool** to let the user select, showing which scope each change belongs to
 
    Always announce: "Using change: <name>" and how to override (e.g., \`/opsx:apply <other>\`).
 
@@ -196,7 +196,7 @@ export function getOpsxApplyCommandTemplate() {
    If a name is provided, use it. Otherwise:
    - Infer from conversation context if the user mentioned a change
    - Auto-select if only one active change exists
-   - If ambiguous, run \`openspec list --json\` to get available changes and use the **AskUserQuestion tool** to let the user select
+   - If ambiguous, check for a workspace manifest (\`cat openspec/workspace.yaml 2>/dev/null\`). If it exists, run \`(cd <scope.path> && openspec list --json)\` for each scope and \`ls openspec/changes/ 2>/dev/null\` for umbrella changes; otherwise run \`openspec list --json\`. Aggregate all results and use the **AskUserQuestion tool** to let the user select, showing which scope each change belongs to
 
    Always announce: "Using change: <name>" and how to override (e.g., \`/opsx:apply <other>\`).
 

package/dist/core/templates/workflows/archive-change.js

@@ -10,8 +10,24 @@ export function getArchiveChangeSkillTemplate() {
 
 1. **If no change name provided, prompt for selection**
 
-   Run \`openspec list --json\` to get available changes. Use the **AskUserQuestion tool** to let the user select.
+   Check for a workspace manifest:
+   \`\`\`bash
+   cat openspec/workspace.yaml 2>/dev/null
+   \`\`\`
+
+   If workspace.yaml exists, list changes across all scopes:
+   \`\`\`bash
+   (cd <scope.path> && openspec list --json)   # for each scope in workspace.yaml
+   ls openspec/changes/ 2>/dev/null             # umbrella changes at root
+   \`\`\`
+
+   Otherwise:
+   \`\`\`bash
+   openspec list --json
+   \`\`\`
 
+   Aggregate all results. Use the **AskUserQuestion tool** to let the user select.
+   In workspace mode, show which scope each change belongs to.
    Show only active changes (not already archived).
    Include the schema used for each change if available.
 
@@ -154,8 +170,24 @@ export function getOpsxArchiveCommandTemplate() {
 
 1. **If no change name provided, prompt for selection**
 
-   Run \`openspec list --json\` to get available changes. Use the **AskUserQuestion tool** to let the user select.
+   Check for a workspace manifest:
+   \`\`\`bash
+   cat openspec/workspace.yaml 2>/dev/null
+   \`\`\`
+
+   If workspace.yaml exists, list changes across all scopes:
+   \`\`\`bash
+   (cd <scope.path> && openspec list --json)   # for each scope in workspace.yaml
+   ls openspec/changes/ 2>/dev/null             # umbrella changes at root
+   \`\`\`
+
+   Otherwise:
+   \`\`\`bash
+   openspec list --json
+   \`\`\`
 
+   Aggregate all results. Use the **AskUserQuestion tool** to let the user select.
+   In workspace mode, show which scope each change belongs to.
    Show only active changes (not already archived).
    Include the schema used for each change if available.
 

package/dist/core/templates/workflows/continue-change.js

@@ -10,7 +10,23 @@ export function getContinueChangeSkillTemplate() {
 
 1. **If no change name provided, prompt for selection**
 
-   Run \`openspec list --json\` to get available changes sorted by most recently modified. Then use the **AskUserQuestion tool** to let the user select which change to work on.
+   Check for a workspace manifest:
+   \`\`\`bash
+   cat openspec/workspace.yaml 2>/dev/null
+   \`\`\`
+
+   If workspace.yaml exists, list changes across all scopes:
+   \`\`\`bash
+   (cd <scope.path> && openspec list --json)   # for each scope in workspace.yaml
+   ls openspec/changes/ 2>/dev/null             # umbrella changes at root
+   \`\`\`
+
+   Otherwise:
+   \`\`\`bash
+   openspec list --json
+   \`\`\`
+
+   Aggregate all results sorted by most recently modified. Use the **AskUserQuestion tool** to let the user select which change to work on.
 
    Present the top 3-4 most recently modified changes as options, showing:
    - Change name
@@ -128,7 +144,23 @@ export function getOpsxContinueCommandTemplate() {
 
 1. **If no change name provided, prompt for selection**
 
-   Run \`openspec list --json\` to get available changes sorted by most recently modified. Then use the **AskUserQuestion tool** to let the user select which change to work on.
+   Check for a workspace manifest:
+   \`\`\`bash
+   cat openspec/workspace.yaml 2>/dev/null
+   \`\`\`
+
+   If workspace.yaml exists, list changes across all scopes:
+   \`\`\`bash
+   (cd <scope.path> && openspec list --json)   # for each scope in workspace.yaml
+   ls openspec/changes/ 2>/dev/null             # umbrella changes at root
+   \`\`\`
+
+   Otherwise:
+   \`\`\`bash
+   openspec list --json
+   \`\`\`
+
+   Aggregate all results sorted by most recently modified. Use the **AskUserQuestion tool** to let the user select which change to work on.
 
    Present the top 3-4 most recently modified changes as options, showing:
    - Change name

package/dist/utils/command-references.d.ts

@@ -17,16 +17,17 @@
 export declare function transformToHyphenCommands(text: string): string;
 /**
  * Creates a transformer that replaces bare `openspec` CLI invocations with a custom command.
- * Only replaces command invocations (backtick-quoted or after `&&`), not path references
- * like `openspec/changes/`.
+ * Only replaces command invocations (backtick-quoted, after `&&`, or at line start),
+ * not path references like `openspec/changes/`.
  *
  * @param cli - The CLI command to use instead of bare `openspec`
  * @returns Transformer function, or undefined if cli is not set
  *
  * @example
  * const t = createCliTransformer('pnpm exec openspec');
- * t('`openspec list --json`') // '`pnpm exec openspec list --json`'
- * t('openspec/changes/foo')   // 'openspec/changes/foo' (path unchanged)
+ * t('`openspec list --json`')        // '`pnpm exec openspec list --json`'
+ * t('openspec status --change "x"')  // 'pnpm exec openspec status --change "x"' (line-start)
+ * t('openspec/changes/foo')          // 'openspec/changes/foo' (path unchanged)
  */
 export declare function createCliTransformer(cli: string | undefined): ((text: string) => string) | undefined;
 //# sourceMappingURL=command-references.d.ts.map

package/dist/utils/command-references.js

@@ -19,22 +19,24 @@ export function transformToHyphenCommands(text) {
 }
 /**
  * Creates a transformer that replaces bare `openspec` CLI invocations with a custom command.
- * Only replaces command invocations (backtick-quoted or after `&&`), not path references
- * like `openspec/changes/`.
+ * Only replaces command invocations (backtick-quoted, after `&&`, or at line start),
+ * not path references like `openspec/changes/`.
  *
  * @param cli - The CLI command to use instead of bare `openspec`
  * @returns Transformer function, or undefined if cli is not set
  *
  * @example
  * const t = createCliTransformer('pnpm exec openspec');
- * t('`openspec list --json`') // '`pnpm exec openspec list --json`'
- * t('openspec/changes/foo')   // 'openspec/changes/foo' (path unchanged)
+ * t('`openspec list --json`')        // '`pnpm exec openspec list --json`'
+ * t('openspec status --change "x"')  // 'pnpm exec openspec status --change "x"' (line-start)
+ * t('openspec/changes/foo')          // 'openspec/changes/foo' (path unchanged)
  */
 export function createCliTransformer(cli) {
     if (!cli)
         return undefined;
     return (text) => text
         .replace(/`openspec\s/g, `\`${cli} `)
-        .replace(/&& openspec\s/g, `&& ${cli} `);
+        .replace(/&& openspec\s/g, `&& ${cli} `)
+        .replace(/^(\s*)openspec\s/gm, `$1${cli} `);
 }
 //# sourceMappingURL=command-references.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@exodus/openspec",
-  "version": "1.2.2",
+  "version": "1.2.3",
   "description": "AI-native system for spec-driven development",
   "keywords": [
     "openspec",