harness-everything 0.2.0 → 0.2.1

package/docs/workflows/security-review.md

@@ -1,58 +1,58 @@
-# Workflow: Security Review
-
-> Automated security scanning, threat modeling, and input-validation reviews to identify potential security holes and enforce robust safety guardrails.
-
----
-
-## 1. Skill Behavior Workflow
-
-This section visualizes how the `security-review` skill executes internally, detailing the sequence of operations, state transitions, and evaluation steps.
-
-```mermaid
-graph TD
-  Start([Code Refactoring / Feature Done]) --> ScanInputs["Locate all user input and API boundary points"]
-  ScanInputs --> ThreatModeling["Perform threat modeling on data flow"]
-  ThreatModeling --> CheckCommonVulnerabilities["Check for SQL Injection, XSS, CSRF, and broken access controls"]
-  CheckCommonVulnerabilities --> AuditDependencies["Scan package dependencies for known CVE vulnerabilities"]
-  AuditDependencies --> FlagSinks["Flag insecure coding patterns, hardcoded secrets, or raw exec commands"]
-  FlagSinks --> CompileSecurityReport["Compile actionable security hardening proposal"]
-  CompileSecurityReport --> End([Codebase hardened and verified secure])
-```
-
----
-
-## 2. Triggering and Routing Path
-
-This diagram illustrates how the `security-review` skill is triggered through user requests or developer actions, and how it integrates or chains together with other companion skills in the Harness OS ecosystem to form unified workflows.
-
-```mermaid
-graph LR
-  Router["harness-everything / tier-router.js"] -->|Pre-flight / Quality PR reviews| SecReview["security-review / SKILL.md"]
-  SecReview -->|Informs security tests written in| TDD["tdd / SKILL.md"]
-  SecReview -->|Integrated as mandatory PR gate in| VerLoop["verification-loop / SKILL.md"]
-```
-
----
-
-## 3. Real-World Use Case Flowchart
-
-Here we model concrete real-world scenarios and use cases of the `security-review` skill, illustrating standard success paths, error handling, or recovery loops.
-
-```mermaid
-graph TD
-  Start["New search feature: executes system shell query using raw user input string"] --> Trigger["security-review skill runs"]
-  Trigger --> Scan["Flags potential command injection vulnerability in search.js"]
-  Scan --> Propose["Propose input sanitization and switching to child_process.execFile with argument array"]
-  Propose --> Implement["Refactor code to use safe argument arrays instead of raw string shell execution"]
-  Implement --> Done([Critical remote code execution vulnerability resolved])
-```
-
----
-
-## 4. Verification Check
-
-To ensure that the `security-review` skill is operating in strict compliance with Harness OS design laws, verify the following:
-
-- [ ] **Physical Boundary Verification**: The skill boundaries are respected and do not leak context.
-- [ ] **State Checkpoint Verification**: The active state is established, validated, and recorded at the beginning and end of each execution branch.
-- [ ] **Cognitive Alignment**: The skill conforms to the **Think > Try > Summarize > Record** cognitive loop.
+# Workflow: Security Review
+
+> Automated security scanning, threat modeling, and input-validation reviews to identify potential security holes and enforce robust safety guardrails.
+
+---
+
+## 1. Skill Behavior Workflow
+
+This section visualizes how the `security-review` skill executes internally, detailing the sequence of operations, state transitions, and evaluation steps.
+
+```mermaid
+graph TD
+  Start([Code Refactoring / Feature Done]) --> ScanInputs["Locate all user input and API boundary points"]
+  ScanInputs --> ThreatModeling["Perform threat modeling on data flow"]
+  ThreatModeling --> CheckCommonVulnerabilities["Check for SQL Injection, XSS, CSRF, and broken access controls"]
+  CheckCommonVulnerabilities --> AuditDependencies["Scan package dependencies for known CVE vulnerabilities"]
+  AuditDependencies --> FlagSinks["Flag insecure coding patterns, hardcoded secrets, or raw exec commands"]
+  FlagSinks --> CompileSecurityReport["Compile actionable security hardening proposal"]
+  CompileSecurityReport --> End([Codebase hardened and verified secure])
+```
+
+---
+
+## 2. Triggering and Routing Path
+
+This diagram illustrates how the `security-review` skill is triggered through user requests or developer actions, and how it integrates or chains together with other companion skills in the Harness OS ecosystem to form unified workflows.
+
+```mermaid
+graph LR
+  Router["harness-everything / tier-router.js"] -->|Pre-flight / Quality PR reviews| SecReview["security-review / SKILL.md"]
+  SecReview -->|Informs security tests written in| TDD["tdd / SKILL.md"]
+  SecReview -->|Integrated as mandatory PR gate in| VerLoop["verification-loop / SKILL.md"]
+```
+
+---
+
+## 3. Real-World Use Case Flowchart
+
+Here we model concrete real-world scenarios and use cases of the `security-review` skill, illustrating standard success paths, error handling, or recovery loops.
+
+```mermaid
+graph TD
+  Start["New search feature: executes system shell query using raw user input string"] --> Trigger["security-review skill runs"]
+  Trigger --> Scan["Flags potential command injection vulnerability in search.js"]
+  Scan --> Propose["Propose input sanitization and switching to child_process.execFile with argument array"]
+  Propose --> Implement["Refactor code to use safe argument arrays instead of raw string shell execution"]
+  Implement --> Done([Critical remote code execution vulnerability resolved])
+```
+
+---
+
+## 4. Verification Check
+
+To ensure that the `security-review` skill is operating in strict compliance with Harness OS design laws, verify the following:
+
+- [ ] **Physical Boundary Verification**: The skill boundaries are respected and do not leak context.
+- [ ] **State Checkpoint Verification**: The active state is established, validated, and recorded at the beginning and end of each execution branch.
+- [ ] **Cognitive Alignment**: The skill conforms to the **Think > Try > Summarize > Record** cognitive loop.

package/docs/workflows/self-evolve.md

@@ -1,59 +1,59 @@
-# Workflow: Self-Evolve
-
-> Analyzes execution logs and session memories to extract underlying root causes, defining new error boundaries and compressing them into cognitive guardrails.
-
----
-
-## 1. Skill Behavior Workflow
-
-This section visualizes how the `self-evolve` skill executes internally, detailing the sequence of operations, state transitions, and evaluation steps.
-
-```mermaid
-graph TD
-  Start([Task Completed / Error Loop Triggered]) --> ReadSessionLogs["Read active debugging logs & session history"]
-  ReadSessionLogs --> IdentifyRootCauses["Isolate and extract system failures or bottlenecks"]
-  IdentifyRootCauses --> SynthesizeGuardrails["Formulate actionable high-level cognitive guardrails"]
-  SynthesizeGuardrails --> CompressMemories["Compress repetitive events into compact markdown files in /memories/"]
-  CompressMemories --> UpdateUserMemory["Commit lessons learned to user memory space"]
-  UpdateUserMemory --> End([Agent cognitive defense expanded for future sessions])
-```
-
----
-
-## 2. Triggering and Routing Path
-
-This diagram illustrates how the `self-evolve` skill is triggered through user requests or developer actions, and how it integrates or chains together with other companion skills in the Harness OS ecosystem to form unified workflows.
-
-```mermaid
-graph LR
-  SessionEnd["Task Completed / Session Closed"] --> Evolve["self-evolve / SKILL.md"]
-  Evolve -->|Reads from| HistoryLog["VS Code Debug logs & memory directories"]
-  Evolve -->|Writes permanent updates to| UserMemory["/memories/ / user-memory files"]
-  Evolve -->|Informs future task triage in| Router["harness-everything / tier-router.js"]
-```
-
----
-
-## 3. Real-World Use Case Flowchart
-
-Here we model concrete real-world scenarios and use cases of the `self-evolve` skill, illustrating standard success paths, error handling, or recovery loops.
-
-```mermaid
-graph TD
-  Start["Session ends after solving a recurring, messy Windows path-slashes bug"] --> Trigger["self-evolve skill runs automatically"]
-  Trigger --> Analyze["Reads last 5 execution logs"]
-  Analyze --> DetectPattern["Finds 3 consecutive terminal command failures caused by path backslashes in PowerShell"]
-  DetectPattern --> Formulate["Formulate new guardrail: 'When on Windows, convert backslashes to forward slashes for cross-shell command lines'"]
-  Formulate --> Write["Write bullet point to /memories/debugging.md"]
-  Write --> Done([Memory recorded: future sessions will automatically avoid Windows path errors])
-```
-
----
-
-## 4. Verification Check
-
-To ensure that the `self-evolve` skill is operating in strict compliance with Harness OS design laws, verify the following:
-
-- [ ] **Physical Boundary Verification**: The skill boundaries are respected and do not leak context.
-- [ ] **State Checkpoint Verification**: The active state is established, validated, and recorded at the beginning and end of each execution branch.
-- [ ] **Cognitive Alignment**: The skill conforms to the **Think > Try > Summarize > Record** cognitive loop.
+# Workflow: Self-Evolve
+
+> Analyzes execution logs and session memories to extract underlying root causes, defining new error boundaries and compressing them into cognitive guardrails.
+
+---
+
+## 1. Skill Behavior Workflow
+
+This section visualizes how the `self-evolve` skill executes internally, detailing the sequence of operations, state transitions, and evaluation steps.
+
+```mermaid
+graph TD
+  Start([Task Completed / Error Loop Triggered]) --> ReadSessionLogs["Read active debugging logs & session history"]
+  ReadSessionLogs --> IdentifyRootCauses["Isolate and extract system failures or bottlenecks"]
+  IdentifyRootCauses --> SynthesizeGuardrails["Formulate actionable high-level cognitive guardrails"]
+  SynthesizeGuardrails --> CompressMemories["Compress repetitive events into compact markdown files in /memories/"]
+  CompressMemories --> UpdateUserMemory["Commit lessons learned to user memory space"]
+  UpdateUserMemory --> End([Agent cognitive defense expanded for future sessions])
+```
+
+---
+
+## 2. Triggering and Routing Path
+
+This diagram illustrates how the `self-evolve` skill is triggered through user requests or developer actions, and how it integrates or chains together with other companion skills in the Harness OS ecosystem to form unified workflows.
+
+```mermaid
+graph LR
+  SessionEnd["Task Completed / Session Closed"] --> Evolve["self-evolve / SKILL.md"]
+  Evolve -->|Reads from| HistoryLog["VS Code Debug logs & memory directories"]
+  Evolve -->|Writes permanent updates to| UserMemory["/memories/ / user-memory files"]
+  Evolve -->|Informs future task triage in| Router["harness-everything / tier-router.js"]
+```
+
+---
+
+## 3. Real-World Use Case Flowchart
+
+Here we model concrete real-world scenarios and use cases of the `self-evolve` skill, illustrating standard success paths, error handling, or recovery loops.
+
+```mermaid
+graph TD
+  Start["Session ends after solving a recurring, messy Windows path-slashes bug"] --> Trigger["self-evolve skill runs automatically"]
+  Trigger --> Analyze["Reads last 5 execution logs"]
+  Analyze --> DetectPattern["Finds 3 consecutive terminal command failures caused by path backslashes in PowerShell"]
+  DetectPattern --> Formulate["Formulate new guardrail: 'When on Windows, convert backslashes to forward slashes for cross-shell command lines'"]
+  Formulate --> Write["Write bullet point to /memories/debugging.md"]
+  Write --> Done([Memory recorded: future sessions will automatically avoid Windows path errors])
+```
+
+---
+
+## 4. Verification Check
+
+To ensure that the `self-evolve` skill is operating in strict compliance with Harness OS design laws, verify the following:
+
+- [ ] **Physical Boundary Verification**: The skill boundaries are respected and do not leak context.
+- [ ] **State Checkpoint Verification**: The active state is established, validated, and recorded at the beginning and end of each execution branch.
+- [ ] **Cognitive Alignment**: The skill conforms to the **Think > Try > Summarize > Record** cognitive loop.

package/docs/workflows/tdd.md

@@ -1,39 +1,39 @@
-# Workflow: Test-Driven Development (TDD)
-
-> Enforces the classic Red-Green-Refactor development cycle. Crucially, this is NOT a linear process. It is a loop driven by terminal exit codes.
-
----
-
-## 1. Skill Behavior Workflow
-
-This section visualizes the script-gated reality of TDD. The AI cannot progress to the next phase until the terminal script explicitly confirms the state.
-
-```mermaid
-graph TD
-  Start([Identify Feature / Bug]) --> DesignInterface["Design interface & contract"]
-  DesignInterface --> WriteTest["Write unit/integration tests first"]
-  
-  WriteTest --> RunRed["Try: Run tests (EXPECT FAILURE)"]
-  RunRed --> VerifyRed{Gate: Exit Code 1?}
-  VerifyRed -->|Exit 0: Fake Test| FixTest["Reflect: Test is broken/fake. Fix it."]
-  FixTest --> RunRed
-  
-  VerifyRed -->|Exit 1: True Red| WriteCode["Write minimal code to pass test"]
-  
-  WriteCode --> RunGreen["Try: Run tests (EXPECT SUCCESS)"]
-  RunGreen --> VerifyGreen{Gate: verify-gate.js}
-  
-  VerifyGreen -->|Exit 1: Still Broken| DebugCode["Reflect: Read logs, fix code"]
-  DebugCode --> RunGreen
-  VerifyGreen -->|Exit 1: 3x Failures| CircuitBreaker["Trigger rule-of-3.js: ZOOM OUT"]
-  CircuitBreaker --> DebugCode
-  
-  VerifyGreen -->|Exit 0: Green| Refactor["Refactor code for readability"]
-  
-  Refactor --> RunVerify["Try: Run tests again"]
-  RunVerify --> VerifyRefactor{Gate: verify-gate.js}
-  VerifyRefactor -->|Exit 1| Revert["Revert refactor / Fix"]
-  Revert --> RunVerify
-  
-  VerifyRefactor -->|Exit 0| End([Feature verified & completed])
-```
+# Workflow: Test-Driven Development (TDD)
+
+> Enforces the classic Red-Green-Refactor development cycle. Crucially, this is NOT a linear process. It is a loop driven by terminal exit codes.
+
+---
+
+## 1. Skill Behavior Workflow
+
+This section visualizes the script-gated reality of TDD. The AI cannot progress to the next phase until the terminal script explicitly confirms the state.
+
+```mermaid
+graph TD
+  Start([Identify Feature / Bug]) --> DesignInterface["Design interface & contract"]
+  DesignInterface --> WriteTest["Write unit/integration tests first"]
+  
+  WriteTest --> RunRed["Try: Run tests (EXPECT FAILURE)"]
+  RunRed --> VerifyRed{Gate: Exit Code 1?}
+  VerifyRed -->|Exit 0: Fake Test| FixTest["Reflect: Test is broken/fake. Fix it."]
+  FixTest --> RunRed
+  
+  VerifyRed -->|Exit 1: True Red| WriteCode["Write minimal code to pass test"]
+  
+  WriteCode --> RunGreen["Try: Run tests (EXPECT SUCCESS)"]
+  RunGreen --> VerifyGreen{Gate: verify-gate.js}
+  
+  VerifyGreen -->|Exit 1: Still Broken| DebugCode["Reflect: Read logs, fix code"]
+  DebugCode --> RunGreen
+  VerifyGreen -->|Exit 1: 3x Failures| CircuitBreaker["Trigger rule-of-3.js: ZOOM OUT"]
+  CircuitBreaker --> DebugCode
+  
+  VerifyGreen -->|Exit 0: Green| Refactor["Refactor code for readability"]
+  
+  Refactor --> RunVerify["Try: Run tests again"]
+  RunVerify --> VerifyRefactor{Gate: verify-gate.js}
+  VerifyRefactor -->|Exit 1| Revert["Revert refactor / Fix"]
+  Revert --> RunVerify
+  
+  VerifyRefactor -->|Exit 0| End([Feature verified & completed])
+```

package/docs/workflows/todo-driven-workflow.md

@@ -1,36 +1,36 @@
-# Workflow: Todo-Driven Workflow
-
-> The fundamental execution loop. Driven entirely by terminal state machines (`todo-cli.js`).
-
----
-
-## 1. Skill Behavior Workflow
-
-This section visualizes the rigid state constraints. Transitioning state is blocked unless verification gates pass.
-
-```mermaid
-graph TD
-  Start([Initialize Checklist]) --> Plan["Define 3-7 Verifiable Sub-tasks"]
-  Plan --> SaveTodo["Try: node todo-cli.js init ..."]
-  
-  SaveTodo --> ChooseTask["Choose ONE pending task"]
-  ChooseTask --> MarkInProgress["Try: node todo-cli.js start <id>"]
-  
-  MarkInProgress --> CheckStart{Gate: Exit Code?}
-  CheckStart -->|Exit 1: Multitasking Blocked| ReflectStart["Reflect: Must complete previous task first"]
-  ReflectStart --> Execute
-  
-  CheckStart -->|Exit 0| Execute["Execute code changes"]
-  
-  Execute --> GatherEvidence["Try: node verify-gate.js"]
-  GatherEvidence --> VerifySuccess{Gate: Exit Code?}
-  
-  VerifySuccess -->|Exit 1: Code is broken| ReflectCode["Reflect: Read Error Log & Fix"]
-  ReflectCode --> Execute
-  
-  VerifySuccess -->|Exit 0: Code works| MarkCompleted["Try: node todo-cli.js complete <id>"]
-  
-  MarkCompleted --> CheckRemaining{All tasks completed?}
-  CheckRemaining -->|No| ChooseTask
-  CheckRemaining -->|Yes| Finish([Signal Task Completion])
-```
+# Workflow: Todo-Driven Workflow
+
+> The fundamental execution loop. Driven entirely by terminal state machines (`todo-cli.js`).
+
+---
+
+## 1. Skill Behavior Workflow
+
+This section visualizes the rigid state constraints. Transitioning state is blocked unless verification gates pass.
+
+```mermaid
+graph TD
+  Start([Initialize Checklist]) --> Plan["Define 3-7 Verifiable Sub-tasks"]
+  Plan --> SaveTodo["Try: node todo-cli.js init ..."]
+  
+  SaveTodo --> ChooseTask["Choose ONE pending task"]
+  ChooseTask --> MarkInProgress["Try: node todo-cli.js start <id>"]
+  
+  MarkInProgress --> CheckStart{Gate: Exit Code?}
+  CheckStart -->|Exit 1: Multitasking Blocked| ReflectStart["Reflect: Must complete previous task first"]
+  ReflectStart --> Execute
+  
+  CheckStart -->|Exit 0| Execute["Execute code changes"]
+  
+  Execute --> GatherEvidence["Try: node verify-gate.js"]
+  GatherEvidence --> VerifySuccess{Gate: Exit Code?}
+  
+  VerifySuccess -->|Exit 1: Code is broken| ReflectCode["Reflect: Read Error Log & Fix"]
+  ReflectCode --> Execute
+  
+  VerifySuccess -->|Exit 0: Code works| MarkCompleted["Try: node todo-cli.js complete <id>"]
+  
+  MarkCompleted --> CheckRemaining{All tasks completed?}
+  CheckRemaining -->|No| ChooseTask
+  CheckRemaining -->|Yes| Finish([Signal Task Completion])
+```

package/docs/workflows/using-git-worktrees.md

@@ -1,63 +1,63 @@
-# Workflow: Using Git Worktrees
-
-> Manages isolated workspace environments in parallel using native Git Worktrees, enabling developers to switch contexts safely without stashing or losing unsaved progress.
-
----
-
-## 1. Skill Behavior Workflow
-
-This section visualizes how the `using-git-worktrees` skill executes internally, detailing the sequence of operations, state transitions, and evaluation steps.
-
-```mermaid
-graph TD
-  Start([Switch Context Needed]) --> CheckClean["Assess if main branch has uncommitted changes"]
-  CheckClean --> CreateWorktree["Run git worktree add to a sibling directory"]
-  CreateWorktree --> CheckoutTarget["Checkout target branch or create a hotfix branch"]
-  CheckoutTarget --> OpenWorkspace["Open the sibling directory as a separate isolated workspace"]
-  OpenWorkspace --> RunDev["Perform isolated edits, tests, and debugging"]
-  RunDev --> CommitIsolated["Commit changes in the isolated workspace"]
-  CommitIsolated --> RemoveWorktree["Prune and clean up the worktree path"]
-  RemoveWorktree --> Return([Return to original workspace with pristine unsaved state intact])
-```
-
----
-
-## 2. Triggering and Routing Path
-
-This diagram illustrates how the `using-git-worktrees` skill is triggered through user requests or developer actions, and how it integrates or chains together with other companion skills in the Harness OS ecosystem to form unified workflows.
-
-```mermaid
-graph LR
-  Router["harness-everything / tier-router.js"] -->|Keyword: worktree / isolate / checkout| WT["using-git-worktrees / SKILL.md"]
-  WT -->|Maintains isolation before running tests in| TDDSkill["tdd / SKILL.md"]
-  WT -->|Protects terminal environment testing in| EnvSkill["environment-detection / SKILL.md"]
-```
-
----
-
-## 3. Real-World Use Case Flowchart
-
-Here we model concrete real-world scenarios and use cases of the `using-git-worktrees` skill, illustrating standard success paths, error handling, or recovery loops.
-
-```mermaid
-graph TD
-  Start["Working on deep feature 'feat-billing' (unstaged edits)"] --> Interrupt["Urgent production hotfix required!"]
-  Interrupt --> Trigger["using-git-worktrees skill invoked"]
-  Trigger --> CreateWT["Add worktree: 'git worktree add ../hotfix-auth hotfix-branch'"]
-  CreateWT --> OpenWT["Open separate workspace editor in ../hotfix-auth"]
-  OpenWT --> FixBug["Fix auth bug & run verification test"]
-  FixBug --> CommitWT["Commit fix and push branch"]
-  CommitWT --> CloseWT["Close editor, run 'git worktree prune'"]
-  CloseWT --> Resume["Return to original billing workspace with all unsaved files exactly where they were"]
-  Resume --> Done([Context switched safely with zero stashing friction])
-```
-
----
-
-## 4. Verification Check
-
-To ensure that the `using-git-worktrees` skill is operating in strict compliance with Harness OS design laws, verify the following:
-
-- [ ] **Physical Boundary Verification**: The skill boundaries are respected and do not leak context.
-- [ ] **State Checkpoint Verification**: The active state is established, validated, and recorded at the beginning and end of each execution branch.
-- [ ] **Cognitive Alignment**: The skill conforms to the **Think > Try > Summarize > Record** cognitive loop.
+# Workflow: Using Git Worktrees
+
+> Manages isolated workspace environments in parallel using native Git Worktrees, enabling developers to switch contexts safely without stashing or losing unsaved progress.
+
+---
+
+## 1. Skill Behavior Workflow
+
+This section visualizes how the `using-git-worktrees` skill executes internally, detailing the sequence of operations, state transitions, and evaluation steps.
+
+```mermaid
+graph TD
+  Start([Switch Context Needed]) --> CheckClean["Assess if main branch has uncommitted changes"]
+  CheckClean --> CreateWorktree["Run git worktree add to a sibling directory"]
+  CreateWorktree --> CheckoutTarget["Checkout target branch or create a hotfix branch"]
+  CheckoutTarget --> OpenWorkspace["Open the sibling directory as a separate isolated workspace"]
+  OpenWorkspace --> RunDev["Perform isolated edits, tests, and debugging"]
+  RunDev --> CommitIsolated["Commit changes in the isolated workspace"]
+  CommitIsolated --> RemoveWorktree["Prune and clean up the worktree path"]
+  RemoveWorktree --> Return([Return to original workspace with pristine unsaved state intact])
+```
+
+---
+
+## 2. Triggering and Routing Path
+
+This diagram illustrates how the `using-git-worktrees` skill is triggered through user requests or developer actions, and how it integrates or chains together with other companion skills in the Harness OS ecosystem to form unified workflows.
+
+```mermaid
+graph LR
+  Router["harness-everything / tier-router.js"] -->|Keyword: worktree / isolate / checkout| WT["using-git-worktrees / SKILL.md"]
+  WT -->|Maintains isolation before running tests in| TDDSkill["tdd / SKILL.md"]
+  WT -->|Protects terminal environment testing in| EnvSkill["environment-detection / SKILL.md"]
+```
+
+---
+
+## 3. Real-World Use Case Flowchart
+
+Here we model concrete real-world scenarios and use cases of the `using-git-worktrees` skill, illustrating standard success paths, error handling, or recovery loops.
+
+```mermaid
+graph TD
+  Start["Working on deep feature 'feat-billing' (unstaged edits)"] --> Interrupt["Urgent production hotfix required!"]
+  Interrupt --> Trigger["using-git-worktrees skill invoked"]
+  Trigger --> CreateWT["Add worktree: 'git worktree add ../hotfix-auth hotfix-branch'"]
+  CreateWT --> OpenWT["Open separate workspace editor in ../hotfix-auth"]
+  OpenWT --> FixBug["Fix auth bug & run verification test"]
+  FixBug --> CommitWT["Commit fix and push branch"]
+  CommitWT --> CloseWT["Close editor, run 'git worktree prune'"]
+  CloseWT --> Resume["Return to original billing workspace with all unsaved files exactly where they were"]
+  Resume --> Done([Context switched safely with zero stashing friction])
+```
+
+---
+
+## 4. Verification Check
+
+To ensure that the `using-git-worktrees` skill is operating in strict compliance with Harness OS design laws, verify the following:
+
+- [ ] **Physical Boundary Verification**: The skill boundaries are respected and do not leak context.
+- [ ] **State Checkpoint Verification**: The active state is established, validated, and recorded at the beginning and end of each execution branch.
+- [ ] **Cognitive Alignment**: The skill conforms to the **Think > Try > Summarize > Record** cognitive loop.