@su-record/vibe 2.9.22 → 2.9.23

package/skills/exec-plan/rubrics/complexity-scoring.md

@@ -1,75 +1,75 @@
-# Complexity Scoring Rubric
-
-Use this rubric to decide whether a task needs an ExecPlan and how to decompose it.
-
-## Scoring Dimensions
-
-Score each dimension 1–3. Total determines the approach.
-
-### Dimension 1: File Scope
-
-| Score | Criteria |
-|-------|----------|
-| 1 | 1–2 files touched |
-| 2 | 3–5 files touched |
-| 3 | 6+ files, or new module created |
-
-### Dimension 2: Dependency Depth
-
-| Score | Criteria |
-|-------|----------|
-| 1 | No external deps; isolated change |
-| 2 | 1–2 existing modules depended on |
-| 3 | Cross-layer dependencies; DB schema; API contract changes |
-
-### Dimension 3: Ambiguity
-
-| Score | Criteria |
-|-------|----------|
-| 1 | Requirement is explicit; no design decisions needed |
-| 2 | 1–2 decision points that need resolution before coding |
-| 3 | Architecture-level decisions; unknown patterns; research needed |
-
-### Dimension 4: Test Surface
-
-| Score | Criteria |
-|-------|----------|
-| 1 | Existing test file; trivial assertion additions |
-| 2 | New test file needed; mocking required |
-| 3 | Integration tests; DB fixtures; snapshot regeneration |
-
-### Dimension 5: Session Risk
-
-| Score | Criteria |
-|-------|----------|
-| 1 | Fits in one session; easy to resume |
-| 2 | May span sessions; partial state is safe |
-| 3 | Long-running; partial state is dangerous; handoff required |
-
----
-
-## Decision Matrix
-
-| Total Score | Approach |
-|-------------|----------|
-| 5–7 | Plan Mode (in-head plan, no file needed) |
-| 8–10 | Light ExecPlan (phases only, no inline patterns) |
-| 11–13 | Full ExecPlan (all fields, inline patterns, phase gates) |
-| 14–15 | ExecPlan + parallel research before starting |
-
----
-
-## Decomposition Rules
-
-When total ≥ 11, decompose into phases:
-
-1. **One phase = one deployable unit** — each phase leaves the codebase in a working state
-2. **Max 3 scenarios per phase** — more means the phase is too large; split it
-3. **Phase gate before next phase** — build + tests must pass at each boundary
-4. **No implicit dependencies between phases** — phase 2 must not assume phase 1 code style; document patterns inline
-
-## Anti-patterns
-
-- Scoring 1 on all dimensions then creating an ExecPlan → overhead without benefit
-- Scoring 3 on ambiguity without resolving decisions first → plan will fail
-- Skipping phase gates to go faster → regressions compound
+# Complexity Scoring Rubric
+
+Use this rubric to decide whether a task needs an ExecPlan and how to decompose it.
+
+## Scoring Dimensions
+
+Score each dimension 1–3. Total determines the approach.
+
+### Dimension 1: File Scope
+
+| Score | Criteria |
+|-------|----------|
+| 1 | 1–2 files touched |
+| 2 | 3–5 files touched |
+| 3 | 6+ files, or new module created |
+
+### Dimension 2: Dependency Depth
+
+| Score | Criteria |
+|-------|----------|
+| 1 | No external deps; isolated change |
+| 2 | 1–2 existing modules depended on |
+| 3 | Cross-layer dependencies; DB schema; API contract changes |
+
+### Dimension 3: Ambiguity
+
+| Score | Criteria |
+|-------|----------|
+| 1 | Requirement is explicit; no design decisions needed |
+| 2 | 1–2 decision points that need resolution before coding |
+| 3 | Architecture-level decisions; unknown patterns; research needed |
+
+### Dimension 4: Test Surface
+
+| Score | Criteria |
+|-------|----------|
+| 1 | Existing test file; trivial assertion additions |
+| 2 | New test file needed; mocking required |
+| 3 | Integration tests; DB fixtures; snapshot regeneration |
+
+### Dimension 5: Session Risk
+
+| Score | Criteria |
+|-------|----------|
+| 1 | Fits in one session; easy to resume |
+| 2 | May span sessions; partial state is safe |
+| 3 | Long-running; partial state is dangerous; handoff required |
+
+---
+
+## Decision Matrix
+
+| Total Score | Approach |
+|-------------|----------|
+| 5–7 | Plan Mode (in-head plan, no file needed) |
+| 8–10 | Light ExecPlan (phases only, no inline patterns) |
+| 11–13 | Full ExecPlan (all fields, inline patterns, phase gates) |
+| 14–15 | ExecPlan + parallel research before starting |
+
+---
+
+## Decomposition Rules
+
+When total ≥ 11, decompose into phases:
+
+1. **One phase = one deployable unit** — each phase leaves the codebase in a working state
+2. **Max 3 scenarios per phase** — more means the phase is too large; split it
+3. **Phase gate before next phase** — build + tests must pass at each boundary
+4. **No implicit dependencies between phases** — phase 2 must not assume phase 1 code style; document patterns inline
+
+## Anti-patterns
+
+- Scoring 1 on all dimensions then creating an ExecPlan → overhead without benefit
+- Scoring 3 on ambiguity without resolving decisions first → plan will fail
+- Skipping phase gates to go faster → regressions compound

package/skills/exec-plan/templates/plan.md

@@ -1,147 +1,147 @@
-# ExecPlan: {{FEATURE_NAME}}
-
-## Meta
-
-| Field | Value |
-|-------|-------|
-| SPEC | `.claude/vibe/specs/{{FEATURE_NAME}}.md` |
-| Feature | `.claude/vibe/features/{{FEATURE_NAME}}.feature` |
-| Generated | {{GENERATED_DATE}} |
-| Phases | {{PHASE_COUNT}} |
-| Scenarios | {{SCENARIO_COUNT}} |
-| Estimated effort | {{EFFORT_ESTIMATE}} |
-
----
-
-## Pre-flight Checks
-
-Run these before starting any phase. All must pass.
-
-- [ ] `npm run build` — clean build
-- [ ] `npx vitest run` — baseline tests pass ({{BASELINE_TEST_COUNT}} tests)
-- [ ] Required files exist:
-  - `{{REQUIRED_FILE_1}}`
-  - `{{REQUIRED_FILE_2}}`
-- [ ] Dependencies installed: `{{DEPENDENCY_CHECK_COMMAND}}`
-
----
-
-## Phase 1: {{PHASE_1_NAME}}
-
-### Environment
-
-| Item | Detail |
-|------|--------|
-| Files to modify | `{{PHASE_1_MODIFY_FILES}}` |
-| Files to create | `{{PHASE_1_CREATE_FILES}}` |
-| Dependencies | `{{PHASE_1_DEPENDENCIES}}` |
-| Pattern to follow | See inline snippet below |
-
-**Pattern (copy from codebase, do not paraphrase):**
-
-```typescript
-{{PHASE_1_PATTERN_SNIPPET}}
-```
-
-### Scenario 1.1: {{SCENARIO_1_1_NAME}}
-
-**REQ**: {{REQ_ID}}
-
-**Given**: {{GIVEN_CONDITION}}
-→ Setup:
-```typescript
-{{SETUP_CODE}}
-```
-
-**When**: {{ACTION}}
-→ Implement in `{{TARGET_FILE}}`, after line containing `{{ANCHOR_TEXT}}`:
-```typescript
-{{IMPLEMENTATION_SNIPPET}}
-```
-Imports needed: `{{IMPORTS_LIST}}`
-
-**Then**: {{EXPECTED_RESULT}}
-→ Verify:
-```bash
-{{VERIFY_COMMAND}}
-```
-Expected output: `{{EXPECTED_OUTPUT}}`
-Fallback if fails: {{FALLBACK_INSTRUCTION}}
-
----
-
-### Scenario 1.2: {{SCENARIO_1_2_NAME}}
-
-**Given**: {{GIVEN_CONDITION}}
-→ Setup: {{SETUP_INSTRUCTION}}
-
-**When**: {{ACTION}}
-→ Implement: {{IMPLEMENTATION_INSTRUCTION}}
-
-**Then**: {{EXPECTED_RESULT}}
-→ Verify: `{{VERIFY_COMMAND}}`
-
----
-
-### Phase 1 Gate
-
-- [ ] `npm run build` — no type errors
-- [ ] `npx vitest run {{PHASE_1_TEST_FILES}}` — all pass
-- [ ] `npx tsc --noEmit` — clean
-
----
-
-## Phase 2: {{PHASE_2_NAME}}
-
-### Environment
-
-| Item | Detail |
-|------|--------|
-| Files to modify | `{{PHASE_2_MODIFY_FILES}}` |
-| Files to create | `{{PHASE_2_CREATE_FILES}}` |
-| Dependencies | `{{PHASE_2_DEPENDENCIES}}` |
-
-### Scenario 2.1: {{SCENARIO_2_1_NAME}}
-
-**Given**: {{GIVEN_CONDITION}}
-→ Setup: {{SETUP_INSTRUCTION}}
-
-**When**: {{ACTION}}
-→ Implement: {{IMPLEMENTATION_INSTRUCTION}}
-
-**Then**: {{EXPECTED_RESULT}}
-→ Verify: `{{VERIFY_COMMAND}}`
-
----
-
-### Phase 2 Gate
-
-- [ ] `npm run build`
-- [ ] `npx vitest run {{PHASE_2_TEST_FILES}}`
-- [ ] `npx tsc --noEmit`
-
----
-
-## Completion Criteria
-
-- [ ] All scenarios passing
-- [ ] Coverage: ≥ {{COVERAGE_THRESHOLD}}%
-- [ ] No regressions in existing tests
-- [ ] `npm run build` exits 0
-- [ ] RTM generated: `generateTraceabilityMatrix("{{FEATURE_NAME}}")`
-
----
-
-## Handoff (if incomplete)
-
-Save state before ending session:
-
-```
-save_memory("execplan-{{FEATURE_NAME}}", {
-  "last_completed": "Phase X, Scenario Y.Z",
-  "next_step": "{{NEXT_STEP_DESCRIPTION}}",
-  "blockers": "{{BLOCKERS_IF_ANY}}"
-})
-```
-
-Resume: `/vibe.utils --continue` → load this file.
+# ExecPlan: {{FEATURE_NAME}}
+
+## Meta
+
+| Field | Value |
+|-------|-------|
+| SPEC | `.claude/vibe/specs/{{FEATURE_NAME}}.md` |
+| Feature | `.claude/vibe/features/{{FEATURE_NAME}}.feature` |
+| Generated | {{GENERATED_DATE}} |
+| Phases | {{PHASE_COUNT}} |
+| Scenarios | {{SCENARIO_COUNT}} |
+| Estimated effort | {{EFFORT_ESTIMATE}} |
+
+---
+
+## Pre-flight Checks
+
+Run these before starting any phase. All must pass.
+
+- [ ] `npm run build` — clean build
+- [ ] `npx vitest run` — baseline tests pass ({{BASELINE_TEST_COUNT}} tests)
+- [ ] Required files exist:
+  - `{{REQUIRED_FILE_1}}`
+  - `{{REQUIRED_FILE_2}}`
+- [ ] Dependencies installed: `{{DEPENDENCY_CHECK_COMMAND}}`
+
+---
+
+## Phase 1: {{PHASE_1_NAME}}
+
+### Environment
+
+| Item | Detail |
+|------|--------|
+| Files to modify | `{{PHASE_1_MODIFY_FILES}}` |
+| Files to create | `{{PHASE_1_CREATE_FILES}}` |
+| Dependencies | `{{PHASE_1_DEPENDENCIES}}` |
+| Pattern to follow | See inline snippet below |
+
+**Pattern (copy from codebase, do not paraphrase):**
+
+```typescript
+{{PHASE_1_PATTERN_SNIPPET}}
+```
+
+### Scenario 1.1: {{SCENARIO_1_1_NAME}}
+
+**REQ**: {{REQ_ID}}
+
+**Given**: {{GIVEN_CONDITION}}
+→ Setup:
+```typescript
+{{SETUP_CODE}}
+```
+
+**When**: {{ACTION}}
+→ Implement in `{{TARGET_FILE}}`, after line containing `{{ANCHOR_TEXT}}`:
+```typescript
+{{IMPLEMENTATION_SNIPPET}}
+```
+Imports needed: `{{IMPORTS_LIST}}`
+
+**Then**: {{EXPECTED_RESULT}}
+→ Verify:
+```bash
+{{VERIFY_COMMAND}}
+```
+Expected output: `{{EXPECTED_OUTPUT}}`
+Fallback if fails: {{FALLBACK_INSTRUCTION}}
+
+---
+
+### Scenario 1.2: {{SCENARIO_1_2_NAME}}
+
+**Given**: {{GIVEN_CONDITION}}
+→ Setup: {{SETUP_INSTRUCTION}}
+
+**When**: {{ACTION}}
+→ Implement: {{IMPLEMENTATION_INSTRUCTION}}
+
+**Then**: {{EXPECTED_RESULT}}
+→ Verify: `{{VERIFY_COMMAND}}`
+
+---
+
+### Phase 1 Gate
+
+- [ ] `npm run build` — no type errors
+- [ ] `npx vitest run {{PHASE_1_TEST_FILES}}` — all pass
+- [ ] `npx tsc --noEmit` — clean
+
+---
+
+## Phase 2: {{PHASE_2_NAME}}
+
+### Environment
+
+| Item | Detail |
+|------|--------|
+| Files to modify | `{{PHASE_2_MODIFY_FILES}}` |
+| Files to create | `{{PHASE_2_CREATE_FILES}}` |
+| Dependencies | `{{PHASE_2_DEPENDENCIES}}` |
+
+### Scenario 2.1: {{SCENARIO_2_1_NAME}}
+
+**Given**: {{GIVEN_CONDITION}}
+→ Setup: {{SETUP_INSTRUCTION}}
+
+**When**: {{ACTION}}
+→ Implement: {{IMPLEMENTATION_INSTRUCTION}}
+
+**Then**: {{EXPECTED_RESULT}}
+→ Verify: `{{VERIFY_COMMAND}}`
+
+---
+
+### Phase 2 Gate
+
+- [ ] `npm run build`
+- [ ] `npx vitest run {{PHASE_2_TEST_FILES}}`
+- [ ] `npx tsc --noEmit`
+
+---
+
+## Completion Criteria
+
+- [ ] All scenarios passing
+- [ ] Coverage: ≥ {{COVERAGE_THRESHOLD}}%
+- [ ] No regressions in existing tests
+- [ ] `npm run build` exits 0
+- [ ] RTM generated: `generateTraceabilityMatrix("{{FEATURE_NAME}}")`
+
+---
+
+## Handoff (if incomplete)
+
+Save state before ending session:
+
+```
+save_memory("execplan-{{FEATURE_NAME}}", {
+  "last_completed": "Phase X, Scenario Y.Z",
+  "next_step": "{{NEXT_STEP_DESCRIPTION}}",
+  "blockers": "{{BLOCKERS_IF_ANY}}"
+})
+```
+
+Resume: `/vibe.utils --continue` → load this file.

package/skills/git-worktree/SKILL.md

@@ -1,73 +1,73 @@
----
-name: git-worktree
-tier: optional
-description: "Git Worktree for parallel branch work. Auto-activates for PR review, hotfix, parallel testing, or working on multiple branches simultaneously."
-triggers: [worktree, PR review, hotfix, parallel branch, multiple branches]
-priority: 50
----
-
-# Git Worktree
-
-## Pre-check (K1)
-
-> Do you need to work on another branch without losing current work? If you can just `git stash` and switch, worktree may be overkill.
-
-## Core Commands
-
-```bash
-# Create worktree for PR review
-git worktree add ../review-{pr_number} origin/pr/{pr_number}
-
-# Create worktree with new branch (hotfix)
-git worktree add -b hotfix/urgent ../hotfix main
-
-# List all worktrees
-git worktree list
-
-# Remove when done
-git worktree remove ../review-{pr_number}
-
-# Clean up stale entries
-git worktree prune
-```
-
-## PR Review Workflow
-
-```
-1. git worktree add ../review-123 origin/pr/123
-2. cd ../review-123
-3. npm install && npm test
-4. Run review agents
-5. cd - && git worktree remove ../review-123
-```
-
-## Hotfix Workflow
-
-```
-1. git worktree add -b hotfix/critical ../hotfix main
-2. cd ../hotfix
-3. Fix bug → commit → push
-4. cd - && git worktree remove ../hotfix
-```
-
-## Naming Convention
-
-```bash
-../review-{pr_number}         # PR review
-../hotfix-{issue_number}      # Hotfix
-../experiment-{feature_name}  # Experiment
-```
-
-## Troubleshooting
-
-| Error | Fix |
-|-------|-----|
-| "already checked out" | Branch is in another worktree — `git worktree list`, then remove |
-| Locked worktree | `git worktree unlock <path>` |
-| Stale worktree | `git worktree prune` |
-
-## Done Criteria (K4)
-
-- [ ] Worktree created and work completed in isolation
-- [ ] Worktree removed after work is done
-- [ ] No stale worktrees left (`git worktree list` clean)
+---
+name: git-worktree
+tier: optional
+description: "Git Worktree for parallel branch work. Auto-activates for PR review, hotfix, parallel testing, or working on multiple branches simultaneously."
+triggers: [worktree, PR review, hotfix, parallel branch, multiple branches]
+priority: 50
+---
+
+# Git Worktree
+
+## Pre-check (K1)
+
+> Do you need to work on another branch without losing current work? If you can just `git stash` and switch, worktree may be overkill.
+
+## Core Commands
+
+```bash
+# Create worktree for PR review
+git worktree add ../review-{pr_number} origin/pr/{pr_number}
+
+# Create worktree with new branch (hotfix)
+git worktree add -b hotfix/urgent ../hotfix main
+
+# List all worktrees
+git worktree list
+
+# Remove when done
+git worktree remove ../review-{pr_number}
+
+# Clean up stale entries
+git worktree prune
+```
+
+## PR Review Workflow
+
+```
+1. git worktree add ../review-123 origin/pr/123
+2. cd ../review-123
+3. npm install && npm test
+4. Run review agents
+5. cd - && git worktree remove ../review-123
+```
+
+## Hotfix Workflow
+
+```
+1. git worktree add -b hotfix/critical ../hotfix main
+2. cd ../hotfix
+3. Fix bug → commit → push
+4. cd - && git worktree remove ../hotfix
+```
+
+## Naming Convention
+
+```bash
+../review-{pr_number}         # PR review
+../hotfix-{issue_number}      # Hotfix
+../experiment-{feature_name}  # Experiment
+```
+
+## Troubleshooting
+
+| Error | Fix |
+|-------|-----|
+| "already checked out" | Branch is in another worktree — `git worktree list`, then remove |
+| Locked worktree | `git worktree unlock <path>` |
+| Stale worktree | `git worktree prune` |
+
+## Done Criteria (K4)
+
+- [ ] Worktree created and work completed in isolation
+- [ ] Worktree removed after work is done
+- [ ] No stale worktrees left (`git worktree list` clean)