agentic-code 0.5.1 → 0.6.0

package/.agents/skills/testing/references/typescript.md

@@ -0,0 +1,134 @@
+# TypeScript/Vitest Testing Rules
+
+## Test Framework
+- **Vitest**: This project uses Vitest
+- Test imports: `import { describe, it, expect, beforeEach, vi } from 'vitest'`
+- Mock creation: Use `vi.mock()`
+
+## Directory Structure
+
+**File structure:**
+- src/application/services/service.ts: Main service file
+- src/application/services/__tests__/service.test.ts: Unit tests
+- src/application/services/__tests__/service.int.test.ts: Integration tests
+
+**Naming Conventions:**
+- Test files: `{target-file-name}.test.ts`
+- Integration test files: `{target-file-name}.int.test.ts`
+
+## Cross-functional E2E Test Patterns
+
+```typescript
+describe('Cross-functional E2E Tests', () => {
+  // Pattern 1: Baseline → Change → Verify
+  it('should maintain existing behavior after new feature', async () => {
+    // 1. Capture baseline
+    const baseline = await testExistingFeature()
+
+    // 2. Enable new feature
+    await enableNewFeature()
+
+    // 3. Verify continuity
+    const result = await testExistingFeature()
+    expect(result).toEqual(baseline)
+    expect(result.responseTime).toBeLessThan(
+      baseline.responseTime * 1.2 // Project-specific threshold
+    )
+  })
+
+  // Pattern 2: Data integrity across features
+  it('should preserve data integrity', async () => {
+    const data = await createTestData()
+    await newFeatureOperation(data.id)
+
+    const retrieved = await existingFeatureGet(data.id)
+    expect(retrieved).toEqual(data) // No unexpected mutations
+  })
+})
+```
+
+**Note**: LLM outputs naturally vary - test behavior, not exact matches
+
+## Test Helper Usage Examples
+
+```typescript
+// ✅ Recommended: Utilize builder pattern
+const testData = new TestDataBuilder()
+  .withDefaults()
+  .withName('Test User')
+  .build()
+
+// ✅ Recommended: Custom assertions
+function assertValidUser(user: unknown): asserts user is User {
+  // Validation logic
+}
+
+// ❌ Avoid: Individual implementation of duplicate complex mocks
+```
+
+## Test Granularity Examples
+
+```typescript
+// ✅ Test observable behavior
+expect(calculatePrice(100, 0.1)).toBe(110)
+
+// ❌ Test implementation details (as any access)
+expect((calculator as any).taxRate).toBe(0.1)
+expect((service as any).validate(input)).toBe(true)
+```
+
+## Mock Type Safety Enforcement
+
+### Minimal Type Definition Requirements
+```typescript
+// ✅ Only required parts
+type TestRepo = Pick<Repository, 'find' | 'save'>
+const mock: TestRepo = { find: vi.fn(), save: vi.fn() }
+
+// Only when absolutely necessary, with clear justification
+const sdkMock = {
+  call: vi.fn()
+} as unknown as ExternalSDK // Complex external SDK type structure
+```
+
+## Basic Vitest Example
+
+```typescript
+import { describe, it, expect, beforeEach, vi } from 'vitest'
+
+// Mock setup example
+vi.mock('./userService', () => ({
+  getUserById: vi.fn(),
+  updateUser: vi.fn()
+}))
+
+describe('ComponentName', () => {
+  it('should follow AAA pattern', () => {
+    // Arrange
+    const input = 'test'
+
+    // Act
+    const result = someFunction(input)
+
+    // Assert
+    expect(result).toBe('expected')
+  })
+})
+```
+
+## Quality Check Commands [MANDATORY for VERIFY phase]
+
+**ALL TypeScript/JavaScript commands MUST pass with 0 errors before task completion:**
+
+```bash
+npm test              # MUST pass all tests
+npm run build        # MUST build successfully
+npm run lint         # MUST have 0 lint errors
+npm run type-check   # MUST have 0 type errors
+```
+
+**ENFORCEMENT:**
+- Run ALL applicable commands listed above
+- Fix ANY errors or warnings before marking task complete
+- If command doesn't exist in package.json, skip that specific command
+- Document which commands were run in task completion

package/.agents/{rules/core/testing-strategy.md → skills/testing-strategy/SKILL.md}

@@ -1,3 +1,10 @@
+---
+name: testing-strategy
+description: |
+  ROI-based test selection framework with calculation formula, critical user journey definitions, and test prioritization guidelines.
+  Use when: designing test strategy, selecting which tests to write, calculating test ROI, or prioritizing test coverage.
+---
+
 # Test Strategy: ROI-Based Selection
 
 ## Core Principle: Maximum Coverage, Minimum Tests

package/.agents/tasks/acceptance-test-generation.md

@@ -2,59 +2,59 @@
 
 ## Required Rules [MANDATORY - MUST BE ACTIVE]
 
-**RULE AVAILABILITY VERIFICATION:**
-1. [LOAD IF NOT ACTIVE] `.agents/rules/language/testing.md`
-2. [LOAD IF NOT ACTIVE] `.agents/rules/core/documentation-criteria.md`
-3. [LOAD IF NOT ACTIVE] `.agents/rules/core/testing-strategy.md`
-4. [LOAD IF NOT ACTIVE] `.agents/rules/core/integration-e2e-testing.md`
+**SKILL AVAILABILITY VERIFICATION:**
+1. [LOAD IF NOT ACTIVE] `.agents/skills/testing/SKILL.md`
+2. [LOAD IF NOT ACTIVE] `.agents/skills/documentation-criteria/SKILL.md`
+3. [LOAD IF NOT ACTIVE] `.agents/skills/testing-strategy/SKILL.md`
+4. [LOAD IF NOT ACTIVE] `.agents/skills/integration-e2e-testing/SKILL.md`
 
 **LOADING PROTOCOL:**
-- STEP 1: CHECK if language/testing.md is active in working memory
-- STEP 2: If language/testing.md NOT active → Execute BLOCKING READ
-- STEP 3: CHECK if documentation-criteria.md is active in working memory
-- STEP 4: If documentation-criteria.md NOT active → Execute BLOCKING READ
-- STEP 5: CHECK if testing-strategy.md is active in working memory
-- STEP 6: If testing-strategy.md NOT active → Execute BLOCKING READ
-- STEP 7: CHECK if integration-e2e-testing.md is active in working memory
-- STEP 8: If integration-e2e-testing.md NOT active → Execute BLOCKING READ
-- STEP 9: CONFIRM all required rules active before proceeding
-
-## Plan Injection Requirement [MANDATORY]
-
-**Upon reading this file, IMMEDIATELY inject to work plan:**
+- STEP 1: CHECK if testing/SKILL.md is active in working memory
+- STEP 2: If testing/SKILL.md NOT active → Execute BLOCKING READ
+- STEP 3: CHECK if documentation-criteria/SKILL.md is active in working memory
+- STEP 4: If documentation-criteria/SKILL.md NOT active → Execute BLOCKING READ
+- STEP 5: CHECK if testing-strategy/SKILL.md is active in working memory
+- STEP 6: If testing-strategy/SKILL.md NOT active → Execute BLOCKING READ
+- STEP 7: CHECK if integration-e2e-testing/SKILL.md is active in working memory
+- STEP 8: If integration-e2e-testing/SKILL.md NOT active → Execute BLOCKING READ
+- STEP 9: CONFIRM all required skills active before proceeding
+
+## Task Tracking Requirement [MANDATORY]
+
+**Upon reading this file, IMMEDIATELY add to your internal task management (Task List):**
 1. All BLOCKING READs identified in Loading Protocol above:
-   - `.agents/rules/language/testing.md` (if not active)
-   - `.agents/rules/core/documentation-criteria.md` (if not active)
-   - `.agents/rules/core/testing-strategy.md` (if not active)
-   - `.agents/rules/core/integration-e2e-testing.md` (if not active)
+   - `.agents/skills/testing/SKILL.md` (if not active)
+   - `.agents/skills/documentation-criteria/SKILL.md` (if not active)
+   - `.agents/skills/testing-strategy/SKILL.md` (if not active)
+   - `.agents/skills/integration-e2e-testing/SKILL.md` (if not active)
 2. Mark each with "[From acceptance-test-generation.md]" source tag
-3. Show evidence of injection:
+3. Show evidence:
    ```
-   [PLAN INJECTION FROM acceptance-test-generation.md]
-   Injected to work plan:
-   ✓ BLOCKING READ: language/testing.md - testing standards
-   ✓ BLOCKING READ: documentation-criteria.md - document analysis
-   ✓ BLOCKING READ: testing-strategy.md - ROI-based test selection
-   ✓ BLOCKING READ: integration-e2e-testing.md - integration/E2E test design
+   [TASK TRACKING FROM acceptance-test-generation.md]
+   Added to Task List:
+   ✓ BLOCKING READ: testing/SKILL.md - testing standards
+   ✓ BLOCKING READ: documentation-criteria/SKILL.md - document analysis
+   ✓ BLOCKING READ: testing-strategy/SKILL.md - ROI-based test selection
+   ✓ BLOCKING READ: integration-e2e-testing/SKILL.md - integration/E2E test design
    Status: VERIFIED
    ```
 
-**ENFORCEMENT:** Cannot proceed without Plan Injection evidence
+**ENFORCEMENT:** Cannot proceed without Task Tracking evidence
 
 **EVIDENCE REQUIRED:**
 ```
-Rule Status Verification:
-✓ language/testing.md - ACTIVE
-✓ documentation-criteria.md - ACTIVE
-✓ testing-strategy.md - ACTIVE
-✓ integration-e2e-testing.md - ACTIVE
+Skill Status Verification:
+✓ testing/SKILL.md - ACTIVE
+✓ documentation-criteria/SKILL.md - ACTIVE
+✓ testing-strategy/SKILL.md - ACTIVE
+✓ integration-e2e-testing/SKILL.md - ACTIVE
 ```
 
 ## Phase Entry Gate [BLOCKING - SYSTEM HALT IF VIOLATED]
 
 **CHECKPOINT: System CANNOT proceed until ALL boxes checked:**
-☐ [VERIFIED] Plan Injection completed (from acceptance-test-generation.md)
-☐ [VERIFIED] Work plan contains ALL BLOCKING READs from this file
+☐ [VERIFIED] Task Tracking completed (from acceptance-test-generation.md)
+☐ [VERIFIED] Task List contains ALL BLOCKING READs from this file
 ☐ [VERIFIED] Design document exists and contains Acceptance Criteria section
 ☐ [VERIFIED] Project testing structure investigated (existing test patterns)
 ☐ [VERIFIED] Test framework configuration confirmed
@@ -244,7 +244,7 @@ Where:
 - Test Level Cost: Unit=3, Integration=11, E2E=38
 ```
 
-**See**: `.agents/rules/core/testing-strategy.md` for detailed ROI framework
+**See**: `.agents/skills/testing-strategy/SKILL.md` for detailed ROI framework
 
 **4.2 Deduplication Check**
 

package/.agents/tasks/code-review.md

@@ -2,16 +2,16 @@
 
 ## Required Rules [MANDATORY - MUST BE ACTIVE]
 
-**RULE AVAILABILITY VERIFICATION:**
-1. [LOAD IF NOT ACTIVE] `.agents/rules/language/rules.md`
-2. [LOAD IF NOT ACTIVE] `.agents/rules/core/ai-development-guide.md`
+**SKILL AVAILABILITY VERIFICATION:**
+1. [LOAD IF NOT ACTIVE] `.agents/skills/coding-rules/SKILL.md`
+2. [LOAD IF NOT ACTIVE] `.agents/skills/ai-development-guide/SKILL.md`
 
 **LOADING PROTOCOL:**
-- STEP 1: CHECK if `.agents/rules/language/rules.md` is active in working memory
+- STEP 1: CHECK if `.agents/skills/coding-rules/SKILL.md` is active in working memory
 - STEP 2: If NOT active → Execute BLOCKING READ
-- STEP 3: CHECK if `.agents/rules/core/ai-development-guide.md` is active in working memory
+- STEP 3: CHECK if `.agents/skills/ai-development-guide/SKILL.md` is active in working memory
 - STEP 4: If NOT active → Execute BLOCKING READ
-- STEP 5: CONFIRM all required rules active before proceeding
+- STEP 5: CONFIRM all required skills active before proceeding
 
 ## Purpose
 

package/.agents/tasks/implementation.md

@@ -2,54 +2,54 @@
 
 ## Required Rules [MANDATORY - MUST BE ACTIVE]
 
-**RULE AVAILABILITY VERIFICATION:**
-1. [VERIFY ACTIVE] `.agents/rules/core/metacognition.md`
-2. [LOAD IF NOT ACTIVE] `.agents/rules/language/rules.md`
-3. [LOAD IF NOT ACTIVE] `.agents/rules/language/testing.md`
+**SKILL AVAILABILITY VERIFICATION:**
+1. [VERIFY ACTIVE] `.agents/skills/metacognition/SKILL.md`
+2. [LOAD IF NOT ACTIVE] `.agents/skills/coding-rules/SKILL.md`
+3. [LOAD IF NOT ACTIVE] `.agents/skills/testing/SKILL.md`
 
 **LOADING PROTOCOL:**
-- STEP 1: VERIFY metacognition.md is active from initial session setup
-- STEP 2: CHECK if language/rules.md is active in working memory
-- STEP 3: If language/rules.md NOT active → Execute BLOCKING READ
-- STEP 4: CHECK if testing.md is active in working memory
-- STEP 5: If testing.md NOT active → Execute BLOCKING READ
-- STEP 6: CONFIRM all rules active before writing ANY code
+- STEP 1: VERIFY metacognition/SKILL.md is active from initial session setup
+- STEP 2: CHECK if coding-rules/SKILL.md is active in working memory
+- STEP 3: If coding-rules/SKILL.md NOT active → Execute BLOCKING READ
+- STEP 4: CHECK if testing/SKILL.md is active in working memory
+- STEP 5: If testing/SKILL.md NOT active → Execute BLOCKING READ
+- STEP 6: CONFIRM all skills active before writing ANY code
 
-## Plan Injection Requirement [MANDATORY]
+## Task Tracking Requirement [MANDATORY]
 
-**Upon reading this file, IMMEDIATELY inject to work plan:**
+**Upon reading this file, IMMEDIATELY add to your internal task management (Task List):**
 1. All BLOCKING READs identified in Loading Protocol above:
-   - `.agents/rules/language/rules.md` (if not active)
-   - `.agents/rules/language/testing.md` (if not active)
+   - `.agents/skills/coding-rules/SKILL.md` (if not active)
+   - `.agents/skills/testing/SKILL.md` (if not active)
 2. Mark each with "[From implementation.md]" source tag
-3. Show evidence of injection:
+3. Show evidence:
    ```
-   [PLAN INJECTION FROM implementation.md]
-   Injected to work plan:
-   ✓ BLOCKING READ: language/rules.md - development standards
-   ✓ BLOCKING READ: language/testing.md - TDD process
+   [TASK TRACKING FROM implementation.md]
+   Added to Task List:
+   ✓ BLOCKING READ: coding-rules/SKILL.md - development standards
+   ✓ BLOCKING READ: testing/SKILL.md - TDD process
    Status: VERIFIED
    ```
 
-**ENFORCEMENT:** Cannot proceed without Plan Injection evidence
+**ENFORCEMENT:** Cannot proceed without Task Tracking evidence
 
 **EVIDENCE REQUIRED:**
 ```
-Rule Status Verification:
-✓ metacognition.md - ACTIVE (from session setup)
-✓ language/rules.md - ACTIVE (loaded/verified)
-✓ language/testing.md - ACTIVE (loaded/verified)
+Skill Status Verification:
+✓ metacognition/SKILL.md - ACTIVE (from session setup)
+✓ coding-rules/SKILL.md - ACTIVE (loaded/verified)
+✓ testing/SKILL.md - ACTIVE (loaded/verified)
 ```
 
 ## Phase Entry Gate [BLOCKING - SYSTEM HALT IF VIOLATED]
 
 **CHECKPOINT: System CANNOT write ANY CODE until ALL boxes checked:**
 ☐ [VERIFIED] THIS FILE (`implementation.md`) has been READ and is active
-☐ [VERIFIED] Plan Injection completed (from implementation.md Plan Injection Requirement)
+☐ [VERIFIED] Task Tracking completed (from implementation.md Task Tracking Requirement)
 ☐ [VERIFIED] All required rules listed above are LOADED and active
-☐ [VERIFIED] Work plan EXISTS with task definitions
-☐ [VERIFIED] Work plan contains ALL BLOCKING READs from this file
-☐ [VERIFIED] Current task identified from work plan
+☐ [VERIFIED] Work Plan document EXISTS with task definitions
+☐ [VERIFIED] Task List contains ALL BLOCKING READs from this file
+☐ [VERIFIED] Current task identified from Work Plan document
 ☐ [VERIFIED] TDD process understood (Red-Green-Refactor-Verify)
 ☐ [VERIFIED] SESSION_BASELINE_DATE established and active
 
@@ -99,18 +99,18 @@ Implement code using TDD process.
 
 **3. REFACTOR Phase - Improve code**
    - Clean up implementation
-   - Apply coding standards from language/rules.md
+   - Apply coding standards from coding-rules/SKILL.md
    - Ensure test still passes
 
 **4. VERIFY Phase - Quality checks**
-   - Execute ALL commands from language/testing.md Quality Check Commands section
+   - Execute ALL commands from testing/SKILL.md Quality Check Commands section
    - Confirm ALL checks pass with 0 errors
    - Ready for commit
 
 **5. COMMIT Phase - Version control [MANDATORY]**
    - Stage changes for current implementation
    - Create commit with descriptive message
-   - Commit message format: "feat: [what was implemented]" or follow work plan task name if available
+   - Commit message format: "feat: [what was implemented]" or follow Work Plan task name if available
    - ENFORCEMENT: Implementation task NOT complete until committed
    - NOTE: Skip if user explicitly says "don't commit"
 
@@ -157,7 +157,7 @@ Regardless of language:
 
 ### 6. Testing Approach
 
-**REFERENCE `.agents/rules/language/testing.md` for complete testing strategy including:**
+**REFERENCE `.agents/skills/testing/SKILL.md` for complete testing strategy including:**
 - Test types and granularity
 - Test-first development process
 - Coverage requirements
@@ -188,8 +188,8 @@ Always:
 
 Essential completion requirements:
 □ ALL quality standards from quality-assurance.md satisfied
-□ ALL language requirements from language/rules.md met
-□ ALL testing requirements from testing.md completed
+□ ALL language requirements from coding-rules/SKILL.md met
+□ ALL testing requirements from testing/SKILL.md completed
 □ Work plan task checkbox updated to [✓]
 □ Metacognition "After Completion" executed
 

package/.agents/tasks/integration-test-review.md

@@ -2,16 +2,16 @@
 
 ## Required Rules [MANDATORY - MUST BE ACTIVE]
 
-**RULE AVAILABILITY VERIFICATION:**
-1. [LOAD IF NOT ACTIVE] `.agents/rules/language/testing.md`
-2. [LOAD IF NOT ACTIVE] `.agents/rules/core/integration-e2e-testing.md`
+**SKILL AVAILABILITY VERIFICATION:**
+1. [LOAD IF NOT ACTIVE] `.agents/skills/testing/SKILL.md`
+2. [LOAD IF NOT ACTIVE] `.agents/skills/integration-e2e-testing/SKILL.md`
 
 **LOADING PROTOCOL:**
-- STEP 1: CHECK if language/testing.md is active in working memory
-- STEP 2: If language/testing.md NOT active → Execute BLOCKING READ
-- STEP 3: CHECK if integration-e2e-testing.md is active in working memory
-- STEP 4: If integration-e2e-testing.md NOT active → Execute BLOCKING READ
-- STEP 5: CONFIRM all required rules active before proceeding
+- STEP 1: CHECK if testing/SKILL.md is active in working memory
+- STEP 2: If testing/SKILL.md NOT active → Execute BLOCKING READ
+- STEP 3: CHECK if integration-e2e-testing/SKILL.md is active in working memory
+- STEP 4: If integration-e2e-testing/SKILL.md NOT active → Execute BLOCKING READ
+- STEP 5: CONFIRM all required skills active before proceeding
 
 ## Purpose
 

package/.agents/tasks/prd-creation.md

@@ -2,45 +2,45 @@
 
 ## Required Rules [MANDATORY - MUST BE ACTIVE]
 
-**RULE AVAILABILITY VERIFICATION:**
-1. [VERIFY ACTIVE] `.agents/rules/core/metacognition.md` (loaded at session start)
-2. [LOAD IF NOT ACTIVE] `.agents/rules/core/documentation-criteria.md`
+**SKILL AVAILABILITY VERIFICATION:**
+1. [VERIFY ACTIVE] `.agents/skills/metacognition/SKILL.md` (loaded at session start)
+2. [LOAD IF NOT ACTIVE] `.agents/skills/documentation-criteria/SKILL.md`
 
 **LOADING PROTOCOL:**
-- STEP 1: VERIFY metacognition.md is active from initial session setup
-- STEP 2: CHECK if documentation-criteria.md is active in working memory
-- STEP 3: If documentation-criteria.md NOT active → Execute BLOCKING READ
-- STEP 4: CONFIRM all rules active before proceeding
+- STEP 1: VERIFY metacognition/SKILL.md is active from initial session setup
+- STEP 2: CHECK if documentation-criteria/SKILL.md is active in working memory
+- STEP 3: If documentation-criteria/SKILL.md NOT active → Execute BLOCKING READ
+- STEP 4: CONFIRM all skills active before proceeding
 
-## Plan Injection Requirement [MANDATORY]
+## Task Tracking Requirement [MANDATORY]
 
-**Upon reading this file, IMMEDIATELY inject to work plan:**
+**Upon reading this file, IMMEDIATELY add to your internal task management (Task List):**
 1. All BLOCKING READs identified in Loading Protocol above:
-   - `.agents/rules/core/documentation-criteria.md` (if not active)
+   - `.agents/skills/documentation-criteria/SKILL.md` (if not active)
 2. Mark each with "[From prd-creation.md]" source tag
-3. Show evidence of injection:
+3. Show evidence:
    ```
-   [PLAN INJECTION FROM prd-creation.md]
-   Injected to work plan:
-   ✓ BLOCKING READ: documentation-criteria.md - PRD creation criteria
+   [TASK TRACKING FROM prd-creation.md]
+   Added to Task List:
+   ✓ BLOCKING READ: documentation-criteria/SKILL.md - PRD creation criteria
    Status: VERIFIED
    ```
 
-**ENFORCEMENT:** Cannot proceed without Plan Injection evidence
+**ENFORCEMENT:** Cannot proceed without Task Tracking evidence
 
 **EVIDENCE REQUIRED:**
 ```
-Rule Status Verification:
-✓ metacognition.md - ACTIVE (from session setup)
-✓ documentation-criteria.md - ACTIVE (loaded/verified)
+Skill Status Verification:
+✓ metacognition/SKILL.md - ACTIVE (from session setup)
+✓ documentation-criteria/SKILL.md - ACTIVE (loaded/verified)
 ```
 
 ## Phase Entry Gate [BLOCKING - SYSTEM HALT IF VIOLATED]
 
 **CHECKPOINT: System CANNOT proceed until ALL boxes checked:**
 ☐ [VERIFIED] THIS FILE (`prd-creation.md`) has been READ and is active
-☐ [VERIFIED] Plan Injection completed (from prd-creation.md Plan Injection Requirement)
-☐ [VERIFIED] Work plan contains ALL BLOCKING READs from this file
+☐ [VERIFIED] Task Tracking completed (from prd-creation.md Task Tracking Requirement)
+☐ [VERIFIED] Task List contains ALL BLOCKING READs from this file
 ☐ [VERIFIED] Project structure confirmed
 ☐ [VERIFIED] Existing PRDs investigation COMPLETED with evidence
 ☐ [VERIFIED] Related documentation search EXECUTED with results documented

package/.agents/tasks/quality-assurance.md

@@ -2,56 +2,56 @@
 
 ## Required Rules [MANDATORY - MUST BE ACTIVE]
 
-**RULE AVAILABILITY VERIFICATION:**
-1. [LOAD IF NOT ACTIVE] `.agents/rules/language/rules.md`
-2. [LOAD IF NOT ACTIVE] `.agents/rules/language/testing.md`
+**SKILL AVAILABILITY VERIFICATION:**
+1. [LOAD IF NOT ACTIVE] `.agents/skills/coding-rules/SKILL.md`
+2. [LOAD IF NOT ACTIVE] `.agents/skills/testing/SKILL.md`
 
 **LOADING PROTOCOL:**
-- STEP 1: CHECK if language/rules.md is active in working memory
-- STEP 2: If language/rules.md NOT active → Execute BLOCKING READ
-- STEP 3: CHECK if testing.md is active in working memory
-- STEP 4: If testing.md NOT active → Execute BLOCKING READ
-- STEP 5: CONFIRM all rules active before executing quality gates
+- STEP 1: CHECK if coding-rules/SKILL.md is active in working memory
+- STEP 2: If coding-rules/SKILL.md NOT active → Execute BLOCKING READ
+- STEP 3: CHECK if testing/SKILL.md is active in working memory
+- STEP 4: If testing/SKILL.md NOT active → Execute BLOCKING READ
+- STEP 5: CONFIRM all skills active before executing quality gates
 
 **CRITICAL**: Cannot execute quality checks until ALL required rules confirmed active
 
-## Plan Injection Requirement [MANDATORY]
+## Task Tracking Requirement [MANDATORY]
 
-**Upon reading this file, IMMEDIATELY inject to work plan:**
+**Upon reading this file, IMMEDIATELY add to your internal task management (Task List):**
 1. All BLOCKING READs identified in Loading Protocol above:
-   - `.agents/rules/language/rules.md` (if not active)
-   - `.agents/rules/language/testing.md` (if not active)
+   - `.agents/skills/coding-rules/SKILL.md` (if not active)
+   - `.agents/skills/testing/SKILL.md` (if not active)
 2. Mark each with "[From quality-assurance.md]" source tag
-3. Show evidence of injection:
+3. Show evidence:
    ```
-   [PLAN INJECTION FROM quality-assurance.md]
-   Injected to work plan:
-   ✓ BLOCKING READ: language/rules.md - quality standards
-   ✓ BLOCKING READ: language/testing.md - testing requirements
+   [TASK TRACKING FROM quality-assurance.md]
+   Added to Task List:
+   ✓ BLOCKING READ: coding-rules/SKILL.md - quality standards
+   ✓ BLOCKING READ: testing/SKILL.md - testing requirements
    Status: VERIFIED
    ```
 
-**ENFORCEMENT:** Cannot proceed without Plan Injection evidence
+**ENFORCEMENT:** Cannot proceed without Task Tracking evidence
 
 **EVIDENCE REQUIRED:**
 ```
-Rule Status Verification:
-✓ language/rules.md - ACTIVE (loaded/verified)
-✓ testing.md - ACTIVE (loaded/verified)
+Skill Status Verification:
+✓ coding-rules/SKILL.md - ACTIVE (loaded/verified)
+✓ testing/SKILL.md - ACTIVE (loaded/verified)
 ```
 
 ## Task Completion Gate [STRICT ENFORCEMENT - NO EXCEPTIONS]
 
 **CANNOT mark task as complete until ALL quality checks pass:**
-□ Plan Injection completed (from quality-assurance.md Plan Injection Requirement)
-□ Work plan contains ALL BLOCKING READs from this file
+□ Task Tracking completed (from quality-assurance.md Task Tracking Requirement)
+□ Task List contains ALL BLOCKING READs from this file
 □ Build process succeeds
 □ Tests pass (or no tests if not applicable)
 □ Linting: 0 errors
 □ Static analysis passes (if applicable)
 □ Manual testing performed (if applicable)
 □ Changes committed to git (for implementation tasks)
-□ Task tracking updated (work plan checkbox if using workflow)
+□ Task tracking updated (Work Plan checkbox if using workflow)
 
 **If any check fails:**
 → Fix issues before proceeding
@@ -92,7 +92,7 @@ Run project build:
 - Verify output artifacts
 - Confirm dependencies resolved
 
-*Note: Build commands are language-specific. Check language/testing.md*
+*Note: Build commands are language-specific. Check testing/SKILL.md*
 
 ### 2. Test Execution
 
@@ -190,7 +190,7 @@ Ensure:
 
 ## Tools by Language
 
-Reference `.agents/rules/language/testing.md` for:
+Reference `.agents/skills/testing/SKILL.md` for:
 - Language-specific test commands
 - Coverage tools
 - Linting configuration