@ngxtm/devkit 3.19.0 → 3.20.0

package/skills/tdd-workflows-tdd-red/SKILL.md

@@ -35,7 +35,7 @@ Write comprehensive failing tests following TDD red phase principles.
 
 ## Role
 
-Generate failing tests using Task tool with subagent_type="unit-testing::test-automator".
+Generate failing tests using Task tool with subagent_type="general-purpose".
 
 ## Prompt Template
 

package/skills/tdd-workflows-tdd-refactor/SKILL.md

@@ -28,7 +28,7 @@ Refactor code with confidence using comprehensive test safety net:
 
 ## Usage
 
-Use Task tool with subagent_type="tdd-orchestrator" to perform safe refactoring.
+Use Task tool with subagent_type="general-purpose" to perform safe refactoring.
 
 Prompt: "Refactor this code while keeping all tests green: $ARGUMENTS. Apply TDD refactor phase:
 

package/skills/typescript-expert/SKILL.md

@@ -27,7 +27,7 @@ You are an advanced TypeScript expert with deep, practical knowledge of type-lev
    - Type performance profiling or compiler internals → typescript-type-expert
 
    Example to output:
-   "This requires deep bundler expertise. Please invoke: 'Use the typescript-build-expert subagent.' Stopping here."
+   "This requires deep bundler expertise. Please invoke: 'Use the typescript-build-expert Task agent.' Stopping here."
 
 1. Analyze project setup comprehensively:
    

package/skills/writing-plans/SKILL.md

@@ -102,16 +102,16 @@ After saving the plan, offer execution choice:
 
 **"Plan complete and saved to `docs/plans/<filename>.md`. Two execution options:**
 
-**1. Subagent-Driven (this session)** - I dispatch fresh subagent per task, review between tasks, fast iteration
+**1. Task Agent-Driven (this session)** - I dispatch fresh Task agent per task, review between tasks, fast iteration
 
 **2. Parallel Session (separate)** - Open new session with executing-plans, batch execution with checkpoints
 
 **Which approach?"**
 
-**If Subagent-Driven chosen:**
+**If Task Agent-Driven chosen:**
 - **REQUIRED SUB-SKILL:** Use superpowers:subagent-driven-development
 - Stay in this session
-- Fresh subagent per task + code review
+- Fresh Task agent per task + code review
 
 **If Parallel Session chosen:**
 - Guide them to open new session in worktree

package/skills/writing-skills/SKILL.md

@@ -11,7 +11,7 @@ description: Use when creating new skills, editing existing skills, or verifying
 
 **Personal skills live in agent-specific directories (`~/.claude/skills` for Claude Code, `~/.codex/skills` for Codex)** 
 
-You write test cases (pressure scenarios with subagents), watch them fail (baseline behavior), write the skill (documentation), watch tests pass (agents comply), and refactor (close loopholes).
+You write test cases (pressure scenarios with Task agents), watch them fail (baseline behavior), write the skill (documentation), watch tests pass (agents comply), and refactor (close loopholes).
 
 **Core principle:** If you didn't watch an agent fail without the skill, you don't know if the skill teaches the right thing.
 
@@ -31,7 +31,7 @@ A **skill** is a reference guide for proven techniques, patterns, or tools. Skil
 
 | TDD Concept | Skill Creation |
 |-------------|----------------|
-| **Test case** | Pressure scenario with subagent |
+| **Test case** | Pressure scenario with Task agent |
 | **Production code** | Skill document (SKILL.md) |
 | **Test fails (RED)** | Agent violates rule without skill (baseline) |
 | **Test passes (GREEN)** | Agent complies with skill present |
@@ -159,7 +159,7 @@ When the description was changed to just "Use when executing implementation plan
 
 ```yaml
 # ❌ BAD: Summarizes workflow - Claude may follow this instead of reading skill
-description: Use when executing plans - dispatches subagent per task with code review between tasks
+description: Use when executing plans - dispatches Task agent per task with code review between tasks
 
 # ❌ BAD: Too much process detail
 description: Use for TDD - write test first, watch it fail, write minimal code, refactor
@@ -233,11 +233,11 @@ search-conversations supports multiple modes and filters. Run --help for details
 **Use cross-references:**
 ```markdown
 # ❌ BAD: Repeat workflow details
-When searching, dispatch subagent with template...
+When searching, dispatch Task agent with template...
 [20 lines of repeated instructions]
 
 # ✅ GOOD: Reference other skill
-Always use subagents (50-100x context savings). REQUIRED: Use [other-skill-name] for workflow.
+Always use Task agents (50-100x context savings). REQUIRED: Use [other-skill-name] for workflow.
 ```
 
 **Compress examples:**
@@ -245,12 +245,12 @@ Always use subagents (50-100x context savings). REQUIRED: Use [other-skill-name]
 # ❌ BAD: Verbose example (42 words)
 your human partner: "How did we handle authentication errors in React Router before?"
 You: I'll search past conversations for React Router authentication patterns.
-[Dispatch subagent with search query: "React Router authentication error handling 401"]
+[Dispatch Task agent with search query: "React Router authentication error handling 401"]
 
 # ✅ GOOD: Minimal example (20 words)
 Partner: "How did we handle auth errors in React Router?"
 You: Searching...
-[Dispatch subagent → synthesis]
+[Dispatch Task agent → synthesis]
 ```
 
 **Eliminate redundancy:**
@@ -536,7 +536,7 @@ Follow the TDD cycle:
 
 ### RED: Write Failing Test (Baseline)
 
-Run pressure scenario with subagent WITHOUT the skill. Document exact behavior:
+Run pressure scenario with Task agent WITHOUT the skill. Document exact behavior:
 - What choices did they make?
 - What rationalizations did they use (verbatim)?
 - Which pressures triggered violations?

package/skills/writing-skills/examples/CLAUDE_MD_TESTING.md

@@ -181,7 +181,7 @@ For each variant:
 
 ## Next Steps
 
-1. Create subagent test harness
+1. Create Task agent test harness
 2. Run NULL baseline on all 4 scenarios
 3. Test each variant on same scenarios
 4. Compare compliance rates

package/skills/writing-skills/references/cso/README.md

@@ -75,7 +75,7 @@ When searching, dispatch agent with template...
 
 # ✅ GOOD: Reference other skill
 
-Use subagents for searches. See [delegating-to-subagents] for workflow.
+Use Task agents for searches. See [delegating-to-subagents] for workflow.
 ```
 
 **3. Compress examples**:
@@ -85,13 +85,13 @@ Use subagents for searches. See [delegating-to-subagents] for workflow.
 
 Partner: "How did we handle auth errors in React Router?"
 You: I'll search past conversations for patterns.
-[Dispatch subagent with query: "React Router authentication error handling 401"]
+[Dispatch Task agent with query: "React Router authentication error handling 401"]
 
 # ✅ GOOD: Minimal (20 words)
 
 Partner: "Auth errors in React Router?"
 You: Searching...
-[Dispatch subagent → synthesis]
+[Dispatch Task agent → synthesis]
 ```
 
 ## Keyword Strategy

package/skills/writing-skills/testing-skills-with-subagents.md

@@ -1,4 +1,4 @@
-# Testing Skills With Subagents
+# Testing Skills With Task Agents
 
 **Load this reference when:** creating or editing skills, before deployment, to verify they work under pressure and resist rationalization.