prompt-language-shell 0.9.6 → 1.0.0

package/dist/skills/execute.md

@@ -100,14 +100,28 @@ position.
 
 ### How to Generate Commands from Skills
 
+**CRITICAL - ONE TASK = ONE COMMAND**: Each input task maps to exactly
+ONE command in your response. The task's action tells you WHICH specific
+step from the skill to use. Do NOT expand an entire skill workflow for
+a single task - only generate the command for that specific step.
+
 1. **Identify skill tasks**: Check if tasks have params.skill
 2. **Find the skill**: Look up the skill in "Available Skills" section
    below (REQUIRED - must exist)
-3. **Match tasks to Execution**: Each task action came from a Steps line;
-   use the corresponding Execution line for the command
-4. **Substitute parameters**: Replace {PARAM} placeholders with actual
+3. **Match task action to skill step**: The task action describes which
+   step from the skill's Steps section this task represents. Find the
+   matching step by semantic meaning (e.g., "Export results" matches
+   "Export the results to {FORMAT}", NOT all three steps of the skill)
+4. **Use corresponding Execution line**: Once you identify which step
+   the task represents, use ONLY that step's corresponding Execution line
+5. **Substitute parameters**: Replace {PARAM} placeholders with actual
    values from task params
 
+**IMPORTANT**: If the schedule contains separate tasks for different
+steps of the same skill (e.g., one task for fetching data, another for
+exporting), each task produces its own single command. Do NOT combine
+them or add steps that weren't scheduled.
+
 ### Example Skill
 
 ```markdown
@@ -151,6 +165,28 @@ steps 1 and 3 (with step 2 skipped), use Execution lines 1 and 3
 which Execution line to use - always match by original position, never
 by sequential task index.
 
+### Expanding Skill References in Execution Lines
+
+Execution lines may contain **skill references** in the format
+`[ Skill Name ]`. These are references to other skills that must be
+expanded to actual commands before execution.
+
+**Format**: `[ Skill Name ]` with spaces inside the brackets
+
+**How to expand**:
+1. When an Execution line contains `[ Skill Name ]`, look up that skill
+   in the "Available Skills" section
+2. Get the referenced skill's Execution command
+3. Replace the `[ Skill Name ]` reference with the actual command
+
+**IMPORTANT**: Skill references are the ONLY exception to the verbatim
+execution rule below. You MUST expand them - never output `[ ... ]`
+syntax in the final command.
+
+**Note**: Use the `skill:` field from task metadata to find the skill
+definition. If that skill's Execution line contains `[ Other Skill ]`,
+look up "Other Skill" and replace the reference with its command.
+
 **CRITICAL - VERBATIM EXECUTION**: Run shell commands EXACTLY as written in
 the ### Execution section. Do NOT:
 - Modify the command string in any way
@@ -371,6 +407,41 @@ commands:
     command: "df -h"
 ```
 
+### Example 8: Partial skill execution (specific steps only)
+
+When the schedule breaks a multi-step skill into separate tasks, each
+task produces exactly ONE command for its specific step:
+
+Skill "Prepare Report" has 3 steps:
+- Steps: Fetch source data | Transform data | Export results
+- Execution: curl {url} | python3 process.py | cat output.csv
+
+Tasks (schedule requested only steps 1 and 3, skipping transform):
+- { action: "Fetch source data", params: { skill: "Prepare Report" } }
+- { action: "Export results", params: { skill: "Prepare Report" } }
+
+Response (2 tasks = 2 commands, NOT 3):
+```
+message: "Prepare report:"
+summary: "Report prepared"
+commands:
+  - description: "Fetch source data"
+    command: "curl {url}"
+  - description: "Export results"
+    command: "cat output.csv"
+```
+
+**WRONG** response (adding unscheduled transform step):
+```
+commands:
+  - description: "Fetch source data"
+    command: "curl {url}"
+  - description: "Transform data"       ← NOT IN SCHEDULE - DO NOT ADD
+    command: "python3 process.py"
+  - description: "Export results"
+    command: "cat output.csv"
+```
+
 ## Handling Complex Operations
 
 For complex multi-step operations:
@@ -420,6 +491,10 @@ Example:
 - **CRITICAL: Assume what commands to run when skill is missing**
 - **CRITICAL: Replace unknown placeholders with `<UNKNOWN>` - this breaks
   shell syntax**
+- **CRITICAL: Add steps that weren't in the scheduled tasks** - if the
+  schedule has 2 tasks, you MUST return exactly 2 commands
+- **CRITICAL: Expand entire skill workflows** when only specific steps
+  were scheduled - match task actions to individual skill steps
 
 **DO:**
 - Match commands precisely to task descriptions
@@ -434,6 +509,10 @@ Example:
   commands**
 - Always use skill's Execution section when params.skill is present
 - Replace all {PARAM} placeholders with values from task params
+- **CRITICAL: Count input tasks and ensure output has same count** -
+  N tasks in = N commands out, no exceptions
+- **CRITICAL: Match each task action to its specific skill step** -
+  use only that step's Execution line for the command
 
 ## Final Validation
 

package/dist/skills/schedule.md

@@ -129,6 +129,13 @@ Before creating tasks, evaluate the request type:
      capabilities", "show skills"
    - Example: "flex" → introspect type
 
+   **CRITICAL - Introspection is ALWAYS a single task:**
+   - Introspection requests MUST result in exactly ONE introspect leaf task
+   - NEVER create multiple introspect tasks for a single request
+   - NEVER nest introspect tasks within groups
+   - NEVER break down capabilities into separate introspect tasks
+   - The single introspect task will list ALL capabilities
+
 2. **Information requests** (questions) - Use question keywords:
    - "explain", "describe", "tell me", "what is", "how does", "find",
      "search"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "prompt-language-shell",
-  "version": "0.9.6",
+  "version": "1.0.0",
   "description": "Your personal command-line concierge. Ask politely, and it gets things done.",
   "type": "module",
   "main": "dist/index.js",
@@ -17,9 +17,10 @@
     "dev": "npm run build && tsc --watch",
     "prepare": "husky",
     "prepublishOnly": "npm run check",
-    "test": "vitest run --exclude 'tests/tools/schedule/*.test.tsx'",
-    "test:watch": "vitest --exclude 'tests/tools/schedule/*.test.tsx'",
+    "test": "vitest run --exclude 'tests/tools/' --exclude 'tests/shell/'",
+    "test:watch": "vitest --exclude 'tests/tools/' --exclude 'tests/shell/'",
     "test:llm": "vitest run tests/tools/schedule/*.test.tsx",
+    "test:shell": "vitest run tests/shell/*.test.ts",
     "format": "prettier --write '**/*.{ts,tsx}'",
     "format:check": "prettier --check '**/*.{ts,tsx}'",
     "lint": "eslint .",
@@ -52,18 +53,18 @@
     "ink-text-input": "^6.0.0",
     "react": "^19.2.3",
     "yaml": "^2.8.2",
-    "zod": "^4.2.1"
+    "zod": "^4.3.6"
   },
   "devDependencies": {
-    "@types/node": "^25.0.3",
-    "@types/react": "^19.2.7",
-    "@vitest/coverage-v8": "^4.0.16",
+    "@types/node": "^25.0.10",
+    "@types/react": "^19.2.9",
+    "@vitest/coverage-v8": "^4.0.18",
     "eslint": "^9.39.2",
     "husky": "^9.1.7",
     "ink-testing-library": "^4.0.0",
-    "prettier": "^3.7.4",
+    "prettier": "^3.8.1",
     "typescript": "^5.9.3",
-    "typescript-eslint": "^8.50.1",
-    "vitest": "^4.0.16"
+    "typescript-eslint": "^8.53.1",
+    "vitest": "^4.0.18"
   }
 }