scene-capability-engine 3.0.1 → 3.0.2

package/docs/steering-strategy-guide.md

@@ -2,11 +2,11 @@
 
 ## Overview
 
-When adopting kiro-spec-engine (kse) into a project that already has steering files in `.kiro/steering/`, you must choose a steering strategy. This is because Kiro IDE loads all files in the steering directory, and having both kse steering rules and your project's custom steering rules can cause conflicts.
+When adopting scene-capability-engine (sce) into a project that already has steering files in `.kiro/steering/`, you must choose a steering strategy. This is because AI IDE loads all files in the steering directory, and having both sce steering rules and your project's custom steering rules can cause conflicts.
 
 ## Why Steering Exclusivity?
 
-Kiro IDE automatically loads all Markdown files in `.kiro/steering/` as AI behavior rules. If you have both kse steering files and your project's custom steering files, the AI will try to follow both sets of rules, which can lead to:
+AI IDE automatically loads all Markdown files in `.kiro/steering/` as AI behavior rules. If you have both sce steering files and your project's custom steering files, the AI will try to follow both sets of rules, which can lead to:
 
 - Conflicting instructions
 - Unpredictable AI behavior
@@ -16,16 +16,16 @@ Therefore, you must choose **one** set of steering rules to use.
 
 ## Steering Strategies
 
-### Strategy 1: Use kse Steering (Recommended for New Users)
+### Strategy 1: Use sce Steering (Recommended for New Users)
 
 **When to choose:**
-- You're new to kse and want to use the recommended steering rules
+- You're new to sce and want to use the recommended steering rules
 - You don't have critical custom steering rules
-- You want the full kse experience with optimized AI behavior
+- You want the full sce experience with optimized AI behavior
 
 **What happens:**
 1. Your existing steering files are backed up to `.kiro/backups/steering-{timestamp}/`
-2. kse steering template files are installed to `.kiro/steering/`
+2. sce steering template files are installed to `.kiro/steering/`
 3. The backup ID is saved in `.kiro/adoption-config.json`
 4. You can rollback if needed
 
@@ -39,34 +39,34 @@ Therefore, you must choose **one** set of steering rules to use.
 
 **When to choose:**
 - You have custom steering rules that are critical to your project
-- You want to integrate kse without changing your AI behavior rules
+- You want to integrate sce without changing your AI behavior rules
 - You're experienced with steering files and want full control
 
 **What happens:**
 1. Your existing steering files are preserved
-2. kse steering files are **not** installed
+2. sce steering files are **not** installed
 3. The choice is documented in `.kiro/adoption-config.json`
-4. You can manually integrate kse steering concepts if desired
+4. You can manually integrate sce steering concepts if desired
 
 **Trade-offs:**
-- You won't get kse's optimized AI behavior out of the box
-- You'll need to manually add kse-specific steering rules if needed
-- Spec workflow may not work as smoothly without kse steering
+- You won't get sce's optimized AI behavior out of the box
+- You'll need to manually add sce-specific steering rules if needed
+- Spec workflow may not work as smoothly without sce steering
 
 ## Adoption Flow
 
 ```
-kse adopt
+sce adopt
     ↓
 Detect existing steering files
     ↓
-    ├─ No steering files → Install kse steering (default)
+    ├─ No steering files → Install sce steering (default)
     │
     └─ Steering files found → Prompt for strategy
            ↓
-           ├─ use-kse → Backup existing → Install kse steering
+           ├─ use-kse → Backup existing → Install sce steering
            │
-           └─ use-project → Keep existing → Skip kse steering
+           └─ use-project → Keep existing → Skip sce steering
 ```
 
 ## Rollback
@@ -75,19 +75,19 @@ If you chose "use-kse" and want to restore your original steering files:
 
 ```bash
 # List available backups
-kse rollback --list
+sce rollback --list
 
 # Restore from backup
-kse rollback {backup-id}
+sce rollback {backup-id}
 ```
 
 Or manually restore from `.kiro/backups/steering-{timestamp}/`.
 
 ## Manual Integration
 
-If you chose "use-project" but want to incorporate kse steering concepts:
+If you chose "use-project" but want to incorporate sce steering concepts:
 
-1. Review kse steering templates in `template/.kiro/steering/`
+1. Review sce steering templates in `template/.kiro/steering/`
 2. Identify useful concepts (Spec workflow, Ultrawork principles, etc.)
 3. Manually merge relevant sections into your steering files
 4. Test with a sample Spec to ensure compatibility
@@ -109,20 +109,20 @@ Your steering strategy choice is saved in `.kiro/adoption-config.json`:
 
 ## Best Practices
 
-### For New kse Users
+### For New sce Users
 
 1. **Choose "use-kse"** to get the full experience
-2. Review the installed steering files to understand kse workflow
+2. Review the installed steering files to understand sce workflow
 3. Customize `ENVIRONMENT.md` for your project specifics
 4. Update `CURRENT_CONTEXT.md` as you work on different Specs
 
 ### For Experienced Users
 
 1. **Choose "use-project"** if you have mature steering rules
-2. Review kse steering templates for useful patterns
+2. Review sce steering templates for useful patterns
 3. Consider creating a hybrid approach:
    - Keep your core steering rules
-   - Add kse-specific rules in separate files
+   - Add sce-specific rules in separate files
    - Use file naming to control load order (e.g., `00-core.md`, `10-kse.md`)
 
 ### For Teams
@@ -138,20 +138,20 @@ Your steering strategy choice is saved in `.kiro/adoption-config.json`:
 
 **Solution:**
 - Check which steering strategy you chose: `cat .kiro/adoption-config.json`
-- If "use-kse", verify kse steering files are present
-- If "use-project", ensure your steering files are compatible with kse
+- If "use-kse", verify sce steering files are present
+- If "use-project", ensure your steering files are compatible with sce
 
 ### Problem: Want to switch strategies after adoption
 
 **Solution:**
 1. If currently "use-kse":
    ```bash
-   kse rollback {steering-backup-id}
+   sce rollback {steering-backup-id}
    ```
 
 2. If currently "use-project":
    - Manually backup your steering files
-   - Copy kse templates from `template/.kiro/steering/`
+   - Copy sce templates from `template/.kiro/steering/`
    - Update `.kiro/adoption-config.json`
 
 ### Problem: Lost steering backup
@@ -163,21 +163,21 @@ Your steering strategy choice is saved in `.kiro/adoption-config.json`:
 
 ## FAQ
 
-**Q: Can I use both kse and project steering files?**
+**Q: Can I use both sce and project steering files?**
 
-A: No, due to Kiro IDE's behavior. You must choose one set of rules.
+A: No, due to AI IDE's behavior. You must choose one set of rules.
 
-**Q: Will my Specs work without kse steering?**
+**Q: Will my Specs work without sce steering?**
 
-A: Yes, but the AI may not follow kse workflow conventions as closely.
+A: Yes, but the AI may not follow sce workflow conventions as closely.
 
-**Q: Can I modify kse steering files after installation?**
+**Q: Can I modify sce steering files after installation?**
 
-A: Yes! kse steering files are templates. Customize them for your project.
+A: Yes! sce steering files are templates. Customize them for your project.
 
 **Q: What if I don't have any steering files?**
 
-A: kse will automatically install its steering files (no choice needed).
+A: sce will automatically install its steering files (no choice needed).
 
 **Q: Can I switch strategies later?**
 
@@ -187,7 +187,7 @@ A: Yes, but you'll need to manually manage the steering files and update the con
 
 - [Adoption Guide](./adoption-guide.md) - Complete adoption workflow
 - [Spec Workflow Guide](../.kiro/specs/SPEC_WORKFLOW_GUIDE.md) - How to use Specs
-- [Steering Files](../.kiro/steering/) - kse steering templates
+- [Steering Files](../.kiro/steering/) - sce steering templates
 
 ---
 

package/docs/team-collaboration-guide.md

@@ -2,7 +2,7 @@
 
 ## Overview
 
-This guide explains how to effectively collaborate on kse projects with your team, covering version control strategies, Spec sharing, and multi-user workflows.
+This guide explains how to effectively collaborate on sce projects with your team, covering version control strategies, Spec sharing, and multi-user workflows.
 
 ---
 
@@ -10,7 +10,7 @@ This guide explains how to effectively collaborate on kse projects with your tea
 
 ### What to Commit
 
-kse uses a **layered .gitignore strategy** to balance team collaboration and personal workflow:
+sce uses a **layered .gitignore strategy** to balance team collaboration and personal workflow:
 
 #### ✅ DO Commit (Team Shared)
 
@@ -78,15 +78,15 @@ kse uses a **layered .gitignore strategy** to balance team collaboration and per
 # Developer A
 git clone <repo>
 cd project
-npm install -g kiro-spec-engine
-kse adopt
+npm install -g scene-capability-engine
+sce adopt
 .kiro/create-workspace.bat alice
 
 # Developer B
 git clone <repo>
 cd project
-npm install -g kiro-spec-engine
-kse adopt
+npm install -g scene-capability-engine
+sce adopt
 .kiro/create-workspace.bat bob
 ```
 
@@ -97,7 +97,7 @@ kse adopt
 .kiro/switch-workspace.bat alice
 
 # Work on your tasks
-kse status
+sce status
 # ... make changes ...
 
 # Commit Spec changes (shared)
@@ -119,7 +119,7 @@ git commit -m "feat: complete task 3.2 in Spec 15-00"
 
 ```bash
 # Create new Spec
-kse workflows create user-authentication
+sce workflows create user-authentication
 
 # Edit requirements, design, tasks
 # ... work on Spec documents ...
@@ -137,7 +137,7 @@ git push
 git pull
 
 # Check available Specs
-kse status
+sce status
 
 # Read Spec documents
 cat .kiro/specs/21-00-user-authentication/requirements.md
@@ -191,17 +191,17 @@ project-root/
 git clone <repo>
 cd project
 
-# Install kse
-npm install -g kiro-spec-engine
-kse adopt
+# Install sce
+npm install -g scene-capability-engine
+sce adopt
 
 # Register environments from templates
-kse env register config/env-local.json
-kse env register config/env-staging.json
-kse env register config/env-production.json
+sce env register config/env-local.json
+sce env register config/env-staging.json
+sce env register config/env-production.json
 
 # Switch to local environment
-kse env switch local
+sce env switch local
 ```
 
 **Benefits**:
@@ -267,7 +267,7 @@ git add .kiro/specs/22-00-feature-name/reports/performance-analysis.md
 
 ```bash
 # 1. Create Spec
-kse workflows create payment-integration
+sce workflows create payment-integration
 
 # 2. Write requirements
 # Edit .kiro/specs/23-00-payment-integration/requirements.md
@@ -294,7 +294,7 @@ git push
 git pull
 
 # 2. Review Spec
-kse status
+sce status
 cat .kiro/specs/23-00-payment-integration/requirements.md
 cat .kiro/specs/23-00-payment-integration/design.md
 
@@ -347,18 +347,18 @@ cat .kiro/specs/23-00-payment-integration/tasks.md
 # 1. Clone and setup
 git clone <repo>
 cd project
-npm install -g kiro-spec-engine
-kse adopt
+npm install -g scene-capability-engine
+sce adopt
 
 # 2. Create personal workspace
 .kiro/create-workspace.bat john
 
 # 3. Register environments
-kse env register config/env-local.json
-kse env switch local
+sce env register config/env-local.json
+sce env switch local
 
 # 4. Review project Specs
-kse status
+sce status
 # See all features and their status
 
 # 5. Pick a task

package/docs/testing-strategy.md

@@ -2,7 +2,7 @@
 
 ## Overview
 
-This document defines the testing strategy for kse (Kiro Spec Engine) to balance code quality with CI/CD performance.
+This document defines the testing strategy for sce (Scene Capability Engine) to balance code quality with CI/CD performance.
 
 ## Test Categories
 
@@ -269,4 +269,4 @@ npm run test:coverage
 
 **Version**: v1.0  
 **Last Updated**: 2026-01-29  
-**Maintained by**: kse Development Team
+**Maintained by**: sce Development Team

package/docs/tools/claude-guide.md

@@ -1,6 +1,6 @@
-# Using kse with Claude Code
+# Using sce with Claude Code
 
-> Complete guide to integrating kse with Claude Code for AI-assisted development
+> Complete guide to integrating sce with Claude Code for AI-assisted development
 
 ---
 
@@ -16,9 +16,9 @@
 
 **Claude Code** is Anthropic's AI coding assistant with a large context window (200K tokens), excellent code understanding, and conversational development capabilities.
 
-**kse integration with Claude** uses the **Manual Export** mode, where you export Spec context and paste it into Claude conversations.
+**sce integration with Claude** uses the **Manual Export** mode, where you export Spec context and paste it into Claude conversations.
 
-### Why Use kse with Claude?
+### Why Use sce with Claude?
 
 - ✅ **Large context window** - Can handle entire Specs at once
 - ✅ **Excellent understanding** - Claude deeply understands requirements and design
@@ -32,8 +32,8 @@
 **Mode:** Manual Export
 
 **How it works:**
-1. Create Specs in kse (requirements, design, tasks)
-2. Export context: `kse context export spec-name`
+1. Create Specs in sce (requirements, design, tasks)
+2. Export context: `sce context export spec-name`
 3. Copy entire context and paste into Claude conversation
 4. Claude implements features based on your Spec
 5. Update task status manually in tasks.md
@@ -45,8 +45,8 @@
 ### Prerequisites
 
 - **Claude Code access** ([Get access](https://claude.ai/))
-- **kse installed** globally (`npm install -g kiro-spec-engine`)
-- **Project adopted** by kse (`kse adopt`)
+- **sce installed** globally (`npm install -g scene-capability-engine`)
+- **Project adopted** by sce (`sce adopt`)
 
 ### Step 1: Create Shell Alias (Recommended)
 
@@ -54,10 +54,10 @@ Add to your `~/.bashrc` or `~/.zshrc`:
 
 ```bash
 # Quick export and copy to clipboard
-alias kse-clip='kse context export $1 && cat .kiro/specs/$1/context-export.md | pbcopy && echo "✅ Context copied to clipboard"'
+alias sce-clip='sce context export $1 && cat .kiro/specs/$1/context-export.md | pbcopy && echo "✅ Context copied to clipboard"'
 
 # Windows PowerShell (add to $PROFILE)
-function kse-clip { kse context export $args[0]; Get-Content ".kiro\specs\$($args[0])\context-export.md" | Set-Clipboard; Write-Host "✅ Context copied to clipboard" }
+function sce-clip { sce context export $args[0]; Get-Content ".kiro\specs\$($args[0])\context-export.md" | Set-Clipboard; Write-Host "✅ Context copied to clipboard" }
 ```
 
 ---
@@ -70,8 +70,8 @@ function kse-clip { kse context export $args[0]; Get-Content ".kiro\specs\$($arg
 
 **Step 1: Export and copy context**
 ```bash
-kse context export 01-00-user-login
-kse-clip 01-00-user-login  # Or manually copy
+sce context export 01-00-user-login
+sce-clip 01-00-user-login  # Or manually copy
 ```
 
 **Step 2: Start new Claude conversation**
@@ -116,7 +116,7 @@ Edit `.kiro/specs/01-00-user-login/tasks.md`:
 
 **Step 1: Generate task-specific prompt**
 ```bash
-kse prompt generate 01-00-user-login 2.1 --tool=claude-code
+sce prompt generate 01-00-user-login 2.1 --tool=claude-code
 ```
 
 **Step 2: Copy and paste into Claude**
@@ -136,9 +136,9 @@ Please implement this task following the design document.
 
 **1. Create and prepare Spec**
 ```bash
-kse spec bootstrap --name 01-00-user-login --non-interactive
+sce spec bootstrap --name 01-00-user-login --non-interactive
 # Edit requirements.md, design.md, tasks.md
-kse-clip 01-00-user-login
+sce-clip 01-00-user-login
 ```
 
 **2. Start Claude conversation**
@@ -507,7 +507,7 @@ Please implement exactly as specified."
 
 **Solution:** Use task-specific prompts
 ```bash
-kse prompt generate 01-00-user-login 2.1 --tool=claude-code --max-length=10000
+sce prompt generate 01-00-user-login 2.1 --tool=claude-code --max-length=10000
 ```
 
 ### Issue: Lost context in long conversation
@@ -559,7 +559,7 @@ Please fix the implementation."
 ### With Code Review
 ```
 # Share context with reviewer
-kse context export 01-00-user-login
+sce context export 01-00-user-login
 
 # Reviewer can see:
 # - What was supposed to be built (requirements)
@@ -609,18 +609,18 @@ kse context export 01-00-user-login
 
 ## Related Documentation
 
-- **[Quick Start Guide](../quick-start.md)** - Get started with kse
+- **[Quick Start Guide](../quick-start.md)** - Get started with sce
 - **[Integration Modes](../integration-modes.md)** - Understanding integration modes
 - **[Spec Workflow](../spec-workflow.md)** - Creating effective Specs
-- **[Command Reference](../command-reference.md)** - All kse commands
+- **[Command Reference](../command-reference.md)** - All sce commands
 
 ---
 
 ## Summary
 
-**Claude + kse workflow:**
-1. Create Spec in kse (requirements, design, tasks)
-2. Export context: `kse context export spec-name`
+**Claude + sce workflow:**
+1. Create Spec in sce (requirements, design, tasks)
+2. Export context: `sce context export spec-name`
 3. Start fresh Claude conversation
 4. Paste complete context
 5. Implement tasks iteratively
@@ -639,11 +639,11 @@ kse context export 01-00-user-login
 - Reference design document explicitly
 - Review all generated code
 
-**Start using kse with Claude:** 🚀
+**Start using sce with Claude:** 🚀
 ```bash
-kse adopt
-kse spec bootstrap --name 01-00-my-feature --non-interactive
-kse-clip 01-00-my-feature
+sce adopt
+sce spec bootstrap --name 01-00-my-feature --non-interactive
+sce-clip 01-00-my-feature
 # Open Claude and paste context
 ```
 

package/docs/tools/cursor-guide.md

@@ -1,6 +1,6 @@
-# Using kse with Cursor
+# Using sce with Cursor
 
-> Complete guide to integrating kse with Cursor IDE for AI-assisted development
+> Complete guide to integrating sce with Cursor IDE for AI-assisted development
 
 ---
 
@@ -16,9 +16,9 @@
 
 **Cursor** is an AI-powered IDE built on VS Code that provides intelligent code completion, chat-based coding, and AI pair programming through Composer mode.
 
-**kse integration with Cursor** uses the **Manual Export** mode, where you export Spec context and provide it to Cursor's AI features (Chat, Composer, or inline suggestions).
+**sce integration with Cursor** uses the **Manual Export** mode, where you export Spec context and provide it to Cursor's AI features (Chat, Composer, or inline suggestions).
 
-### Why Use kse with Cursor?
+### Why Use sce with Cursor?
 
 - ✅ **Structured context** - Cursor understands your requirements and design
 - ✅ **Better code generation** - AI follows your architecture decisions
@@ -32,8 +32,8 @@
 **Mode:** Manual Export
 
 **How it works:**
-1. You create Specs in kse (requirements, design, tasks)
-2. You export context using `kse context export`
+1. You create Specs in sce (requirements, design, tasks)
+2. You export context using `sce context export`
 3. You provide context to Cursor (Chat, Composer, or .cursorrules)
 4. Cursor generates code based on your Spec
 5. You update task status in tasks.md
@@ -45,17 +45,17 @@
 ### Prerequisites
 
 - **Cursor IDE** installed ([Download](https://cursor.sh/))
-- **kse** installed globally (`npm install -g kiro-spec-engine`)
-- **Project adopted** by kse (`kse adopt`)
+- **sce** installed globally (`npm install -g scene-capability-engine`)
+- **Project adopted** by sce (`sce adopt`)
 
-### Step 1: Configure Cursor for kse
+### Step 1: Configure Cursor for sce
 
 Create a `.cursorrules` file in your project root:
 
 ```markdown
 # Project Rules
 
-This project uses kse (Kiro Spec Engine) for spec-driven development.
+This project uses sce (Scene Capability Engine) for spec-driven development.
 
 ## Spec Location
 All Specs are in `.kiro/specs/` directory.
@@ -87,10 +87,10 @@ Add to your `~/.bashrc` or `~/.zshrc`:
 
 ```bash
 # Quick export and copy to clipboard
-alias kse-clip='kse context export $1 && cat .kiro/specs/$1/context-export.md | pbcopy && echo "✅ Context copied to clipboard"'
+alias sce-clip='sce context export $1 && cat .kiro/specs/$1/context-export.md | pbcopy && echo "✅ Context copied to clipboard"'
 
 # Generate task-specific prompt
-alias kse-task='kse prompt generate $1 $2 --tool=cursor'
+alias sce-task='sce prompt generate $1 $2 --tool=cursor'
 ```
 
 Reload your shell:
@@ -108,7 +108,7 @@ source ~/.bashrc  # or source ~/.zshrc
 
 **Step 1: Export context**
 ```bash
-kse context export 01-00-user-login
+sce context export 01-00-user-login
 ```
 
 **Step 2: Copy context**
@@ -120,7 +120,7 @@ cat .kiro/specs/01-00-user-login/context-export.md | pbcopy
 type .kiro\specs\01-00-user-login\context-export.md | clip
 
 # Or use alias
-kse-clip 01-00-user-login
+sce-clip 01-00-user-login
 ```
 
 **Step 3: Open Cursor Composer**
@@ -156,7 +156,7 @@ Edit `.kiro/specs/01-00-user-login/tasks.md`:
 
 **Step 1: Generate task-specific prompt**
 ```bash
-kse prompt generate 01-00-user-login 1.1 --tool=cursor
+sce prompt generate 01-00-user-login 1.1 --tool=cursor
 ```
 
 **Step 2: Open Cursor Chat**
@@ -213,13 +213,13 @@ class AuthController {
 
 **1. Create and write Spec**
 ```bash
-kse spec bootstrap --name 01-00-user-login --non-interactive
+sce spec bootstrap --name 01-00-user-login --non-interactive
 # Edit requirements.md, design.md, tasks.md
 ```
 
 **2. Export context**
 ```bash
-kse-clip 01-00-user-login
+sce-clip 01-00-user-login
 ```
 
 **3. Open Cursor Composer (Cmd+K)**
@@ -366,10 +366,10 @@ Implement task 1.3: Add authentication logic
 **Re-export after Spec changes:**
 ```bash
 # After editing design.md
-kse context export 01-00-user-login
+sce context export 01-00-user-login
 
 # Copy new context
-kse-clip 01-00-user-login
+sce-clip 01-00-user-login
 
 # Provide to Cursor again
 ```
@@ -379,7 +379,7 @@ kse-clip 01-00-user-login
 **For large Specs (>5KB context):**
 ```bash
 # Instead of exporting entire Spec
-kse prompt generate 01-00-user-login 1.1 --tool=cursor
+sce prompt generate 01-00-user-login 1.1 --tool=cursor
 
 # Generates focused prompt for just task 1.1
 ```
@@ -458,7 +458,7 @@ Please implement exactly as specified.
 
 **Solution:** Use task-specific prompts
 ```bash
-kse prompt generate 01-00-user-login 1.1 --tool=cursor --max-length=5000
+sce prompt generate 01-00-user-login 1.1 --tool=cursor --max-length=5000
 ```
 
 ### Issue: Cursor suggests wrong file locations
@@ -576,7 +576,7 @@ Please fix the implementation."
 
 ```bash
 # Export context for reviewer
-kse context export 01-00-user-login
+sce context export 01-00-user-login
 
 # Share context-export.md with reviewer
 # Reviewer can see requirements and design
@@ -662,18 +662,18 @@ Please help debug and fix the issue.
 
 ## Related Documentation
 
-- **[Quick Start Guide](../quick-start.md)** - Get started with kse
+- **[Quick Start Guide](../quick-start.md)** - Get started with sce
 - **[Integration Modes](../integration-modes.md)** - Understanding integration modes
 - **[Spec Workflow](../spec-workflow.md)** - Creating effective Specs
-- **[Command Reference](../command-reference.md)** - All kse commands
+- **[Command Reference](../command-reference.md)** - All sce commands
 
 ---
 
 ## Summary
 
-**Cursor + kse workflow:**
-1. Create Spec in kse (requirements, design, tasks)
-2. Export context: `kse context export spec-name`
+**Cursor + sce workflow:**
+1. Create Spec in sce (requirements, design, tasks)
+2. Export context: `sce context export spec-name`
 3. Use Cursor Composer (Cmd+K) or Chat (Cmd+L)
 4. Provide context and implement tasks
 5. Update tasks.md as you complete tasks
@@ -691,11 +691,11 @@ Please help debug and fix the issue.
 - Re-export context after Spec changes
 - Review all AI suggestions
 
-**Start using kse with Cursor:** 🚀
+**Start using sce with Cursor:** 🚀
 ```bash
-kse adopt
-kse spec bootstrap --name 01-00-my-feature --non-interactive
-kse context export 01-00-my-feature
+sce adopt
+sce spec bootstrap --name 01-00-my-feature --non-interactive
+sce context export 01-00-my-feature
 # Open Cursor Composer (Cmd+K) and paste context
 ```