superclaude-kiro 1.2.7 → 1.2.8

package/README.md

@@ -1,8 +1,8 @@
-# SuperClaude for Kiro CLI
+# SuperClaude for Kiro
 
-Easy installation of [SuperClaude Framework](https://superclaude.netlify.app/) for Kiro CLI. One command to install, update, or uninstall.
+Easy installation of [SuperClaude Framework](https://superclaude.netlify.app/) for Kiro (CLI and IDE). One command to install, update, or uninstall.
 
-> **Attribution**: This package is an installer for the SuperClaude Framework created by [SuperClaude-Org](https://github.com/SuperClaude-Org/SuperClaude_Framework). All command content and framework design belongs to the original authors. This package simply provides a convenient installation mechanism for Kiro CLI users.
+> **Attribution**: This package is an installer for the SuperClaude Framework created by [SuperClaude-Org](https://github.com/SuperClaude-Org/SuperClaude_Framework). All command content and framework design belongs to the original authors. This package simply provides a convenient installation mechanism for Kiro users.
 
 ## Installation
 
@@ -20,43 +20,62 @@ npx superclaude-kiro install --with-morph
 
 ## Usage
 
-After installation, start Kiro CLI:
+After installation, start Kiro:
 
+**Kiro CLI:**
 ```bash
 kiro-cli chat
 ```
 
-Reference SuperClaude commands using `#sc-*` syntax:
+**Kiro IDE:**
+Open the Kiro IDE and start a chat session.
 
+### Command Syntax
+
+SuperClaude commands use different prefixes depending on your environment:
+
+| Environment | Syntax | Example |
+|-------------|--------|---------|
+| Kiro CLI | `#sc-*` | `#sc-implement Add user auth` |
+| Kiro IDE | `/sc-*` | `/sc-implement Add user auth` |
+
+**CLI Examples:**
 ```
 #sc-implement Add user authentication
 #sc-analyze Review this code for security issues
 #sc-help Show all available commands
 ```
 
+**IDE Examples:**
+```
+/sc-implement Add user authentication
+/sc-analyze Review this code for security issues
+/sc-help Show all available commands
+```
+
 ## Available Commands
 
-| Command | Description |
-|---------|-------------|
-| `#sc-analyze` | Comprehensive code analysis |
-| `#sc-brainstorm` | Interactive requirements discovery |
-| `#sc-build` | Project building with error handling |
-| `#sc-cleanup` | Code cleanup and optimization |
-| `#sc-design` | System and component design |
-| `#sc-document` | Documentation generation |
-| `#sc-estimate` | Development estimates |
-| `#sc-explain` | Code explanations |
-| `#sc-git` | Git operations |
-| `#sc-implement` | Feature implementation |
-| `#sc-improve` | Code improvements |
-| `#sc-index` | Project documentation generation |
-| `#sc-pm` | Project management orchestration |
-| `#sc-research` | Deep web research |
-| `#sc-task` | Complex task execution |
-| `#sc-test` | Test execution |
-| `#sc-troubleshoot` | Issue diagnosis |
-| `#sc-workflow` | Workflow generation |
-| `#sc-help` | Show all commands and flags |
+| Command | CLI Syntax | IDE Syntax | Description |
+|---------|------------|------------|-------------|
+| analyze | `#sc-analyze` | `/sc-analyze` | Comprehensive code analysis |
+| brainstorm | `#sc-brainstorm` | `/sc-brainstorm` | Interactive requirements discovery |
+| build | `#sc-build` | `/sc-build` | Project building with error handling |
+| cleanup | `#sc-cleanup` | `/sc-cleanup` | Code cleanup and optimization |
+| design | `#sc-design` | `/sc-design` | System and component design |
+| document | `#sc-document` | `/sc-document` | Documentation generation |
+| estimate | `#sc-estimate` | `/sc-estimate` | Development estimates |
+| explain | `#sc-explain` | `/sc-explain` | Code explanations |
+| git | `#sc-git` | `/sc-git` | Git operations |
+| implement | `#sc-implement` | `/sc-implement` | Feature implementation |
+| improve | `#sc-improve` | `/sc-improve` | Code improvements |
+| index | `#sc-index` | `/sc-index` | Project documentation generation |
+| pm | `#sc-pm` | `/sc-pm` | Project management orchestration |
+| research | `#sc-research` | `/sc-research` | Deep web research |
+| task | `#sc-task` | `/sc-task` | Complex task execution |
+| test | `#sc-test` | `/sc-test` | Test execution |
+| troubleshoot | `#sc-troubleshoot` | `/sc-troubleshoot` | Issue diagnosis |
+| workflow | `#sc-workflow` | `/sc-workflow` | Workflow generation |
+| help | `#sc-help` | `/sc-help` | Show all commands and flags |
 
 ## CLI Commands
 
@@ -141,7 +160,7 @@ All agents are configured with:
 - `"allowedTools": ["*", "use_subagent", "@context7", "@playwright", "@sequential-thinking", "@serena", "@morphllm-fast-apply/edit_file"]` - All built-in tools, subagents, and MCP tools pre-approved
 - `"toolsSettings"` - Shell and write operations auto-allowed
 - `"useLegacyMcpJson": true` - Uses global MCP servers
-- `"model": "claude-opus-4.5"` - Uses Claude Opus 4.5 by default (subagents inherit this when spawned with superclaude agent)
+- `"model": "claude-opus-4.6"` - Uses Claude Opus 4.6 by default (subagents inherit this when spawned with superclaude agent)
 
 **Note**: No default model is set - Kiro CLI remembers your model choice.
 
@@ -269,7 +288,7 @@ npx superclaude-kiro install --force
 - **SuperClaude GitHub**: https://github.com/SuperClaude-Org/SuperClaude_Framework
 - **Kiro CLI Documentation**: https://kiro.dev/docs/cli/
 
-This installer package was created to simplify SuperClaude deployment for Kiro CLI users. All credit for the SuperClaude framework, commands, and methodology goes to the original creators.
+This installer package was created to simplify SuperClaude deployment for Kiro users. All credit for the SuperClaude framework, commands, and methodology goes to the original creators.
 
 ## License
 

package/dist/agents/sc-analyze.json

@@ -28,5 +28,5 @@
     }
   },
   "useLegacyMcpJson": true,
-  "model": "claude-opus-4.5"
+  "model": "claude-opus-4.6"
 }

package/dist/agents/sc-implement.json

@@ -28,5 +28,5 @@
     }
   },
   "useLegacyMcpJson": true,
-  "model": "claude-opus-4.5"
+  "model": "claude-opus-4.6"
 }

package/dist/agents/sc-pm.json

@@ -28,5 +28,5 @@
     }
   },
   "useLegacyMcpJson": true,
-  "model": "claude-opus-4.5"
+  "model": "claude-opus-4.6"
 }

package/dist/agents/superclaude.json

@@ -28,5 +28,5 @@
     }
   },
   "useLegacyMcpJson": true,
-  "model": "claude-opus-4.5"
+  "model": "claude-opus-4.6"
 }

package/dist/steering/superclaude/sc-analyze.md

@@ -86,4 +86,13 @@ Key behaviors:
 **Will Not:**
 - Execute dynamic analysis requiring code compilation or runtime
 - Modify source code or apply fixes without explicit user consent
-- Analyze external dependencies beyond import and usage patterns
+- Analyze external dependencies beyond import and usage patterns
+
+**Output**: Analysis report containing:
+- Severity-rated findings
+- Code quality metrics
+- Security vulnerabilities
+- Performance issues
+- Recommendations
+
+**Next Step**: After review, use `/sc:improve` to apply recommended fixes or `/sc:cleanup` for dead code removal.

package/dist/steering/superclaude/sc-brainstorm.md

@@ -97,4 +97,26 @@ Key behaviors:
 **Will Not:**
 - Make implementation decisions without proper requirements discovery
 - Override user vision with prescriptive solutions during exploration phase
-- Bypass systematic exploration for complex multi-domain projects
+- Bypass systematic exploration for complex multi-domain projects
+
+## CRITICAL BOUNDARIES
+
+**STOP AFTER REQUIREMENTS DISCOVERY**
+
+This command produces a REQUIREMENTS SPECIFICATION ONLY.
+
+**Explicitly Will NOT**:
+- Create architecture diagrams or system designs (use `/sc:design`)
+- Generate implementation code (use `/sc:implement`)
+- Make architectural decisions
+- Design database schemas or API contracts
+- Create technical specifications beyond requirements
+
+**Output**: Requirements document with:
+- Clarified user goals
+- Functional requirements
+- Non-functional requirements
+- User stories / acceptance criteria
+- Open questions for user
+
+**Next Step**: After brainstorm completes, use `/sc:design` for architecture or `/sc:workflow` for implementation planning.

package/dist/steering/superclaude/sc-business-panel.md

@@ -87,4 +87,36 @@ Question-driven exploration for deep learning and strategic thinking development
 ## Integration Notes
 - Compatible with all thinking flags (--think, --think-hard, --ultrathink)
 - Supports wave orchestration for comprehensive business analysis
-- Integrates with scribe persona for professional business communication
+- Integrates with scribe persona for professional business communication
+
+## CRITICAL BOUNDARIES
+
+**SYNTHESIS OUTPUT ONLY - NOT IMPLEMENTATION**
+
+This command produces EXPERT ANALYSIS and RECOMMENDATIONS only.
+
+**Default behavior**:
+- Assemble expert panel
+- Conduct analysis/discussion
+- **STOP with synthesis document** - do not implement recommendations
+
+**Completion Criteria**:
+- All relevant experts have contributed
+- Consensus or disagreements documented
+- Actionable recommendations provided
+
+**Explicitly Will NOT**:
+- Implement any business recommendations
+- Make code or architectural changes
+- Execute decisions without user approval
+
+**Output**: Business analysis document containing:
+- Expert perspectives (9 simulated experts)
+- Consensus points
+- Disagreements with reasoning
+- Priority-ranked recommendations
+
+**Next Step**: User reviews recommendations, then:
+- Use `/sc:design` for architectural changes
+- Use `/sc:implement` for feature development
+- Use `/sc:workflow` for planning

package/dist/steering/superclaude/sc-cleanup.md

@@ -90,4 +90,23 @@ Key behaviors:
 **Will Not:**
 - Remove code without thorough safety analysis and validation
 - Override project-specific cleanup exclusions or architectural constraints
-- Apply cleanup operations that compromise functionality or introduce bugs
+- Apply cleanup operations that compromise functionality or introduce bugs
+
+## AUTO-FIX VS APPROVAL-REQUIRED
+
+**Auto-fix (applies automatically)**:
+- Unused imports removal
+- Dead code with zero references
+- Empty blocks removal
+- Redundant type annotations
+
+**Approval Required (prompts user first)**:
+- Code with indirect references
+- Exports potentially used externally
+- Test fixtures/utilities
+- Configuration values
+
+**Safety Threshold**:
+- If code has ANY usage path, prompt user
+- If code affects public API, prompt user
+- If unsure, prompt user

package/dist/steering/superclaude/sc-design.md

@@ -85,4 +85,12 @@ Key behaviors:
 **Will Not:**
 - Generate actual implementation code (use /sc:implement for implementation)
 - Modify existing system architecture without explicit design approval
-- Create designs that violate established architectural constraints
+- Create designs that violate established architectural constraints
+
+**Output**: Architecture documents containing:
+- System diagrams (component, sequence, data flow)
+- API specifications
+- Database schemas
+- Interface definitions
+
+**Next Step**: After design is approved, use `/sc:implement` to build the designed components.

package/dist/steering/superclaude/sc-estimate.md

@@ -83,4 +83,25 @@ Key behaviors:
 **Will Not:**
 - Guarantee estimate accuracy without proper scope analysis and validation
 - Provide estimates without appropriate domain expertise and complexity assessment
-- Override historical benchmarks without clear justification and analysis
+- Override historical benchmarks without clear justification and analysis
+
+## CRITICAL BOUNDARIES
+
+**STOP AFTER ESTIMATION**
+
+This command produces an ESTIMATION REPORT ONLY - no implementation.
+
+**Explicitly Will NOT**:
+- Execute work based on estimates
+- Create implementation timelines for execution
+- Start implementation tasks
+- Make commitments on behalf of user
+
+**Output**: Estimation report containing:
+- Time/effort breakdown
+- Complexity analysis
+- Confidence intervals
+- Risk assessment
+- Resource requirements
+
+**Next Step**: After estimation, user decides on timeline. Use `/sc:workflow` for planning or `/sc:implement` for execution.

package/dist/steering/superclaude/sc-implement.md

@@ -94,4 +94,18 @@ Key behaviors:
 **Will Not:**
 - Make architectural decisions without appropriate persona consultation
 - Implement features conflicting with security policies or architectural constraints
-- Override user-specified safety constraints or bypass quality gates
+- Override user-specified safety constraints or bypass quality gates
+
+## COMPLETION CRITERIA
+
+**Implementation is DONE when**:
+- Feature code is written and compiles
+- Basic functionality verified
+- Files saved and ready for testing
+
+**Post-Implementation Checklist**:
+1. Code compiles without errors
+2. Basic functionality works
+3. Ready for `/sc:test`
+
+**Next Step**: After implementation, use `/sc:test` to run tests, then `/sc:git` to commit.

package/dist/steering/superclaude/sc-improve.md

@@ -90,4 +90,24 @@ Key behaviors:
 **Will Not:**
 - Apply risky improvements without proper analysis and user confirmation
 - Make architectural changes without understanding full system impact
-- Override established coding standards or project-specific conventions
+- Override established coding standards or project-specific conventions
+
+## AUTO-FIX VS APPROVAL-REQUIRED
+
+**Auto-fix (applies automatically)**:
+- Style fixes (formatting, naming conventions)
+- Unused variable removal
+- Import organization
+- Simple type annotations
+
+**Approval Required (prompts user first)**:
+- Architectural changes
+- Logic refactoring
+- Function signature changes
+- Removing code used by public APIs
+- Changes affecting multiple files
+
+**Explicitly Will NOT** (without `--force` flag):
+- Make architectural decisions
+- Refactor code structure without confirmation
+- Remove functionality

package/dist/steering/superclaude/sc-research.md

@@ -100,4 +100,24 @@ inclusion: manual
 
 ## Boundaries
 **Will**: Current information, intelligent search, evidence-based analysis
-**Won't**: Make claims without sources, skip validation, access restricted content
+**Won't**: Make claims without sources, skip validation, access restricted content
+
+## CRITICAL BOUNDARIES
+
+**STOP AFTER RESEARCH REPORT**
+
+This command produces a RESEARCH REPORT ONLY - no implementation.
+
+**Explicitly Will NOT**:
+- Implement findings or recommendations
+- Write code based on research
+- Make architectural decisions
+- Create system changes based on research
+
+**Output**: Research report (`claudedocs/research_*.md`) containing:
+- Findings with sources
+- Evidence-based analysis
+- Recommendations (for human decision)
+- Cited references
+
+**Next Step**: After research completes, user decides next action. Use `/sc:design` for architecture or `/sc:implement` for coding.

package/dist/steering/superclaude/sc-spawn.md

@@ -82,4 +82,24 @@ Key behaviors:
 **Will Not:**
 - Replace domain-specific commands for simple operations
 - Override user coordination preferences or execution strategies
-- Execute operations without proper dependency analysis and validation
+- Execute operations without proper dependency analysis and validation
+
+## CRITICAL BOUNDARIES
+
+**STOP AFTER TASK DECOMPOSITION**
+
+This command produces a TASK HIERARCHY ONLY - delegates execution to other commands.
+
+**Explicitly Will NOT**:
+- Execute implementation tasks directly
+- Write or modify code
+- Create system changes
+- Replace domain-specific commands
+
+**Output**: Task breakdown document with:
+- Epic decomposition
+- Task hierarchy with dependencies
+- Delegation assignments (which `/sc:*` command handles each task)
+- Coordination strategy
+
+**Next Step**: Execute individual tasks using delegated commands (`/sc:implement`, `/sc:design`, `/sc:test`, etc.)

package/dist/steering/superclaude/sc-spec-panel.md

@@ -425,4 +425,12 @@ Comprehensive analysis with full expert commentary, examples, and implementation
 - Replace human judgment and domain expertise in critical decisions
 - Modify specifications without explicit user consent and validation
 - Generate specifications from scratch without existing content or context
-- Provide legal or regulatory compliance guarantees beyond analysis guidance
+- Provide legal or regulatory compliance guarantees beyond analysis guidance
+
+**Output**: Expert review document containing:
+- Multi-expert analysis (10 simulated experts)
+- Specific, actionable recommendations
+- Consensus points and disagreements
+- Priority-ranked improvements
+
+**Next Step**: After review, incorporate feedback into spec, then use `/sc:design` for architecture or `/sc:implement` for coding.

package/dist/steering/superclaude/sc-task.md

@@ -86,4 +86,31 @@ Key behaviors:
 **Will Not:**
 - Execute simple tasks that don't require advanced orchestration
 - Compromise quality standards for speed or convenience
-- Operate without proper validation and quality gates
+- Operate without proper validation and quality gates
+
+## CRITICAL BOUNDARIES
+
+**USER-INVOKED DISCRETE TASK EXECUTION**
+
+This command executes specific tasks when explicitly invoked by user.
+
+**Difference from /sc:pm**:
+- `/sc:pm` = session-level orchestration (background monitoring, continuous)
+- `/sc:task` = user-invoked discrete execution (explicit start/end)
+
+**Behavior**:
+- User invokes `/sc:task [description]`
+- Execute the specific task using multi-agent coordination
+- **STOP when task is complete** - do not continue to next tasks without user input
+
+**Completion Criteria**:
+- Task objective achieved
+- All sub-tasks marked completed in TodoWrite
+- Validation passed
+
+**Output**: Task completion report with:
+- What was accomplished
+- Files modified
+- Tests status (if applicable)
+
+**Next Step**: User decides next action. May invoke another `/sc:task` or use specific commands.

package/dist/steering/superclaude/sc-troubleshoot.md

@@ -85,4 +85,36 @@ Key behaviors:
 **Will Not:**
 - Apply risky fixes without proper analysis and user confirmation
 - Modify production systems without explicit permission and safety validation
-- Make architectural changes without understanding full system impact
+- Make architectural changes without understanding full system impact
+
+## CRITICAL BOUNDARIES
+
+**DIAGNOSE FIRST - FIXES REQUIRE `--fix` FLAG**
+
+This command is DIAGNOSIS-FIRST by default.
+
+**Default behavior (no `--fix` flag)**:
+- Diagnose the issue
+- Identify root cause
+- Propose solution options
+- **STOP and present findings to user** - do not apply any fixes
+
+**With `--fix` flag**:
+- After diagnosis, prompt user for confirmation before applying
+- Apply fix only after user explicitly approves
+- Verify fix with tests
+
+**Explicitly Will NOT** (without `--fix` flag):
+- Apply any code changes
+- Modify any files
+- Execute fixes automatically
+
+**Output**: Diagnostic report containing:
+- Issue description
+- Root cause analysis
+- Proposed solutions (ranked)
+- Risk assessment for each solution
+
+**Next Step**: User reviews diagnosis, then either:
+- Re-run with `--fix` flag to apply recommended fix
+- Use `/sc:improve` for broader refactoring

package/dist/steering/superclaude/sc-workflow.md

@@ -94,4 +94,25 @@ Key behaviors:
 **Will Not:**
 - Execute actual implementation tasks beyond workflow planning and strategy
 - Override established development processes without proper analysis and validation
-- Generate workflows without comprehensive requirement analysis and dependency mapping
+- Generate workflows without comprehensive requirement analysis and dependency mapping
+
+## CRITICAL BOUNDARIES
+
+**STOP AFTER PLAN CREATION**
+
+This command produces an IMPLEMENTATION PLAN ONLY - no code execution.
+
+**Explicitly Will NOT**:
+- Execute any implementation tasks
+- Write or modify code
+- Create files (except the workflow plan document)
+- Make architectural changes
+- Run builds or tests
+
+**Output**: Workflow plan document (`claudedocs/workflow_*.md`) containing:
+- Implementation phases
+- Task dependencies
+- Execution order
+- Checkpoints and validation steps
+
+**Next Step**: After workflow completes, use `/sc:implement` to execute the plan step by step.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "superclaude-kiro",
-  "version": "1.2.7",
-  "description": "SuperClaude Framework for Kiro CLI - Easy installation for teams",
+  "version": "1.2.8",
+  "description": "SuperClaude Framework for Kiro (CLI and IDE) - Easy installation for teams",
   "type": "module",
   "bin": {
     "superclaude-kiro": "./bin/superclaude-kiro.js"

package/src/mcp-servers.js

@@ -102,7 +102,7 @@ export const MCP_SERVERS = {
     config: {
       command: 'npx',
       args: ['-y', '@morphllm/morphmcp'],
-      autoApprove: ['edit_file']
+      autoApprove: ['edit_file', 'warpgrep_codebase_search']
     }
   }
 };