harness-everything 0.2.1 → 0.2.2

package/docs/workflows/grill-me.md

@@ -1,62 +1,62 @@
-# Workflow: Grill Me
-
-> Relentless Challenger interview process that stress-tests architectural plans, highlights hidden assumptions, and demands explicit edge-case handling.
-
----
-
-## 1. Skill Behavior Workflow
-
-This section visualizes how the `grill-me` skill executes internally, detailing the sequence of operations, state transitions, and evaluation steps.
-
-```mermaid
-graph TD
-  Start([Developer Proposes Plan]) --> IntroduceChallenger["Introduce 'Challenger' adversarial persona"]
-  IntroduceChallenger --> ProbeAssumptions["Analyze proposal and probe soft/mocked points"]
-  ProbeAssumptions --> AskHardQuestions["Ask 3-5 aggressive, non-trivial stress-testing questions"]
-  AskHardQuestions --> ReceiveAnswers["Developer provides details & arguments"]
-  ReceiveAnswers --> ValidateResilience{Answers robust & handle failures?}
-  ValidateResilience -->|No| GrillDeeper["Grill deeper on specific vulnerabilities"]
-  ValidateResilience -->|Yes| DistillDecisions["Distill final agreed design decisions"]
-  GrillDeeper --> ReceiveAnswers
-  DistillDecisions --> End([Proposal approved and hardened against failures])
-```
-
----
-
-## 2. Triggering and Routing Path
-
-This diagram illustrates how the `grill-me` 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: grill / debate / plan| GrillMe["grill-me / SKILL.md"]
-  GrillMe -->|Writes final hardened agreements into| GWD["grill-with-docs / SKILL.md"]
-  GrillMe -->|Directs macro execution strategies of| Fable["fable-mode / SKILL.md"]
-```
-
----
-
-## 3. Real-World Use Case Flowchart
-
-Here we model concrete real-world scenarios and use cases of the `grill-me` skill, illustrating standard success paths, error handling, or recovery loops.
-
-```mermaid
-graph TD
-  Start["Proposal: 'I will write a fast cron job to sync database tables directly'"] --> Trigger["grill-me skill activated"]
-  Trigger --> Challenger["Challenger SRE: 'What happens if the cron script fails mid-sync? Will there be database lock contention? How do we prevent partial/corrupt states?'"]
-  Challenger --> Answer1["Dev: 'I'll add database transaction wraps and skip locks'"]
-  Answer1 --> Challenger2["Challenger: 'How will we monitor and alert if locks are skipped repeatedly?'"]
-  Challenger2 --> Answer2["Dev: 'I'll add structured logging and trigger a standard Slack web-hook alerting'"]
-  Answer2 --> Approve["Challenger: 'Excellent. Let's record these lock-skip alerts as mandatory requirements.'"]
-  Approve --> Done([Plan hardened and logged])
-```
-
----
-
-## 4. Verification Check
-
-To ensure that the `grill-me` 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: Grill Me
+
+> Relentless Challenger interview process that stress-tests architectural plans, highlights hidden assumptions, and demands explicit edge-case handling.
+
+---
+
+## 1. Skill Behavior Workflow
+
+This section visualizes how the `grill-me` skill executes internally, detailing the sequence of operations, state transitions, and evaluation steps.
+
+```mermaid
+graph TD
+  Start([Developer Proposes Plan]) --> IntroduceChallenger["Introduce 'Challenger' adversarial persona"]
+  IntroduceChallenger --> ProbeAssumptions["Analyze proposal and probe soft/mocked points"]
+  ProbeAssumptions --> AskHardQuestions["Ask 3-5 aggressive, non-trivial stress-testing questions"]
+  AskHardQuestions --> ReceiveAnswers["Developer provides details & arguments"]
+  ReceiveAnswers --> ValidateResilience{Answers robust & handle failures?}
+  ValidateResilience -->|No| GrillDeeper["Grill deeper on specific vulnerabilities"]
+  ValidateResilience -->|Yes| DistillDecisions["Distill final agreed design decisions"]
+  GrillDeeper --> ReceiveAnswers
+  DistillDecisions --> End([Proposal approved and hardened against failures])
+```
+
+---
+
+## 2. Triggering and Routing Path
+
+This diagram illustrates how the `grill-me` 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: grill / debate / plan| GrillMe["grill-me / SKILL.md"]
+  GrillMe -->|Writes final hardened agreements into| GWD["grill-with-docs / SKILL.md"]
+  GrillMe -->|Directs macro execution strategies of| Fable["fable-mode / SKILL.md"]
+```
+
+---
+
+## 3. Real-World Use Case Flowchart
+
+Here we model concrete real-world scenarios and use cases of the `grill-me` skill, illustrating standard success paths, error handling, or recovery loops.
+
+```mermaid
+graph TD
+  Start["Proposal: 'I will write a fast cron job to sync database tables directly'"] --> Trigger["grill-me skill activated"]
+  Trigger --> Challenger["Challenger SRE: 'What happens if the cron script fails mid-sync? Will there be database lock contention? How do we prevent partial/corrupt states?'"]
+  Challenger --> Answer1["Dev: 'I'll add database transaction wraps and skip locks'"]
+  Answer1 --> Challenger2["Challenger: 'How will we monitor and alert if locks are skipped repeatedly?'"]
+  Challenger2 --> Answer2["Dev: 'I'll add structured logging and trigger a standard Slack web-hook alerting'"]
+  Answer2 --> Approve["Challenger: 'Excellent. Let's record these lock-skip alerts as mandatory requirements.'"]
+  Approve --> Done([Plan hardened and logged])
+```
+
+---
+
+## 4. Verification Check
+
+To ensure that the `grill-me` 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/grill-with-docs.md

@@ -1,62 +1,62 @@
-# Workflow: Grill with Docs
-
-> Decision tracking, Glossary alignment, and ADR-driven (Architecture Decision Record) grilling to eliminate technical drift between code and documentation.
-
----
-
-## 1. Skill Behavior Workflow
-
-This section visualizes how the `grill-with-docs` skill executes internally, detailing the sequence of operations, state transitions, and evaluation steps.
-
-```mermaid
-graph TD
-  Start([Plan Proposed against Domain]) --> ReadDomainModel["Read CONTEXT.md and existing ADRs"]
-  ReadDomainModel --> ChallengeDrift["Examine plan for term drift or architectural violations"]
-  ChallengeDrift --> UpdateGlossary["Refine and match terminology with current Glossary"]
-  UpdateGlossary --> DraftADR["Draft formal Architecture Decision Record in ADR format"]
-  DraftADR --> StressTestADR["Stress-test ADR against error boundaries and fail-safes"]
-  StressTestADR --> WriteDocs["Commit ADR to docs/adr/ and update CONTEXT.md"]
-  WriteDocs --> InjectTodos["Inject critical TODO: [CRITICAL BUG FIX] tags into corresponding code"]
-  InjectTodos --> End([Code and documentation are perfectly aligned])
-```
-
----
-
-## 2. Triggering and Routing Path
-
-This diagram illustrates how the `grill-with-docs` 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: adr / decision / glossary| GWD["grill-with-docs / SKILL.md"]
-  GWD -->|Coordinates stress-tests using| GrillMe["grill-me / SKILL.md"]
-  GWD -->|Aligns documentation during macro work in| Fable["fable-mode / SKILL.md"]
-  GWD -->|Triggers todo tasks tracked by| Todo["todo-driven-workflow / SKILL.md"]
-```
-
----
-
-## 3. Real-World Use Case Flowchart
-
-Here we model concrete real-world scenarios and use cases of the `grill-with-docs` skill, illustrating standard success paths, error handling, or recovery loops.
-
-```mermaid
-graph TD
-  Start["Requirement: Change notification retry rate limits"] --> Trigger["grill-with-docs skill invoked"]
-  Trigger --> ReadDocs["Analyzes docs/adr/003-rate-limiting.md"]
-  ReadDocs --> CheckDrift["Finds that proposed change violates the maximum overload protection limit"]
-  CheckDrift --> RefinePlan["Plan updated to stay within the 003-rate-limiting contract"]
-  RefinePlan --> CreateADR["Create docs/adr/008-notification-retries.md"]
-  CreateADR --> SyncCode["Modify code and inject aligned TODO tags directly in code to maintain truth"]
-  SyncCode --> Done([Zero architectural drift achieved])
-```
-
----
-
-## 4. Verification Check
-
-To ensure that the `grill-with-docs` 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: Grill with Docs
+
+> Decision tracking, Glossary alignment, and ADR-driven (Architecture Decision Record) grilling to eliminate technical drift between code and documentation.
+
+---
+
+## 1. Skill Behavior Workflow
+
+This section visualizes how the `grill-with-docs` skill executes internally, detailing the sequence of operations, state transitions, and evaluation steps.
+
+```mermaid
+graph TD
+  Start([Plan Proposed against Domain]) --> ReadDomainModel["Read CONTEXT.md and existing ADRs"]
+  ReadDomainModel --> ChallengeDrift["Examine plan for term drift or architectural violations"]
+  ChallengeDrift --> UpdateGlossary["Refine and match terminology with current Glossary"]
+  UpdateGlossary --> DraftADR["Draft formal Architecture Decision Record in ADR format"]
+  DraftADR --> StressTestADR["Stress-test ADR against error boundaries and fail-safes"]
+  StressTestADR --> WriteDocs["Commit ADR to docs/adr/ and update CONTEXT.md"]
+  WriteDocs --> InjectTodos["Inject critical TODO: [CRITICAL BUG FIX] tags into corresponding code"]
+  InjectTodos --> End([Code and documentation are perfectly aligned])
+```
+
+---
+
+## 2. Triggering and Routing Path
+
+This diagram illustrates how the `grill-with-docs` 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: adr / decision / glossary| GWD["grill-with-docs / SKILL.md"]
+  GWD -->|Coordinates stress-tests using| GrillMe["grill-me / SKILL.md"]
+  GWD -->|Aligns documentation during macro work in| Fable["fable-mode / SKILL.md"]
+  GWD -->|Triggers todo tasks tracked by| Todo["todo-driven-workflow / SKILL.md"]
+```
+
+---
+
+## 3. Real-World Use Case Flowchart
+
+Here we model concrete real-world scenarios and use cases of the `grill-with-docs` skill, illustrating standard success paths, error handling, or recovery loops.
+
+```mermaid
+graph TD
+  Start["Requirement: Change notification retry rate limits"] --> Trigger["grill-with-docs skill invoked"]
+  Trigger --> ReadDocs["Analyzes docs/adr/003-rate-limiting.md"]
+  ReadDocs --> CheckDrift["Finds that proposed change violates the maximum overload protection limit"]
+  CheckDrift --> RefinePlan["Plan updated to stay within the 003-rate-limiting contract"]
+  RefinePlan --> CreateADR["Create docs/adr/008-notification-retries.md"]
+  CreateADR --> SyncCode["Modify code and inject aligned TODO tags directly in code to maintain truth"]
+  SyncCode --> Done([Zero architectural drift achieved])
+```
+
+---
+
+## 4. Verification Check
+
+To ensure that the `grill-with-docs` 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/improve-codebase-architecture.md

@@ -1,60 +1,60 @@
-# Workflow: Improve Codebase Architecture
-
-> Finds deepening opportunities in the codebase, consolidating tightly-coupled modules and mapping dependencies visually using Mermaid diagram reports.
-
----
-
-## 1. Skill Behavior Workflow
-
-This section visualizes how the `improve-codebase-architecture` skill executes internally, detailing the sequence of operations, state transitions, and evaluation steps.
-
-```mermaid
-graph TD
-  Start([Audit Request / Refactoring]) --> ScanDirectories["Scan code directories for coupling"]
-  ScanDirectories --> IdentifyTightlyCoupled["Locate highly coupled modules / wide files"]
-  IdentifyTightlyCoupled --> DeepModuleTest["Analyze modules against Deep Module Design rules"]
-  DeepModuleTest --> DefineSeams["Identify clean seams & write interface abstractions"]
-  DefineSeams --> GenMermaidReport["Generate visual HTML / Mermaid codebase dependency map"]
-  GenMermaidReport --> ProposeDecomposition["Formulate restructuring and extraction proposal"]
-  ProposeDecomposition --> End([Actionable refactoring strategy compiled])
-```
-
----
-
-## 2. Triggering and Routing Path
-
-This diagram illustrates how the `improve-codebase-architecture` 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: refactor / architecture / couple| ICA["improve-codebase-architecture / SKILL.md"]
-  ICA -->|Deductions challenged by SRE via| GrillMe["grill-me / SKILL.md"]
-  ICA -->|Guides large-scale structural rewrites in| Fable["fable-mode / SKILL.md"]
-  ICA -->|Extracts interfaces to simplify unit tests in| TDD["tdd / SKILL.md"]
-```
-
----
-
-## 3. Real-World Use Case Flowchart
-
-Here we model concrete real-world scenarios and use cases of the `improve-codebase-architecture` skill, illustrating standard success paths, error handling, or recovery loops.
-
-```mermaid
-graph TD
-  Start["Monolithic file 'utils.js' handles email, token creation, DB pooling, and logging"] --> Trigger["improve-codebase-architecture skill analyzed"]
-  Trigger --> Audit["Analyzes dependency graphs and calculates coupling scores"]
-  Audit --> FindSeams["Identifies three distinct interfaces: IEmailService, ITokener, IDbPool"]
-  FindSeams --> GenMermaid["Output detailed Mermaid diagram visualizing the proposed separated structure"]
-  GenMermaid --> RefactorPlan["Drafts multi-stage module extraction plan"]
-  RefactorPlan --> Done([Clear, modular architectural blueprint established])
-```
-
----
-
-## 4. Verification Check
-
-To ensure that the `improve-codebase-architecture` 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: Improve Codebase Architecture
+
+> Finds deepening opportunities in the codebase, consolidating tightly-coupled modules and mapping dependencies visually using Mermaid diagram reports.
+
+---
+
+## 1. Skill Behavior Workflow
+
+This section visualizes how the `improve-codebase-architecture` skill executes internally, detailing the sequence of operations, state transitions, and evaluation steps.
+
+```mermaid
+graph TD
+  Start([Audit Request / Refactoring]) --> ScanDirectories["Scan code directories for coupling"]
+  ScanDirectories --> IdentifyTightlyCoupled["Locate highly coupled modules / wide files"]
+  IdentifyTightlyCoupled --> DeepModuleTest["Analyze modules against Deep Module Design rules"]
+  DeepModuleTest --> DefineSeams["Identify clean seams & write interface abstractions"]
+  DefineSeams --> GenMermaidReport["Generate visual HTML / Mermaid codebase dependency map"]
+  GenMermaidReport --> ProposeDecomposition["Formulate restructuring and extraction proposal"]
+  ProposeDecomposition --> End([Actionable refactoring strategy compiled])
+```
+
+---
+
+## 2. Triggering and Routing Path
+
+This diagram illustrates how the `improve-codebase-architecture` 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: refactor / architecture / couple| ICA["improve-codebase-architecture / SKILL.md"]
+  ICA -->|Deductions challenged by SRE via| GrillMe["grill-me / SKILL.md"]
+  ICA -->|Guides large-scale structural rewrites in| Fable["fable-mode / SKILL.md"]
+  ICA -->|Extracts interfaces to simplify unit tests in| TDD["tdd / SKILL.md"]
+```
+
+---
+
+## 3. Real-World Use Case Flowchart
+
+Here we model concrete real-world scenarios and use cases of the `improve-codebase-architecture` skill, illustrating standard success paths, error handling, or recovery loops.
+
+```mermaid
+graph TD
+  Start["Monolithic file 'utils.js' handles email, token creation, DB pooling, and logging"] --> Trigger["improve-codebase-architecture skill analyzed"]
+  Trigger --> Audit["Analyzes dependency graphs and calculates coupling scores"]
+  Audit --> FindSeams["Identifies three distinct interfaces: IEmailService, ITokener, IDbPool"]
+  FindSeams --> GenMermaid["Output detailed Mermaid diagram visualizing the proposed separated structure"]
+  GenMermaid --> RefactorPlan["Drafts multi-stage module extraction plan"]
+  RefactorPlan --> Done([Clear, modular architectural blueprint established])
+```
+
+---
+
+## 4. Verification Check
+
+To ensure that the `improve-codebase-architecture` 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/repo-docs.md

@@ -1,59 +1,59 @@
-# Workflow: Repo Docs
-
-> Generates high-quality, professional README.md and AGENTS.md files based on actual workspace structures and product-archetype templates.
-
----
-
-## 1. Skill Behavior Workflow
-
-This section visualizes how the `repo-docs` skill executes internally, detailing the sequence of operations, state transitions, and evaluation steps.
-
-```mermaid
-graph TD
-  Start([Generate Repository Docs]) --> AuditProjectStructure["Audit workspace directory tree"]
-  AuditProjectStructure --> ClassifyProductArchetype["Classify repository archetype: tool, library, platform"]
-  ClassifyProductArchetype --> LoadTemplates["Load standard README and AGENTS templates"]
-  LoadTemplates --> InjectCustomStructure["Populate files with actual paths, licenses, and badges"]
-  InjectCustomStructure --> FormatMarkdown["Format documents following clean layout rules"]
-  FormatMarkdown --> WriteFiles["Commit README.md and AGENTS.md to workspace root"]
-  WriteFiles --> End([Professional onboarding documentation created])
-```
-
----
-
-## 2. Triggering and Routing Path
-
-This diagram illustrates how the `repo-docs` 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: doc / readme / agents-template| RepoDocs["repo-docs / SKILL.md"]
-  RepoDocs -->|Integrates frontmatter constraints into| BMAS["build-multi-agent-system / SKILL.md"]
-  RepoDocs -->|Leverages ADR details generated in| GWD["grill-with-docs / SKILL.md"]
-```
-
----
-
-## 3. Real-World Use Case Flowchart
-
-Here we model concrete real-world scenarios and use cases of the `repo-docs` skill, illustrating standard success paths, error handling, or recovery loops.
-
-```mermaid
-graph TD
-  Start["New library lacks onboarding docs and setup details"] --> Trigger["repo-docs skill invoked"]
-  Trigger --> Scan["Scans folders: discovers it's a TypeScript utility package"]
-  Scan --> MatchTemplate["Loads library archetype README template"]
-  MatchTemplate --> GenDocs["Outputs README.md with TypeScript usage examples, badges, and structure"]
-  GenDocs --> GenOnboarding["Outputs AGENTS.md defining the developer agent rules for the repo"]
-  GenOnboarding --> Done([Clean, standardized documentation committed])
-```
-
----
-
-## 4. Verification Check
-
-To ensure that the `repo-docs` 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: Repo Docs
+
+> Generates high-quality, professional README.md and AGENTS.md files based on actual workspace structures and product-archetype templates.
+
+---
+
+## 1. Skill Behavior Workflow
+
+This section visualizes how the `repo-docs` skill executes internally, detailing the sequence of operations, state transitions, and evaluation steps.
+
+```mermaid
+graph TD
+  Start([Generate Repository Docs]) --> AuditProjectStructure["Audit workspace directory tree"]
+  AuditProjectStructure --> ClassifyProductArchetype["Classify repository archetype: tool, library, platform"]
+  ClassifyProductArchetype --> LoadTemplates["Load standard README and AGENTS templates"]
+  LoadTemplates --> InjectCustomStructure["Populate files with actual paths, licenses, and badges"]
+  InjectCustomStructure --> FormatMarkdown["Format documents following clean layout rules"]
+  FormatMarkdown --> WriteFiles["Commit README.md and AGENTS.md to workspace root"]
+  WriteFiles --> End([Professional onboarding documentation created])
+```
+
+---
+
+## 2. Triggering and Routing Path
+
+This diagram illustrates how the `repo-docs` 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: doc / readme / agents-template| RepoDocs["repo-docs / SKILL.md"]
+  RepoDocs -->|Integrates frontmatter constraints into| BMAS["build-multi-agent-system / SKILL.md"]
+  RepoDocs -->|Leverages ADR details generated in| GWD["grill-with-docs / SKILL.md"]
+```
+
+---
+
+## 3. Real-World Use Case Flowchart
+
+Here we model concrete real-world scenarios and use cases of the `repo-docs` skill, illustrating standard success paths, error handling, or recovery loops.
+
+```mermaid
+graph TD
+  Start["New library lacks onboarding docs and setup details"] --> Trigger["repo-docs skill invoked"]
+  Trigger --> Scan["Scans folders: discovers it's a TypeScript utility package"]
+  Scan --> MatchTemplate["Loads library archetype README template"]
+  MatchTemplate --> GenDocs["Outputs README.md with TypeScript usage examples, badges, and structure"]
+  GenDocs --> GenOnboarding["Outputs AGENTS.md defining the developer agent rules for the repo"]
+  GenOnboarding --> Done([Clean, standardized documentation committed])
+```
+
+---
+
+## 4. Verification Check
+
+To ensure that the `repo-docs` 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/rewrite-commits.md

@@ -1,60 +1,60 @@
-# Workflow: Rewrite Commits
-
-> Safely rewrites or squashes a specified range of commits into highly professional, Conventional Commits (Angular style) on a new branch.
-
----
-
-## 1. Skill Behavior Workflow
-
-This section visualizes how the `rewrite-commits` skill executes internally, detailing the sequence of operations, state transitions, and evaluation steps.
-
-```mermaid
-graph TD
-  Start([Define Commit Range]) --> BackupBranch["Create a backup branch of current state"]
-  BackupBranch --> ReadCommits["Read all commit messages in the range"]
-  ReadCommits --> AnalyzeDiffs["Read files & diffs associated with each commit"]
-  AnalyzeDiffs --> GenNewMessages["Generate high-quality Angular-style messages for each diff"]
-  GenNewMessages --> SoftReset["Execute git reset --soft to merge range changes"]
-  SoftReset --> ReapplyCommits["Re-apply changes with perfectly clean, segmented commit history"]
-  ReapplyCommits --> VerifyBranch["Run verification checks on the final rebuilt branch"]
-  VerifyBranch --> End([Perfectly clean Git history on new branch])
-```
-
----
-
-## 2. Triggering and Routing Path
-
-This diagram illustrates how the `rewrite-commits` 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: commit / rewrite / squash| Rewrite["rewrite-commits / SKILL.md"]
-  Rewrite -->|Supplements convention templates in| GitCommit["git-commit / SKILL.md"]
-  Rewrite -->|Pre-verify rewritten commits via| VerLoop["verification-loop / SKILL.md"]
-```
-
----
-
-## 3. Real-World Use Case Flowchart
-
-Here we model concrete real-world scenarios and use cases of the `rewrite-commits` skill, illustrating standard success paths, error handling, or recovery loops.
-
-```mermaid
-graph TD
-  Start["Branch has messy commits: 'fixed stuff', 'more fixes', 'bug'"] --> Trigger["Rewrite-commits skill run for HEAD~3"]
-  Trigger --> Backup["Backup branch 'backup-feature-x' created"]
-  Trigger --> GatherDiffs["Analyze total diff across the 3 messy commits"]
-  GatherDiffs --> Generate完美["Determine changes relate to user auth session handling"]
-  Generate完美 --> Rebuild["Reset and make 1 perfect commit: 'fix(auth): correct token refresh race condition'"]
-  Rebuild --> Done([Clean, reviewable PR history ready])
-```
-
----
-
-## 4. Verification Check
-
-To ensure that the `rewrite-commits` 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: Rewrite Commits
+
+> Safely rewrites or squashes a specified range of commits into highly professional, Conventional Commits (Angular style) on a new branch.
+
+---
+
+## 1. Skill Behavior Workflow
+
+This section visualizes how the `rewrite-commits` skill executes internally, detailing the sequence of operations, state transitions, and evaluation steps.
+
+```mermaid
+graph TD
+  Start([Define Commit Range]) --> BackupBranch["Create a backup branch of current state"]
+  BackupBranch --> ReadCommits["Read all commit messages in the range"]
+  ReadCommits --> AnalyzeDiffs["Read files & diffs associated with each commit"]
+  AnalyzeDiffs --> GenNewMessages["Generate high-quality Angular-style messages for each diff"]
+  GenNewMessages --> SoftReset["Execute git reset --soft to merge range changes"]
+  SoftReset --> ReapplyCommits["Re-apply changes with perfectly clean, segmented commit history"]
+  ReapplyCommits --> VerifyBranch["Run verification checks on the final rebuilt branch"]
+  VerifyBranch --> End([Perfectly clean Git history on new branch])
+```
+
+---
+
+## 2. Triggering and Routing Path
+
+This diagram illustrates how the `rewrite-commits` 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: commit / rewrite / squash| Rewrite["rewrite-commits / SKILL.md"]
+  Rewrite -->|Supplements convention templates in| GitCommit["git-commit / SKILL.md"]
+  Rewrite -->|Pre-verify rewritten commits via| VerLoop["verification-loop / SKILL.md"]
+```
+
+---
+
+## 3. Real-World Use Case Flowchart
+
+Here we model concrete real-world scenarios and use cases of the `rewrite-commits` skill, illustrating standard success paths, error handling, or recovery loops.
+
+```mermaid
+graph TD
+  Start["Branch has messy commits: 'fixed stuff', 'more fixes', 'bug'"] --> Trigger["Rewrite-commits skill run for HEAD~3"]
+  Trigger --> Backup["Backup branch 'backup-feature-x' created"]
+  Trigger --> GatherDiffs["Analyze total diff across the 3 messy commits"]
+  GatherDiffs --> Generate完美["Determine changes relate to user auth session handling"]
+  Generate完美 --> Rebuild["Reset and make 1 perfect commit: 'fix(auth): correct token refresh race condition'"]
+  Rebuild --> Done([Clean, reviewable PR history ready])
+```
+
+---
+
+## 4. Verification Check
+
+To ensure that the `rewrite-commits` 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.