scene-capability-engine 3.0.1 → 3.0.3

package/docs/spec-collaboration-guide.md

@@ -2,7 +2,7 @@
 
 ## Overview
 
-The Spec-level collaboration system enables multiple AI instances (Kiro) to work on different Specs in parallel within a large project. This guide explains how to use the collaboration features to coordinate parallel development efforts.
+The Spec-level collaboration system enables multiple AI instances (SCE) to work on different Specs in parallel within a large project. This guide explains how to use the collaboration features to coordinate parallel development efforts.
 
 ## Key Concepts
 
@@ -23,9 +23,9 @@ Specs can depend on other Specs in three ways:
 
 Interface contracts formally define the APIs, data structures, and behaviors that a Spec provides or consumes. They ensure compatibility between independently developed Specs.
 
-### Kiro Instances
+### SCE Instances
 
-A Kiro instance is an AI assistant working on a specific Spec. You can assign Specs to different instances to enable parallel development.
+A SCE instance is an AI assistant working on a specific Spec. You can assign Specs to different instances to enable parallel development.
 
 ## Quick Start
 
@@ -34,7 +34,7 @@ A Kiro instance is an AI assistant working on a specific Spec. You can assign Sp
 Create a Master Spec with Sub-Specs:
 
 ```bash
-kse collab init user-management \
+sce collab init user-management \
   --sub-specs user-service auth-service session-manager \
   --dependencies "auth-service:user-service" \
   --dependencies "session-manager:auth-service"
@@ -50,23 +50,23 @@ This creates:
 View all Specs and their status:
 
 ```bash
-kse collab status
+sce collab status
 ```
 
 View dependency graph:
 
 ```bash
-kse collab status --graph
+sce collab status --graph
 ```
 
-### 3. Assign Specs to Kiro Instances
+### 3. Assign Specs to SCE Instances
 
 Assign Specs to different AI instances:
 
 ```bash
-kse collab assign user-service kiro-1
-kse collab assign auth-service kiro-2
-kse collab assign session-manager kiro-3
+sce collab assign user-service SCE-1
+sce collab assign auth-service SCE-2
+sce collab assign session-manager SCE-3
 ```
 
 ### 4. Define Interface Contracts
@@ -115,7 +115,7 @@ Create an interface contract for a Spec (in `.kiro/specs/{spec-name}/interfaces/
 Verify that implementations match contracts:
 
 ```bash
-kse collab verify user-service
+sce collab verify user-service
 ```
 
 ### 6. Run Integration Tests
@@ -123,7 +123,7 @@ kse collab verify user-service
 Run integration tests across multiple Specs:
 
 ```bash
-kse collab integrate user-service auth-service session-manager
+sce collab integrate user-service auth-service session-manager
 ```
 
 ## Workflow Example
@@ -133,7 +133,7 @@ kse collab integrate user-service auth-service session-manager
 **Step 1: Architect creates Master Spec**
 
 ```bash
-kse collab init user-management \
+sce collab init user-management \
   --sub-specs database-layer user-service auth-service notification-service \
   --dependencies "user-service:database-layer" \
   --dependencies "auth-service:user-service" \
@@ -143,7 +143,7 @@ kse collab init user-management \
 **Step 2: Check which Specs are ready**
 
 ```bash
-kse collab status
+sce collab status
 ```
 
 Output:
@@ -163,79 +163,79 @@ Ready to start: database-layer
 **Step 3: Assign and start development**
 
 ```bash
-kse collab assign database-layer kiro-1
-kse collab assign user-service kiro-2
-kse collab assign auth-service kiro-3
+sce collab assign database-layer SCE-1
+sce collab assign user-service SCE-2
+sce collab assign auth-service SCE-3
 ```
 
 **Step 4: Define interfaces**
 
-Each Kiro instance defines the interface contract for their Spec.
+Each SCE instance defines the interface contract for their Spec.
 
 **Step 5: Verify and integrate**
 
 ```bash
-kse collab verify database-layer
-kse collab verify user-service
-kse collab integrate database-layer user-service
+sce collab verify database-layer
+sce collab verify user-service
+sce collab integrate database-layer user-service
 ```
 
 ## Commands Reference
 
-### `kse collab init`
+### `sce collab init`
 
 Initialize a Master Spec with Sub-Specs.
 
 ```bash
-kse collab init <master-spec> [options]
+sce collab init <master-spec> [options]
 ```
 
 Options:
 - `-s, --sub-specs <specs...>`: Sub-spec names
 - `-d, --dependencies <deps...>`: Dependencies in format "spec:dep1,dep2"
 
-### `kse collab status`
+### `sce collab status`
 
 Display collaboration status.
 
 ```bash
-kse collab status [spec-name] [options]
+sce collab status [spec-name] [options]
 ```
 
 Options:
 - `-g, --graph`: Show dependency graph
 - `--critical-path`: Highlight critical path in graph
 
-### `kse collab assign`
+### `sce collab assign`
 
-Assign a Spec to a Kiro instance.
+Assign a Spec to a SCE instance.
 
 ```bash
-kse collab assign <spec-name> <kiro-instance>
+sce collab assign <spec-name> <SCE-instance>
 ```
 
-### `kse collab verify`
+### `sce collab verify`
 
 Verify interface contracts for a Spec.
 
 ```bash
-kse collab verify <spec-name>
+sce collab verify <spec-name>
 ```
 
-### `kse collab integrate`
+### `sce collab integrate`
 
 Run integration tests across Specs.
 
 ```bash
-kse collab integrate <spec-names...>
+sce collab integrate <spec-names...>
 ```
 
-### `kse collab migrate`
+### `sce collab migrate`
 
 Convert a standalone Spec to collaborative mode.
 
 ```bash
-kse collab migrate <spec-name>
+sce collab migrate <spec-name>
 ```
 
 ## Best Practices
@@ -250,7 +250,7 @@ Keep dependencies minimal and well-justified. Too many dependencies create bottl
 
 ### 3. Regular Verification
 
-Run `kse collab verify` frequently to catch interface mismatches early.
+Run `sce collab verify` frequently to catch interface mismatches early.
 
 ### 4. Integration Testing
 
@@ -258,11 +258,11 @@ Write integration tests that span multiple Specs to verify they work together co
 
 ### 5. Status Updates
 
-Update Spec status regularly so other Kiro instances know when dependencies are ready.
+Update Spec status regularly so other SCE instances know when dependencies are ready.
 
 ### 6. Critical Path Awareness
 
-Use `kse collab status --graph --critical-path` to identify bottlenecks and prioritize work.
+Use `sce collab status --graph --critical-path` to identify bottlenecks and prioritize work.
 
 ## Troubleshooting
 
@@ -276,7 +276,7 @@ Use `kse collab status --graph --critical-path` to identify bottlenecks and prio
 
 **Error**: `Implementation does not match contract for 'UserService'`
 
-**Solution**: Update either the implementation or the contract to match. Run `kse collab verify` to see specific mismatches.
+**Solution**: Update either the implementation or the contract to match. Run `sce collab verify` to see specific mismatches.
 
 ### Spec Blocked
 
@@ -291,8 +291,8 @@ Use `kse collab status --graph --critical-path` to identify bottlenecks and prio
 You can create nested structures with Sub-Sub-Specs:
 
 ```bash
-kse collab init backend-system --sub-specs api-layer business-logic data-layer
-kse collab init api-layer --sub-specs rest-api graphql-api
+sce collab init backend-system --sub-specs api-layer business-logic data-layer
+sce collab init api-layer --sub-specs rest-api graphql-api
 ```
 
 ### Breaking Changes
@@ -301,8 +301,8 @@ When you need to make breaking changes to an interface:
 
 1. Version the interface (e.g., `UserServiceV2.json`)
 2. Update consumers to use the new version
-3. Run `kse collab verify` to detect breaking changes
-4. Coordinate with affected Kiro instances
+3. Run `sce collab verify` to detect breaking changes
+4. Coordinate with affected SCE instances
 
 ### Custom Integration Tests
 
@@ -348,7 +348,7 @@ Collaboration metadata is stored in `.kiro/specs/{spec-name}/collaboration.json`
     }
   ],
   "assignment": {
-    "kiroInstance": "kiro-1",
+    "kiroInstance": "SCE-1",
     "assignedAt": "2026-02-01T10:00:00Z"
   },
   "status": {

package/docs/spec-locking-guide.md

@@ -1,6 +1,6 @@
 # Spec Locking Guide
 
-This guide explains how to use the Spec locking mechanism for multi-user collaboration in kse projects.
+This guide explains how to use the Spec locking mechanism for multi-user collaboration in sce projects.
 
 ## Overview
 
@@ -10,13 +10,13 @@ When multiple developers work on the same project, they may accidentally edit th
 
 ```bash
 # Before editing a Spec, acquire a lock
-kse lock acquire my-feature --reason "Implementing user authentication"
+sce lock acquire my-feature --reason "Implementing user authentication"
 
 # Check who has locks on which Specs
-kse lock status
+sce lock status
 
 # When done editing, release the lock
-kse unlock my-feature
+sce unlock my-feature
 ```
 
 ## Commands
@@ -24,7 +24,7 @@ kse unlock my-feature
 ### Acquire a Lock
 
 ```bash
-kse lock acquire <spec-name> [options]
+sce lock acquire <spec-name> [options]
 ```
 
 Options:
@@ -33,15 +33,15 @@ Options:
 
 Example:
 ```bash
-kse lock acquire 01-00-user-auth --reason "Adding OAuth support" --timeout 48
+sce lock acquire 01-00-user-auth --reason "Adding OAuth support" --timeout 48
 ```
 
 ### Release a Lock
 
 ```bash
-kse unlock <spec-name> [options]
+sce unlock <spec-name> [options]
 # or
-kse lock release <spec-name> [options]
+sce lock release <spec-name> [options]
 ```
 
 Options:
@@ -49,18 +49,18 @@ Options:
 
 Example:
 ```bash
-kse unlock 01-00-user-auth
-kse unlock 01-00-user-auth --force  # Override someone else's lock
+sce unlock 01-00-user-auth
+sce unlock 01-00-user-auth --force  # Override someone else's lock
 ```
 
 ### Check Lock Status
 
 ```bash
 # View all locked Specs
-kse lock status
+sce lock status
 
 # View specific Spec lock status
-kse lock status <spec-name>
+sce lock status <spec-name>
 ```
 
 Output includes:
@@ -73,7 +73,7 @@ Output includes:
 ### Clean Up Stale Locks
 
 ```bash
-kse lock cleanup
+sce lock cleanup
 ```
 
 Removes all locks that have exceeded their timeout period. This is useful when:
@@ -84,14 +84,14 @@ Removes all locks that have exceeded their timeout period. This is useful when:
 ### View Machine Identifier
 
 ```bash
-kse lock whoami
+sce lock whoami
 ```
 
 Shows your machine's unique identifier, which is used to track lock ownership.
 
 ## Integration with Status Command
 
-The `kse status` command now shows lock indicators for each Spec:
+The `sce status` command now shows lock indicators for each Spec:
 
 ```
 📁 Specs (5)
@@ -117,19 +117,19 @@ Lock indicators:
 
 ```bash
 # Good practice
-kse lock acquire my-feature --reason "Refactoring task structure"
+sce lock acquire my-feature --reason "Refactoring task structure"
 # ... make your changes ...
-kse unlock my-feature
+sce unlock my-feature
 ```
 
 ### 2. Use Meaningful Reasons
 
 ```bash
 # Good - explains what you're doing
-kse lock acquire api-spec --reason "Adding pagination to list endpoints"
+sce lock acquire api-spec --reason "Adding pagination to list endpoints"
 
 # Bad - no context
-kse lock acquire api-spec
+sce lock acquire api-spec
 ```
 
 ### 3. Release Locks Promptly
@@ -140,10 +140,10 @@ Don't hold locks longer than necessary. Release as soon as you're done editing.
 
 ```bash
 # Check if anyone is working on the Spec
-kse lock status my-feature
+sce lock status my-feature
 
 # If unlocked, acquire and start working
-kse lock acquire my-feature
+sce lock acquire my-feature
 ```
 
 ### 5. Communicate Before Force Unlocking
@@ -155,10 +155,10 @@ If you need to force unlock someone else's lock:
 
 ```bash
 # Check if stale
-kse lock status their-spec
+sce lock status their-spec
 
 # If stale or confirmed with owner
-kse unlock their-spec --force
+sce unlock their-spec --force
 ```
 
 ## Configuration
@@ -168,8 +168,8 @@ kse unlock their-spec --force
 Default timeout is 24 hours. You can customize per-lock:
 
 ```bash
-kse lock acquire my-spec --timeout 48  # 48 hours
-kse lock acquire quick-fix --timeout 2  # 2 hours
+sce lock acquire my-spec --timeout 48  # 48 hours
+sce lock acquire quick-fix --timeout 2  # 2 hours
 ```
 
 ### Machine ID Storage
@@ -195,7 +195,7 @@ You're trying to unlock a Spec locked by another machine. Options:
 
 Run periodic cleanup:
 ```bash
-kse lock cleanup
+sce lock cleanup
 ```
 
 Consider adding this to your CI/CD pipeline or team workflow.

package/docs/spec-numbering-guide.md

@@ -4,7 +4,7 @@
 
 ## Overview
 
-Kiro Spec Engine uses a two-part numbering system: `{major}-{minor}-{description}`
+Scene Capability Engine uses a two-part numbering system: `{major}-{minor}-{description}`
 
 - **Major number**: Represents a feature domain or theme (01, 02, 03, ...)
 - **Minor number**: Represents iterations or sub-features within that domain (00, 01, 02, ...)
@@ -169,7 +169,7 @@ Group Specs that:
 
 ## Practical Examples
 
-### Example 1: Tool/Library Project (kiro-spec-engine)
+### Example 1: Tool/Library Project (scene-capability-engine)
 
 **Project Type**: CLI tool with independent features
 
@@ -314,17 +314,17 @@ If you started with simple numbering and need to add structure:
 
 ## Tool Support
 
-Kiro Spec Engine provides commands to help with numbering:
+Scene Capability Engine provides commands to help with numbering:
 
 ```bash
 # List all Specs with their numbers
-kse status
+sce status
 
 # View Specs grouped by major number
-kse workflows
+sce workflows
 
 # Get next available number suggestion
-kse workflows --suggest-next
+sce workflows --suggest-next
 ```
 
 ## Summary

package/docs/spec-workflow.md

@@ -1,6 +1,6 @@
 # Spec Workflow Guide
 
-> Understanding the Spec-driven development workflow in kse
+> Understanding the Spec-driven development workflow in sce
 
 ---
 
@@ -13,7 +13,7 @@
 
 ## Overview
 
-A **Spec** (specification) is the fundamental unit of work in kse. It's a structured description of a feature or component that guides both human developers and AI assistants through the implementation process.
+A **Spec** (specification) is the fundamental unit of work in sce. It's a structured description of a feature or component that guides both human developers and AI assistants through the implementation process.
 
 Every Spec follows a three-stage workflow: **Requirements → Design → Tasks**
 
@@ -251,7 +251,7 @@ Response: { ... }
 
 **1. Create the Spec:**
 ```bash
-kse spec bootstrap --name 01-00-user-login --non-interactive
+sce spec bootstrap --name 01-00-user-login --non-interactive
 ```
 
 **2. Write Requirements** (`.kiro/specs/01-00-user-login/requirements.md`):
@@ -292,7 +292,7 @@ Response: { token } or { error }
 
 **5. Export Context:**
 ```bash
-kse context export 01-00-user-login
+sce context export 01-00-user-login
 ```
 
 **6. Implement with AI:**
@@ -302,22 +302,22 @@ kse context export 01-00-user-login
 
 **7. Track Progress:**
 ```bash
-kse status
+sce status
 ```
 
 **8. Maintain Document Governance:**
 ```bash
 # Check for document violations
-kse docs diagnose
+sce docs diagnose
 
 # Clean up temporary files
-kse docs cleanup --spec 01-00-user-login
+sce docs cleanup --spec 01-00-user-login
 
 # Organize artifacts (reports, scripts, etc.)
-kse docs archive --spec 01-00-user-login
+sce docs archive --spec 01-00-user-login
 
 # Validate final structure
-kse docs validate --spec 01-00-user-login
+sce docs validate --spec 01-00-user-login
 ```
 
 ---
@@ -371,16 +371,16 @@ graph TD
 ```mermaid
 sequenceDiagram
     participant Dev as Developer
-    participant kse as kse
+    participant sce as sce
     participant AI as AI Tool
     
-    Dev->>kse: Create Spec (requirements, design, tasks)
-    Dev->>kse: kse context export spec-name
-    kse->>Dev: context-export.md
+    Dev->>sce: Create Spec (requirements, design, tasks)
+    Dev->>sce: sce context export spec-name
+    sce->>Dev: context-export.md
     Dev->>AI: Provide context
     AI->>Dev: Generate code
-    Dev->>kse: Update task status
-    Dev->>kse: kse status (check progress)
+    Dev->>sce: Update task status
+    Dev->>sce: sce status (check progress)
 ```
 
 ### Automated Workflow (Windsurf/Cline)
@@ -389,13 +389,13 @@ sequenceDiagram
 sequenceDiagram
     participant Dev as Developer
     participant AI as AI Tool
-    participant kse as kse
+    participant sce as sce
     
     Dev->>AI: "Implement user login feature"
-    AI->>kse: kse context export 01-00-user-login
-    kse->>AI: Return context
+    AI->>sce: sce context export 01-00-user-login
+    sce->>AI: Return context
     AI->>AI: Generate code
-    AI->>kse: kse task claim 01-00-user-login 1.1
+    AI->>sce: sce task claim 01-00-user-login 1.1
     AI->>Dev: Code generated, task claimed
 ```
 
@@ -422,10 +422,10 @@ sequenceDiagram
 4. **Be AI-friendly** - Tasks should be clear enough for AI to implement
 
 ### Document Governance
-1. **Keep Specs clean** - Use `kse docs archive` to organize artifacts
-2. **Remove temporary files** - Use `kse docs cleanup` regularly
-3. **Validate structure** - Use `kse docs validate` before committing
-4. **Install Git hooks** - Use `kse docs hooks install` to prevent violations
+1. **Keep Specs clean** - Use `sce docs archive` to organize artifacts
+2. **Remove temporary files** - Use `sce docs cleanup` regularly
+3. **Validate structure** - Use `sce docs validate` before committing
+4. **Install Git hooks** - Use `sce docs hooks install` to prevent violations
 
 ### Throughout
 1. **Keep it updated** - Specs are living documents
@@ -486,7 +486,7 @@ sequenceDiagram
 - **[Quick Start Guide](quick-start.md)** - Get started with your first Spec
 - **[Document Governance](document-governance.md)** - Keep your Specs clean and organized
 - **[Integration Modes](integration-modes.md)** - How to use Specs with AI tools
-- **[Command Reference](command-reference.md)** - All kse commands
+- **[Command Reference](command-reference.md)** - All sce commands
 - **[Examples](examples/)** - Complete example Specs
 
 ---
@@ -509,7 +509,7 @@ The Spec workflow is:
 
 **Start your next Spec:** 🚀
 ```bash
-kse spec bootstrap --name 02-00-your-feature --non-interactive
+sce spec bootstrap --name 02-00-your-feature --non-interactive
 ```
 
 ---