@tdsoft-tech/aikit 0.1.15 → 0.1.16

package/dist/cli.js

@@ -2361,9 +2361,7 @@ var DEFAULT_COMMANDS = [
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user has provided the task description with this command. Use it directly - do NOT ask the user for a task description!
-- The arguments contain the task description you should create
+Task description: $ARGUMENTS
 
 1. Create a new bead file with unique ID
 2. Add task description, status, and notes
@@ -2385,9 +2383,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user has provided
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user has provided the feature or task to plan. Use it directly - do NOT ask the user what to plan!
-- The arguments contain the feature/task description you should create a plan for
+Feature or task to plan: $ARGUMENTS
 
 1. UNDERSTAND: Clarify requirements through Socratic questioning
 2. RESEARCH: Check existing patterns and dependencies
@@ -2429,9 +2425,7 @@ Brief description of the goal.
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user has provided the task reference or description. Use it directly - do NOT ask the user which task to implement!
-- The arguments contain the task reference (e.g., task-001) or task description to implement
+Task reference or description: $ARGUMENTS
 
 1. LOAD: Get task details from .beads/ or plan
 2. TEST: Write failing tests first (RED)
@@ -2530,9 +2524,7 @@ Before marking complete:
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user has provided the task description. Use it directly - do NOT ask the user what task to perform!
-- The arguments contain the task description to execute
+Task description: $ARGUMENTS
 
 **Phase 1: Requirements Gathering**
 - Interactive selection of task type (Feature, Bug Fix, Refactoring, etc.)
@@ -2622,9 +2614,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user has provided
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user has provided the issue description. Use it directly - do NOT ask user what to fix!
-- The arguments contain the issue description you should fix
+Issue description: $ARGUMENTS
 
 1. Identify issue
 2. Make minimal change to fix
@@ -2641,10 +2631,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user has provided
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user has provided optional file argument. Use it if provided!
-- If a file argument is provided, focus on fixing types in that specific file
-- If no file argument is provided, fix all type errors in the project
+Optional file argument: $ARGUMENTS
 
 1. Run \`npm run typecheck\`
 2. Parse error output
@@ -2679,10 +2666,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user has provided
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user may have provided a commit message. Use it if provided!
-- If a commit message is provided, use that message directly
-- If no message is provided, generate a conventional commit message based on changes
+Optional commit message: $ARGUMENTS
 
 1. Stage changes: \`git add -A\`
 2. Generate commit message following conventional commits:
@@ -2704,10 +2688,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user may have pro
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user may have provided a PR title. Use it if provided!
-- If a title is provided, use that as the PR title
-- If no title is provided, generate a title based on changes
+Optional PR title: $ARGUMENTS
 
 1. Push current branch
 2. Generate PR description:
@@ -2728,9 +2709,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user may have pro
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user has provided the research topic. Use it directly - do NOT ask user what to research!
-- The arguments contain the topic you should research
+Research topic: $ARGUMENTS
 
 1. Search documentation and resources
 2. Find code examples and patterns
@@ -2770,10 +2749,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user has provided
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user may have provided a path. Use it if provided!
-- If a path is provided, review code in that specific directory
-- If no path is provided, review the entire codebase
+Optional path: $ARGUMENTS
 
 1. Check code quality metrics
 2. Identify:
@@ -2795,9 +2771,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user may have pro
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user has provided the feature to design. Use it directly - do NOT ask user what to design!
-- The arguments contain the feature you should design
+Feature to design: $ARGUMENTS
 
 1. Requirements gathering (Socratic questioning)
 2. Research existing solutions
@@ -2821,9 +2795,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user has provided
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user has provided a problem. Use it directly - do NOT ask the user what to brainstorm about!
-- The arguments contain the problem you should brainstorm ideas for
+Problem to brainstorm: $ARGUMENTS
 
 1. Define problem clearly
 2. Generate diverse ideas (no judgement)
@@ -2842,9 +2814,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user has provided
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user has provided the branch name. Use it directly - do NOT ask user what to name the branch!
-- The arguments contain the branch name to create
+Branch name: $ARGUMENTS
 
 1. Ensure clean working directory
 2. Pull latest main/master
@@ -2865,10 +2835,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user has provided
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user may have provided a target branch. Use it if provided!
-- If a target branch is provided, merge to that branch
-- If no target is provided, default to merging to main/master
+Optional target branch: $ARGUMENTS
 
 1. Run quality gates first
 2. Commit any pending changes
@@ -3061,10 +3028,7 @@ The analysis will be saved automatically for later reference.`
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user has provided optional file or pattern argument. Use it if provided!
-- If a file/pattern argument is provided, focus refactoring on that specific target
-- If no argument is provided, identify refactoring opportunities across the codebase
+Optional file or pattern: $ARGUMENTS
 
 1. Ensure tests are in place
 2. Identify refactoring opportunities
@@ -3082,10 +3046,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user has provided
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user has provided optional pattern argument. Use it if provided!
-- If a pattern argument is provided, run tests matching that pattern
-- If no argument is provided, run the full test suite
+Optional pattern: $ARGUMENTS
 
 1. Run test command: \`npm run test\`
 2. Parse and display results
@@ -3103,10 +3064,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user has provided
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user may have provided --fix flag. Check for it!
-- If --fix flag is provided, automatically fix issues
-- If no --fix flag is provided, only report issues without fixing
+Optional flags: $ARGUMENTS
 
 1. Run linter: \`npm run lint\`
 2. Parse errors and warnings
@@ -3124,10 +3082,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user may have pro
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user may have provided an environment. Use it if provided!
-- If an environment is provided, deploy to that environment
-- If no environment is provided, default to production or prompt user
+Optional environment: $ARGUMENTS
 
 1. Run quality gates (test, lint, build)
 2. Check for uncommitted changes
@@ -3145,10 +3100,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user may have pro
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user may have provided a version. Use it if provided!
-- If a version is provided, rollback to that specific version
-- If no version is provided, list available versions and prompt user
+Optional version: $ARGUMENTS
 
 1. Identify current version
 2. List available versions
@@ -3166,11 +3118,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user may have pro
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user may have provided flags. Check for them!
-- If --tail N is provided, show only the last N lines
-- If --follow is provided, stream live log updates
-- If no flags are provided, show standard log output
+Optional flags: $ARGUMENTS
 
 1. Determine log location
 2. Apply filters if specified
@@ -3277,6 +3225,11 @@ Describe what this command does.
    * Format command for agent consumption
    */
   formatForAgent(command, args) {
+    let content = command.content;
+    if (args && args.trim()) {
+      const argParts = args.trim().split(/\s+/);
+      content = content.replace(/\$ARGUMENTS/g, args.trim()).replace(/\$1/g, argParts[0] || "").replace(/\$2/g, argParts[1] || "").replace(/\$3/g, argParts[2] || "").replace(/\$4/g, argParts[3] || "").replace(/\$5/g, argParts[4] || "");
+    }
     let output = `# Command: /${command.name}
 
 ## Usage
@@ -3289,14 +3242,11 @@ ${command.description}
 ${command.examples.map((e) => `- \`${e}\``).join("\n")}
 
 ## Workflow
-${command.content}
+${content}
 `;
     if (args && args.trim()) {
       output += `
-## Arguments Provided
-\`${args}\`
-
-**IMPORTANT**: The user provided these arguments with the command. Use them in the workflow as needed.
+User arguments are : ${args.trim()}
 `;
     }
     return output;