@ngxtm/devkit 3.19.0 → 3.21.0

package/merged-commands/data-engineering-data-driven-feature.md

@@ -31,18 +31,18 @@ Build features guided by data insights, A/B testing, and continuous measurement
 ## Phase 1: Data Analysis and Hypothesis Formation
 
 ### 1. Exploratory Data Analysis
-- Use Task tool with subagent_type="machine-learning-ops::data-scientist"
+- Use Task tool with subagent_type="general-purpose"
 - Prompt: "Perform exploratory data analysis for feature: $ARGUMENTS. Analyze existing user behavior data, identify patterns and opportunities, segment users by behavior, and calculate baseline metrics. Use modern analytics tools (Amplitude, Mixpanel, Segment) to understand current user journeys, conversion funnels, and engagement patterns."
 - Output: EDA report with visualizations, user segments, behavioral patterns, baseline metrics
 
 ### 2. Business Hypothesis Development
-- Use Task tool with subagent_type="business-analytics::business-analyst"
+- Use Task tool with subagent_type="general-purpose"
 - Context: Data scientist's EDA findings and behavioral patterns
 - Prompt: "Formulate business hypotheses for feature: $ARGUMENTS based on data analysis. Define clear success metrics, expected impact on key business KPIs, target user segments, and minimum detectable effects. Create measurable hypotheses using frameworks like ICE scoring or RICE prioritization."
 - Output: Hypothesis document, success metrics definition, expected ROI calculations
 
 ### 3. Statistical Experiment Design
-- Use Task tool with subagent_type="machine-learning-ops::data-scientist"
+- Use Task tool with subagent_type="general-purpose"
 - Context: Business hypotheses and success metrics
 - Prompt: "Design statistical experiment for feature: $ARGUMENTS. Calculate required sample size for statistical power, define control and treatment groups, specify randomization strategy, and plan for multiple testing corrections. Consider Bayesian A/B testing approaches for faster decision making. Design for both primary and guardrail metrics."
 - Output: Experiment design document, power analysis, statistical test plan
@@ -50,19 +50,19 @@ Build features guided by data insights, A/B testing, and continuous measurement
 ## Phase 2: Feature Architecture and Analytics Design
 
 ### 4. Feature Architecture Planning
-- Use Task tool with subagent_type="data-engineering::backend-architect"
+- Use Task tool with subagent_type="general-purpose"
 - Context: Business requirements and experiment design
 - Prompt: "Design feature architecture for: $ARGUMENTS with A/B testing capability. Include feature flag integration (LaunchDarkly, Split.io, or Optimizely), gradual rollout strategy, circuit breakers for safety, and clean separation between control and treatment logic. Ensure architecture supports real-time configuration updates."
 - Output: Architecture diagrams, feature flag schema, rollout strategy
 
 ### 5. Analytics Instrumentation Design
-- Use Task tool with subagent_type="data-engineering::data-engineer"
+- Use Task tool with subagent_type="general-purpose"
 - Context: Feature architecture and success metrics
 - Prompt: "Design comprehensive analytics instrumentation for: $ARGUMENTS. Define event schemas for user interactions, specify properties for segmentation and analysis, design funnel tracking and conversion events, plan cohort analysis capabilities. Implement using modern SDKs (Segment, Amplitude, Mixpanel) with proper event taxonomy."
 - Output: Event tracking plan, analytics schema, instrumentation guide
 
 ### 6. Data Pipeline Architecture
-- Use Task tool with subagent_type="data-engineering::data-engineer"
+- Use Task tool with subagent_type="general-purpose"
 - Context: Analytics requirements and existing data infrastructure
 - Prompt: "Design data pipelines for feature: $ARGUMENTS. Include real-time streaming for live metrics (Kafka, Kinesis), batch processing for detailed analysis, data warehouse integration (Snowflake, BigQuery), and feature store for ML if applicable. Ensure proper data governance and GDPR compliance."
 - Output: Pipeline architecture, ETL/ELT specifications, data flow diagrams
@@ -70,19 +70,19 @@ Build features guided by data insights, A/B testing, and continuous measurement
 ## Phase 3: Implementation with Instrumentation
 
 ### 7. Backend Implementation
-- Use Task tool with subagent_type="backend-development::backend-architect"
+- Use Task tool with subagent_type="general-purpose"
 - Context: Architecture design and feature requirements
 - Prompt: "Implement backend for feature: $ARGUMENTS with full instrumentation. Include feature flag checks at decision points, comprehensive event tracking for all user actions, performance metrics collection, error tracking and monitoring. Implement proper logging for experiment analysis."
 - Output: Backend code with analytics, feature flag integration, monitoring setup
 
 ### 8. Frontend Implementation
-- Use Task tool with subagent_type="frontend-mobile-development::frontend-developer"
+- Use Task tool with subagent_type="general-purpose"
 - Context: Backend APIs and analytics requirements
 - Prompt: "Build frontend for feature: $ARGUMENTS with analytics tracking. Implement event tracking for all user interactions, session recording integration if applicable, performance metrics (Core Web Vitals), and proper error boundaries. Ensure consistent experience between control and treatment groups."
 - Output: Frontend code with analytics, A/B test variants, performance monitoring
 
 ### 9. ML Model Integration (if applicable)
-- Use Task tool with subagent_type="machine-learning-ops::ml-engineer"
+- Use Task tool with subagent_type="general-purpose"
 - Context: Feature requirements and data pipelines
 - Prompt: "Integrate ML models for feature: $ARGUMENTS if needed. Implement online inference with low latency, A/B testing between model versions, model performance tracking, and automatic fallback mechanisms. Set up model monitoring for drift detection."
 - Output: ML pipeline, model serving infrastructure, monitoring setup
@@ -90,13 +90,13 @@ Build features guided by data insights, A/B testing, and continuous measurement
 ## Phase 4: Pre-Launch Validation
 
 ### 10. Analytics Validation
-- Use Task tool with subagent_type="data-engineering::data-engineer"
+- Use Task tool with subagent_type="general-purpose"
 - Context: Implemented tracking and event schemas
 - Prompt: "Validate analytics implementation for: $ARGUMENTS. Test all event tracking in staging, verify data quality and completeness, validate funnel definitions, ensure proper user identification and session tracking. Run end-to-end tests for data pipeline."
 - Output: Validation report, data quality metrics, tracking coverage analysis
 
 ### 11. Experiment Setup
-- Use Task tool with subagent_type="cloud-infrastructure::deployment-engineer"
+- Use Task tool with subagent_type="general-purpose"
 - Context: Feature flags and experiment design
 - Prompt: "Configure experiment infrastructure for: $ARGUMENTS. Set up feature flags with proper targeting rules, configure traffic allocation (start with 5-10%), implement kill switches, set up monitoring alerts for key metrics. Test randomization and assignment logic."
 - Output: Experiment configuration, monitoring dashboards, rollout plan
@@ -104,13 +104,13 @@ Build features guided by data insights, A/B testing, and continuous measurement
 ## Phase 5: Launch and Experimentation
 
 ### 12. Gradual Rollout
-- Use Task tool with subagent_type="cloud-infrastructure::deployment-engineer"
+- Use Task tool with subagent_type="general-purpose"
 - Context: Experiment configuration and monitoring setup
 - Prompt: "Execute gradual rollout for feature: $ARGUMENTS. Start with internal dogfooding, then beta users (1-5%), gradually increase to target traffic. Monitor error rates, performance metrics, and early indicators. Implement automated rollback on anomalies."
 - Output: Rollout execution, monitoring alerts, health metrics
 
 ### 13. Real-time Monitoring
-- Use Task tool with subagent_type="observability-monitoring::observability-engineer"
+- Use Task tool with subagent_type="general-purpose"
 - Context: Deployed feature and success metrics
 - Prompt: "Set up comprehensive monitoring for: $ARGUMENTS. Create real-time dashboards for experiment metrics, configure alerts for statistical significance, monitor guardrail metrics for negative impacts, track system performance and error rates. Use tools like Datadog, New Relic, or custom dashboards."
 - Output: Monitoring dashboards, alert configurations, SLO definitions
@@ -118,19 +118,19 @@ Build features guided by data insights, A/B testing, and continuous measurement
 ## Phase 6: Analysis and Decision Making
 
 ### 14. Statistical Analysis
-- Use Task tool with subagent_type="machine-learning-ops::data-scientist"
+- Use Task tool with subagent_type="general-purpose"
 - Context: Experiment data and original hypotheses
 - Prompt: "Analyze A/B test results for: $ARGUMENTS. Calculate statistical significance with confidence intervals, check for segment-level effects, analyze secondary metrics impact, investigate any unexpected patterns. Use both frequentist and Bayesian approaches. Account for multiple testing if applicable."
 - Output: Statistical analysis report, significance tests, segment analysis
 
 ### 15. Business Impact Assessment
-- Use Task tool with subagent_type="business-analytics::business-analyst"
+- Use Task tool with subagent_type="general-purpose"
 - Context: Statistical analysis and business metrics
 - Prompt: "Assess business impact of feature: $ARGUMENTS. Calculate actual vs expected ROI, analyze impact on key business metrics, evaluate cost-benefit including operational overhead, project long-term value. Make recommendation on full rollout, iteration, or rollback."
 - Output: Business impact report, ROI analysis, recommendation document
 
 ### 16. Post-Launch Optimization
-- Use Task tool with subagent_type="machine-learning-ops::data-scientist"
+- Use Task tool with subagent_type="general-purpose"
 - Context: Launch results and user feedback
 - Prompt: "Identify optimization opportunities for: $ARGUMENTS based on data. Analyze user behavior patterns in treatment group, identify friction points in user journey, suggest improvements based on data, plan follow-up experiments. Use cohort analysis for long-term impact."
 - Output: Optimization recommendations, follow-up experiment plans

package/merged-commands/debug/fast.md

@@ -1,5 +1,5 @@
 ---
-description: ⚡ Quick Debug — Fast diagnosis for simple bugs
+description: Quick Debug — Fast diagnosis for simple bugs
 version: "1.0"
 category: debugging
 execution-mode: execute
@@ -13,38 +13,22 @@ execution-mode: execute
 
 ---
 
-## 🛑 PRE-FLIGHT (DO FIRST — BLOCKS PHASE 1)
-
-**LOAD now** (in order; path `./rules/` or `~/.{TOOL}/skills/agent-assistant/rules/`):
-1. ORCHESTRATION-LAWS.md  
-2. ADAPTIVE-EXECUTION.md  
-3. EXECUTION-PROTOCOL.md  
-
-**⛔ Do not run Phase 1 until all are loaded.** Follow **all** rules in those files; they override any conflicting instructions in this file.
-
----
-
-## 🔀 TIERED EXECUTION
-
-| Tier | When | Action |
-|------|------|--------|
-| **TIER 1** | runSubagent EXISTS | Invoke sub-agent (MANDATORY) |
-| **TIER 2** | Tool MISSING | EMBODY agent file (FALLBACK) |
+## Execution
+One phase at a time, sequential. Each phase must complete before next begins.
 
 ---
 
-## ⛔ INCREMENTAL EXECUTION (MANDATORY)
+## Phase 1: QUICK DIAGNOSIS
 
-One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in one reply. No batching (load only what each phase needs). **Within each phase:** when doing a part, output it in format so user sees what’s happening (announce before doing).
-
----
+| Attribute | Value |
+|-----------|-------|
+| **Role** | `debugger` |
+| **Goal** | Fast root cause identification |
+| **Exit** | Root cause identified |
 
-## 🎭 Phase 1: QUICK DIAGNOSIS
+### Delegation
 
-| Agent | `debugger` |
-|-------|------------|
-| Goal | Fast root cause identification |
-| Exit | Root cause identified |
+> Task(subagent_type="general-purpose", prompt="You are a debugger. Perform fast root cause identification for the given issue. Exit when root cause is identified.", description="debugger: Fast root cause identification")
 
 ---
 
@@ -61,5 +45,5 @@ One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in
 
 Present findings with:
 
-1. ✅ **Root Cause** — Identified
-2. 🔧 **Fix** → `/fix:fast`
+1. **Root Cause** — Identified
+2. **Fix** → `/fix:fast`

package/merged-commands/debug/hard.md

@@ -1,5 +1,5 @@
 ---
-description: ⚡⚡⚡ Full Debug — Deep investigation for complex issues
+description: Full Debug — Deep investigation for complex issues
 version: "1.0"
 category: debugging
 execution-mode: execute
@@ -13,77 +13,75 @@ execution-mode: execute
 
 ---
 
-## 🛑 PRE-FLIGHT (DO FIRST — BLOCKS PHASE 1)
+## DELIVERABLE FILES
 
-**LOAD now** (in order; path `./rules/` or `~/.{TOOL}/skills/agent-assistant/rules/`):
-
-1. ORCHESTRATION-LAWS.md
-2. ADAPTIVE-EXECUTION.md
-3. EXECUTION-PROTOCOL.md
+| Role | Output |
+|------|--------|
+| debugger | `./reports/debugs/DEBUG-{issue}.md` |
 
-**⛔ Do not run Phase 1 until all are loaded.** Follow **all** rules in those files; they override any conflicting instructions in this file.
+All files in `./reports/` → English only.
 
 ---
 
-## 🔀 TIERED EXECUTION
-
-| Tier       | When               | Action                       |
-| ---------- | ------------------ | ---------------------------- |
-| **TIER 1** | runSubagent EXISTS | Invoke sub-agent (MANDATORY) |
-| **TIER 2** | Tool MISSING       | EMBODY agent file (FALLBACK) |
+## Execution
+One phase at a time, sequential. Each phase must complete before next begins.
 
 ---
 
-## 📁 DELIVERABLE FILES
+## Phase 1: INFORMATION GATHERING
 
-| Agent    | Output                              |
-| -------- | ----------------------------------- |
-| debugger | `./reports/debugs/DEBUG-{issue}.md` |
+| Attribute | Value |
+|-----------|-------|
+| **Role** | `scouter` |
+| **Goal** | Gather context and reproduction steps |
+| **Exit** | Context gathered, reproduction documented |
 
-All files in `./reports/` → English only.
+### Delegation
 
----
+> Task(subagent_type="general-purpose", prompt="You are a scouter. Gather context and reproduction steps for the given issue. Exit when context is gathered and reproduction is documented.", description="scouter: Gather context and reproduction steps")
 
-## ⛔ INCREMENTAL EXECUTION (MANDATORY)
+---
 
-One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in one reply. No batching (load only what each phase needs). **Within each phase:** when doing a part, output it in format so user sees what’s happening (announce before doing).
+## Phase 2: HYPOTHESIS FORMATION
 
----
+| Attribute | Value |
+|-----------|-------|
+| **Role** | `debugger` |
+| **Goal** | Form and rank hypotheses |
+| **Exit** | Hypotheses documented with evidence |
 
-## 🎭 Phase 1: INFORMATION GATHERING
+### Delegation
 
-| Agent | `scouter`                                 |
-| ----- | ----------------------------------------- |
-| Goal  | Gather context and reproduction steps     |
-| Exit  | Context gathered, reproduction documented |
+> Task(subagent_type="general-purpose", prompt="You are a debugger. Form and rank hypotheses for the issue. Exit when hypotheses are documented with evidence.", description="debugger: Form and rank hypotheses")
 
 ---
 
-## 🎭 Phase 2: HYPOTHESIS FORMATION
-
-| Agent | `debugger`                          |
-| ----- | ----------------------------------- |
-| Goal  | Form and rank hypotheses            |
-| Exit  | Hypotheses documented with evidence |
+## Phase 3: ROOT CAUSE ANALYSIS
 
----
+| Attribute | Value |
+|-----------|-------|
+| **Role** | `debugger` |
+| **Goal** | Deep investigation |
+| **Output** | `./reports/debugs/DEBUG-{issue}.md` |
+| **Exit** | Root cause identified, failure chain documented |
 
-## 🎭 Phase 3: ROOT CAUSE ANALYSIS
+### Delegation
 
-| Agent  | `debugger`                                      |
-| ------ | ----------------------------------------------- |
-| Goal   | Deep investigation                              |
-| Output | `./reports/debugs/DEBUG-{issue}.md`             |
-| Exit   | Root cause identified, failure chain documented |
+> Task(subagent_type="general-purpose", prompt="You are a debugger. Perform deep investigation to identify root cause. Write findings to ./reports/debugs/DEBUG-{issue}.md. Exit when root cause is identified and failure chain is documented.", description="debugger: Deep root cause investigation")
 
 ---
 
-## 🎭 Phase 4: SOLUTION DESIGN
+## Phase 4: SOLUTION DESIGN
+
+| Attribute | Value |
+|-----------|-------|
+| **Role** | `planner` |
+| **Goal** | Design fix strategy |
+| **Exit** | Fix approach defined with rollback plan |
+
+### Delegation
 
-| Agent | `planner`                               |
-| ----- | --------------------------------------- |
-| Goal  | Design fix strategy                     |
-| Exit  | Fix approach defined with rollback plan |
+> Task(subagent_type="general-purpose", prompt="You are a planner. Design a fix strategy based on the root cause analysis. Exit when fix approach is defined with rollback plan.", description="planner: Design fix strategy")
 
 ---
 
@@ -91,6 +89,6 @@ One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in
 
 Present findings with:
 
-1. ✅ **Root Cause** — Identified
-2. 🔧 **Fix** → `/fix:hard`
-3. 📝 **Document** → `/docs:core`
+1. **Root Cause** — Identified
+2. **Fix** → `/fix:hard`
+3. **Document** → `/docs:core`

package/merged-commands/debug.md

@@ -6,7 +6,7 @@ argument-hint: [issues]
 **Reported Issues**:
  $ARGUMENTS
 
-Use the `debugger` subagent to find the root cause of the issues, then analyze and explain the reports to the user.
+Use a Task agent for debugging to find the root cause of the issues, then analyze and explain the reports to the user: Task(subagent_type="general-purpose", prompt="You are a debugger. Find root cause of issues...", description="Debug issues")
 
 **IMPORTANT**: **Do not** implement the fix automatically.
 **IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.

package/merged-commands/debugging-toolkit-smart-debug.md

@@ -39,7 +39,7 @@ Parse for:
 ## Workflow
 
 ### 1. Initial Triage
-Use Task tool (subagent_type="debugger") for AI-powered analysis:
+Use Task tool (subagent_type="general-purpose") for AI-powered analysis:
 - Error pattern recognition
 - Stack trace analysis with probable causes
 - Component dependency analysis

package/merged-commands/deploy/check.md

@@ -1,5 +1,5 @@
 ---
-description: ✅ Deploy Check — Pre-deployment readiness verification
+description: Deploy Check — Pre-deployment readiness verification
 version: "1.0"
 category: operations
 execution-mode: execute
@@ -11,55 +11,21 @@ execution-mode: execute
 
 ---
 
-## 🛑 PRE-FLIGHT (DO FIRST — BLOCKS PHASE 1)
-
-**LOAD now** (in order; path `./rules/` or `~/.{TOOL}/skills/agent-assistant/rules/`):
-1. ORCHESTRATION-LAWS.md  
-2. ADAPTIVE-EXECUTION.md  
-3. EXECUTION-PROTOCOL.md  
-
-**⛔ Do not run Phase 1 until all are loaded.** Follow **all** rules in those files; they override any conflicting instructions in this file.
-
----
-
-## 🔀 TIERED EXECUTION PROTOCOL (MANDATORY)
-
-> **Reference**: `{RULES_PATH}/ADAPTIVE-EXECUTION.md`
-
-```yaml
-tiered_execution:
-  principle: "Sub-agent FIRST (Tier 1). EMBODY ONLY on system failure (Tier 2)."
-  for_each_phase:
-    TIER_1_MANDATORY: "IF tool exists → MUST use SUB_AGENT_DELEGATION"
-    TIER_2_FALLBACK: "ONLY on system error—NOT complexity/preference/speed"
-  anti_lazy_fallback:
-    - ❌ NEVER use Tier 2 when Tier 1 tool is available
-    - ✅ ALWAYS attempt Tier 1 first when tool exists
-```
+## Execution
+One phase at a time, sequential. Each phase must complete before next begins.
 
 ---
 
-## ⛔ INCREMENTAL EXECUTION (MANDATORY)
-
-One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in one reply. No batching (load only what each phase needs). **Within each phase:** when doing a part, output it in format so user sees what’s happening (announce before doing).
-
----
-
-## 🎭 Phase 1: CODE QUALITY CHECK
+## Phase 1: CODE QUALITY CHECK
 
 | Attribute | Value |
 |-----------|-------|
-| **Agent** | `reviewer` |
+| **Role** | `reviewer` |
 | **Goal** | Verify code quality standards |
 
-### ⚡ TIERED EXECUTION
-
-**TIER 1 (MANDATORY when tool exists):**
-> Invoke runSubagent for `reviewer`. Context: ISOLATED.
+### Delegation
 
-**TIER 2 (FALLBACK on system error only):**
-> Load `{AGENTS_PATH}/reviewer.md`
-> EMBODY [reviewer] — Requires logged system error justification.
+> Task(subagent_type="general-purpose", prompt="You are a reviewer. Verify code quality standards are met. Exit when no critical issues remain, standards are met, and code is approved for deploy.", description="reviewer: Verify code quality standards")
 
 **Exit Criteria:**
 
@@ -69,21 +35,16 @@ One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in
 
 ---
 
-## 🎭 Phase 2: TEST VERIFICATION
+## Phase 2: TEST VERIFICATION
 
 | Attribute | Value |
 |-----------|-------|
-| **Agent** | `tester` |
+| **Role** | `tester` |
 | **Goal** | Verify all tests passing |
 
-### ⚡ TIERED EXECUTION
+### Delegation
 
-**TIER 1 (MANDATORY when tool exists):**
-> Invoke runSubagent for `tester`. Context: ISOLATED.
-
-**TIER 2 (FALLBACK on system error only):**
-> Load `{AGENTS_PATH}/tester.md`
-> EMBODY [tester] — Requires logged system error justification.
+> Task(subagent_type="general-purpose", prompt="You are a tester. Verify all tests are passing with adequate coverage and no flaky tests. Exit when all tests pass, coverage is adequate, and no flaky tests exist.", description="tester: Verify all tests passing")
 
 **Exit Criteria:**
 
@@ -93,21 +54,16 @@ One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in
 
 ---
 
-## 🎭 Phase 3: SECURITY SCAN
+## Phase 3: SECURITY SCAN
 
 | Attribute | Value |
 |-----------|-------|
-| **Agent** | `security-engineer` |
+| **Role** | `security-engineer` |
 | **Goal** | Security vulnerability check |
 
-### ⚡ TIERED EXECUTION
-
-**TIER 1 (MANDATORY when tool exists):**
-> Invoke runSubagent for `security-engineer`. Context: ISOLATED.
+### Delegation
 
-**TIER 2 (FALLBACK on system error only):**
-> Load `{AGENTS_PATH}/security-engineer.md`
-> EMBODY [security-engineer] — Requires logged system error justification.
+> Task(subagent_type="general-purpose", prompt="You are a security-engineer. Perform a security vulnerability check. Exit when no critical vulnerabilities exist, dependencies are secure, and secrets are not exposed.", description="security-engineer: Security vulnerability check")
 
 **Exit Criteria:**
 
@@ -117,21 +73,16 @@ One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in
 
 ---
 
-## 🎭 Phase 4: INFRASTRUCTURE CHECK
+## Phase 4: INFRASTRUCTURE CHECK
 
 | Attribute | Value |
 |-----------|-------|
-| **Agent** | `devops-engineer` |
+| **Role** | `devops-engineer` |
 | **Goal** | Verify infrastructure readiness |
 
-### ⚡ TIERED EXECUTION
-
-**TIER 1 (MANDATORY when tool exists):**
-> Invoke runSubagent for `devops-engineer`. Context: ISOLATED.
+### Delegation
 
-**TIER 2 (FALLBACK on system error only):**
-> Load `{AGENTS_PATH}/devops-engineer.md`
-> EMBODY [devops-engineer] — Requires logged system error justification.
+> Task(subagent_type="general-purpose", prompt="You are a devops-engineer. Verify infrastructure readiness for deployment. Exit when build succeeds, environment is configured, and rollback plan is ready.", description="devops-engineer: Verify infrastructure readiness")
 
 **Exit Criteria:**
 
@@ -145,6 +96,6 @@ One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in
 
 Present readiness report with:
 
-1. ✅ **Ready** → `/deploy:preview` or `/deploy:production`
-2. ❌ **Not Ready** — Issues to address
-3. 🔧 **Fix Issues** → Route to appropriate fix workflow
+1. **Ready** → `/deploy:preview` or `/deploy:production`
+2. **Not Ready** — Issues to address
+3. **Fix Issues** → Route to appropriate fix workflow

package/merged-commands/deploy/preview.md

@@ -1,5 +1,5 @@
 ---
-description: 🔍 Deploy Preview — Staging/Preview deployment
+description: Deploy Preview — Staging/Preview deployment
 version: "1.0"
 category: operations
 execution-mode: execute
@@ -11,55 +11,21 @@ execution-mode: execute
 
 ---
 
-## 🛑 PRE-FLIGHT (DO FIRST — BLOCKS PHASE 1)
-
-**LOAD now** (in order; path `./rules/` or `~/.{TOOL}/skills/agent-assistant/rules/`):
-1. ORCHESTRATION-LAWS.md  
-2. ADAPTIVE-EXECUTION.md  
-3. EXECUTION-PROTOCOL.md  
-
-**⛔ Do not run Phase 1 until all are loaded.** Follow **all** rules in those files; they override any conflicting instructions in this file.
-
----
-
-## 🔀 TIERED EXECUTION PROTOCOL (MANDATORY)
-
-> **Reference**: `{RULES_PATH}/ADAPTIVE-EXECUTION.md`
-
-```yaml
-tiered_execution:
-  principle: "Sub-agent FIRST (Tier 1). EMBODY ONLY on system failure (Tier 2)."
-  for_each_phase:
-    TIER_1_MANDATORY: "IF tool exists → MUST use SUB_AGENT_DELEGATION"
-    TIER_2_FALLBACK: "ONLY on system error—NOT complexity/preference/speed"
-  anti_lazy_fallback:
-    - ❌ NEVER use Tier 2 when Tier 1 tool is available
-    - ✅ ALWAYS attempt Tier 1 first when tool exists
-```
+## Execution
+One phase at a time, sequential. Each phase must complete before next begins.
 
 ---
 
-## ⛔ INCREMENTAL EXECUTION (MANDATORY)
-
-One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in one reply. No batching (load only what each phase needs). **Within each phase:** when doing a part, output it in format so user sees what’s happening (announce before doing).
-
----
-
-## 🎭 Phase 1: READINESS CHECK
+## Phase 1: READINESS CHECK
 
 | Attribute | Value |
 |-----------|-------|
-| **Agent** | `devops-engineer` |
+| **Role** | `devops-engineer` |
 | **Goal** | Quick deployment readiness |
 
-### ⚡ TIERED EXECUTION
+### Delegation
 
-**TIER 1 (MANDATORY when tool exists):**
-> Invoke runSubagent for `devops-engineer`. Context: ISOLATED.
-
-**TIER 2 (FALLBACK on system error only):**
-> Load `{AGENTS_PATH}/devops-engineer.md`
-> EMBODY [devops-engineer] — Requires logged system error justification.
+> Task(subagent_type="general-purpose", prompt="You are a devops-engineer. Perform a quick deployment readiness check. Exit when build passes, tests pass, and no blockers exist.", description="devops-engineer: Quick deployment readiness")
 
 **Exit Criteria:**
 
@@ -69,21 +35,16 @@ One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in
 
 ---
 
-## 🎭 Phase 2: DEPLOY
+## Phase 2: DEPLOY
 
 | Attribute | Value |
 |-----------|-------|
-| **Agent** | `devops-engineer` |
+| **Role** | `devops-engineer` |
 | **Goal** | Deploy to preview environment |
 
-### ⚡ TIERED EXECUTION
-
-**TIER 1 (MANDATORY when tool exists):**
-> Invoke runSubagent for `devops-engineer`. Context: ISOLATED.
+### Delegation
 
-**TIER 2 (FALLBACK on system error only):**
-> Load `{AGENTS_PATH}/devops-engineer.md`
-> EMBODY [devops-engineer] — Requires logged system error justification.
+> Task(subagent_type="general-purpose", prompt="You are a devops-engineer. Deploy to preview environment. Exit when deployment is successful and environment is accessible.", description="devops-engineer: Deploy to preview environment")
 
 **Exit Criteria:**
 
@@ -92,21 +53,16 @@ One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in
 
 ---
 
-## 🎭 Phase 3: VERIFICATION
+## Phase 3: VERIFICATION
 
 | Attribute | Value |
 |-----------|-------|
-| **Agent** | `devops-engineer` |
+| **Role** | `devops-engineer` |
 | **Goal** | Verify deployment health |
 
-### ⚡ TIERED EXECUTION
-
-**TIER 1 (MANDATORY when tool exists):**
-> Invoke runSubagent for `devops-engineer`. Context: ISOLATED.
+### Delegation
 
-**TIER 2 (FALLBACK on system error only):**
-> Load `{AGENTS_PATH}/devops-engineer.md`
-> EMBODY [devops-engineer] — Requires logged system error justification.
+> Task(subagent_type="general-purpose", prompt="You are a devops-engineer. Verify deployment health. Exit when health checks pass, core functionality is verified, and preview URL is accessible.", description="devops-engineer: Verify deployment health")
 
 **Exit Criteria:**
 
@@ -120,6 +76,6 @@ One phase at a time, each phase independent: Phase 1 → then Phase 2 → … in
 
 Present deployment result with:
 
-1. ✅ **Success** — Preview ready for testing
-2. 🚀 **Promote** → `/deploy:production`
-3. ⏪ **Rollback** → `/deploy:rollback`
+1. **Success** — Preview ready for testing
+2. **Promote** → `/deploy:production`
+3. **Rollback** → `/deploy:rollback`