dino-spec 13.6.1 → 14.0.0

package/dist/skills/index.js

@@ -5,8 +5,8 @@
  * Each skill represents a workflow phase with appropriate tools and context.
  */
 import { join } from 'path';
-import { FileSystem } from '../utils/file-system.js';
 import { VERSION } from '../core/config.js';
+import { FileSystem } from '../utils/file-system.js';
 /**
  * Generate frontmatter YAML from options
  */
@@ -55,102 +55,102 @@ const PHASE_SKILLS = [
             allowedTools: ['Read', 'Grep', 'Glob', 'AskUserQuestion', 'TodoWrite', 'Task'],
             disallowedTools: ['Edit', 'Write', 'Bash'],
         },
-        content: `# 📋 Spec Phase
-
-Intelligent specification kit that analyzes prompts, clarifies requirements, and gates implementation until 80% confidence is reached.
-
-## Auto-Trigger
-
-This skill auto-triggers when ambiguity score > 40. Can also be invoked manually via \`/dino.spec\`.
-
-## Algorithm
-
-### Stage 0: Triage
-
-1. **Check session context**
-   - If active focus/recent work exists:
-     - Ask: "I see you were working on [focus area]. Is this related?"
-     - If yes: Build on existing context
-     - If no: Fresh analysis mode
-
-2. **Detect multi-part requests**
-   - Look for: "and", "also", numbered lists, multiple verbs
-   - If multi-part detected:
-     - Split into discrete tasks
-     - Present recommended order
-     - Run spec-kit on FIRST task only
-
-3. **Calculate complexity score (0-100)**
-
-### Stage 1: Mode Selection
-
-| Complexity | Ambiguity | Mode |
-|------------|-----------|------|
-| < 30 | < 20 | SKIP - proceed directly |
-| < 30 | >= 20 | LIGHTWEIGHT - quick check |
-| >= 30 | * | FULL - thorough analysis |
-
-### Stage 2a: Lightweight Mode
-
-For low complexity requests:
-
-1. Quick confidence check
-2. If quick_confidence >= 80%: One-liner confirmation, proceed
-3. If quick_confidence < 80%: Escalate to FULL mode
-
-### Stage 2b: Full Mode
-
-**RESEARCH-FIRST** (exploratory requests):
-1. Scout codebase for patterns
-2. Present 2-3 concrete options
-3. Targeted questions after direction chosen
-4. Iterate until confidence >= 80%
-
-**QUESTIONS-FIRST** (specific but unclear):
-1. Identify uncertainties: Where? What? When?
-2. Ask targeted questions
-3. Research only if complexity revealed
-4. Iterate until confidence >= 80%
-
-## Complexity Scoring
-
-- **Ambiguity (0-25)**: vague verbs, missing details, unclear success
-- **Scope (0-25)**: multiple components, cross-cutting, file count
-- **Risk (0-25)**: security, data, breaking changes
-- **Novelty (0-25)**: new patterns, external deps, unfamiliar domain
-
-## Confidence Gate
-
-**CRITICAL: Implementation is BLOCKED until confidence reaches threshold**
-
-| Task Type | Confidence Gate | Criteria |
-|-----------|-----------------|----------|
-| Normal tasks | 80% | Default for most tasks |
-| Ralph-eligible tasks | 90% | complexity > 70, 3+ parts, breaking changes |
-
-### Ralph Loop Eligibility
-
-A task is Ralph-eligible (requires 90% confidence) when:
-- **High complexity:** Score > 70
-- **Multi-story:** 3+ distinct parts
-- **Breaking changes:** System-wide impact (with scope >= 15)
-- **Cross-cutting:** Affects entire codebase (scope >= 20)
-
-When Ralph-eligible:
-1. Higher gate ensures thorough understanding before large-scale work
-2. After reaching 90% confidence, recommend \`/dino.ralph\`
-3. Ralph provides fresh-context iterations with learning persistence
-
-If below threshold after 5 question rounds, present assumptions for explicit validation.
-
-## Output
-
-Update \`.dino/session.md\` with:
-- Requirements with acceptance criteria
-- Clarifications log
-- Validated assumptions
-- Risk assessment
-- Recommended next step (/dino.nest or /dino.hunt)
+        content: `# 📋 Spec Phase
+
+Intelligent specification kit that analyzes prompts, clarifies requirements, and gates implementation until 80% confidence is reached.
+
+## Auto-Trigger
+
+This skill auto-triggers when ambiguity score > 40. Can also be invoked manually via \`/dino.spec\`.
+
+## Algorithm
+
+### Stage 0: Triage
+
+1. **Check session context**
+   - If active focus/recent work exists:
+     - Ask: "I see you were working on [focus area]. Is this related?"
+     - If yes: Build on existing context
+     - If no: Fresh analysis mode
+
+2. **Detect multi-part requests**
+   - Look for: "and", "also", numbered lists, multiple verbs
+   - If multi-part detected:
+     - Split into discrete tasks
+     - Present recommended order
+     - Run spec-kit on FIRST task only
+
+3. **Calculate complexity score (0-100)**
+
+### Stage 1: Mode Selection
+
+| Complexity | Ambiguity | Mode |
+|------------|-----------|------|
+| < 30 | < 20 | SKIP - proceed directly |
+| < 30 | >= 20 | LIGHTWEIGHT - quick check |
+| >= 30 | * | FULL - thorough analysis |
+
+### Stage 2a: Lightweight Mode
+
+For low complexity requests:
+
+1. Quick confidence check
+2. If quick_confidence >= 80%: One-liner confirmation, proceed
+3. If quick_confidence < 80%: Escalate to FULL mode
+
+### Stage 2b: Full Mode
+
+**RESEARCH-FIRST** (exploratory requests):
+1. Scout codebase for patterns
+2. Present 2-3 concrete options
+3. Targeted questions after direction chosen
+4. Iterate until confidence >= 80%
+
+**QUESTIONS-FIRST** (specific but unclear):
+1. Identify uncertainties: Where? What? When?
+2. Ask targeted questions
+3. Research only if complexity revealed
+4. Iterate until confidence >= 80%
+
+## Complexity Scoring
+
+- **Ambiguity (0-25)**: vague verbs, missing details, unclear success
+- **Scope (0-25)**: multiple components, cross-cutting, file count
+- **Risk (0-25)**: security, data, breaking changes
+- **Novelty (0-25)**: new patterns, external deps, unfamiliar domain
+
+## Confidence Gate
+
+**CRITICAL: Implementation is BLOCKED until confidence reaches threshold**
+
+| Task Type | Confidence Gate | Criteria |
+|-----------|-----------------|----------|
+| Normal tasks | 80% | Default for most tasks |
+| Ralph-eligible tasks | 90% | complexity > 70, 3+ parts, breaking changes |
+
+### Ralph Loop Eligibility
+
+A task is Ralph-eligible (requires 90% confidence) when:
+- **High complexity:** Score > 70
+- **Multi-story:** 3+ distinct parts
+- **Breaking changes:** System-wide impact (with scope >= 15)
+- **Cross-cutting:** Affects entire codebase (scope >= 20)
+
+When Ralph-eligible:
+1. Higher gate ensures thorough understanding before large-scale work
+2. After reaching 90% confidence, recommend \`/dino.ralph\`
+3. Ralph provides fresh-context iterations with learning persistence
+
+If below threshold after 5 question rounds, present assumptions for explicit validation.
+
+## Output
+
+Update \`.dino/session.md\` with:
+- Requirements with acceptance criteria
+- Clarifications log
+- Validated assumptions
+- Risk assessment
+- Recommended next step (/dino.nest or /dino.hunt)
 `,
     },
     {
@@ -166,37 +166,37 @@ Update \`.dino/session.md\` with:
             effort: 'low',
             allowedTools: ['Read', 'Grep', 'Glob', 'AskUserQuestion', 'TodoWrite'],
         },
-        content: `# 🦕 Discover Phase
-
-Capture and clarify requirements from user prompts.
-
-## Workflow
-
-1. **Analyze Request**
-   - Parse user's intent and goals
-   - Identify explicit requirements
-   - Note implicit assumptions
-
-2. **Gather Context**
-   - Read relevant existing code
-   - Check session.md for prior context
-   - Review related files
-
-3. **Document Requirements**
-   - Update session.md Notes section
-   - Create TodoWrite items for actionable items
-   - Record decisions and constraints
-
-4. **Clarify if Needed**
-   - Use AskUserQuestion for ambiguities
-   - Validate understanding before proceeding
-
-## Output
-
-After discovery, update \`.dino/session.md\` with:
-- Clear requirements summary
-- Key constraints identified
-- Open questions (if any)
+        content: `# 🦕 Discover Phase
+
+Capture and clarify requirements from user prompts.
+
+## Workflow
+
+1. **Analyze Request**
+   - Parse user's intent and goals
+   - Identify explicit requirements
+   - Note implicit assumptions
+
+2. **Gather Context**
+   - Read relevant existing code
+   - Check session.md for prior context
+   - Review related files
+
+3. **Document Requirements**
+   - Update session.md Notes section
+   - Create TodoWrite items for actionable items
+   - Record decisions and constraints
+
+4. **Clarify if Needed**
+   - Use AskUserQuestion for ambiguities
+   - Validate understanding before proceeding
+
+## Output
+
+After discovery, update \`.dino/session.md\` with:
+- Clear requirements summary
+- Key constraints identified
+- Open questions (if any)
 `,
     },
     {
@@ -213,33 +213,33 @@ After discovery, update \`.dino/session.md\` with:
             allowedTools: ['Read', 'Grep', 'Glob', 'Task', 'WebSearch', 'WebFetch'],
             disallowedTools: ['Edit', 'Write', 'Bash'],
         },
-        content: `# 🔍 Scout Phase
-
-Research existing patterns and explore implementation options.
-
-## Workflow
-
-1. **Explore Codebase**
-   - Search for similar patterns
-   - Review existing implementations
-   - Identify reusable components
-
-2. **Research Options**
-   - Compare approaches
-   - Check documentation
-   - Review best practices
-
-3. **Document Findings**
-   - List viable options with pros/cons
-   - Note dependencies and risks
-   - Identify technical constraints
-
-## Output
-
-Research summary with:
-- Existing patterns found
-- Implementation options
-- Recommended approach
+        content: `# 🔍 Scout Phase
+
+Research existing patterns and explore implementation options.
+
+## Workflow
+
+1. **Explore Codebase**
+   - Search for similar patterns
+   - Review existing implementations
+   - Identify reusable components
+
+2. **Research Options**
+   - Compare approaches
+   - Check documentation
+   - Review best practices
+
+3. **Document Findings**
+   - List viable options with pros/cons
+   - Note dependencies and risks
+   - Identify technical constraints
+
+## Output
+
+Research summary with:
+- Existing patterns found
+- Implementation options
+- Recommended approach
 `,
     },
     {
@@ -255,33 +255,33 @@ Research summary with:
             effort: 'low',
             allowedTools: ['Read', 'AskUserQuestion'],
         },
-        content: `# 🐕 Sniff Phase
-
-Detect and resolve ambiguities before implementation.
-
-## Workflow
-
-1. **Identify Ambiguities**
-   - Review requirements for unclear points
-   - Check for conflicting constraints
-   - Note missing information
-
-2. **Ask Questions**
-   - Use AskUserQuestion with clear options
-   - Prioritize blocking questions
-   - Group related questions
-
-3. **Record Decisions**
-   - Update session.md with answers
-   - Document design decisions
-   - Note any deferred items
-
-## Question Guidelines
-
-- Keep questions focused and specific
-- Provide 2-4 clear options when possible
-- Include recommended option with rationale
-- Use multiSelect when choices aren't exclusive
+        content: `# 🐕 Sniff Phase
+
+Detect and resolve ambiguities before implementation.
+
+## Workflow
+
+1. **Identify Ambiguities**
+   - Review requirements for unclear points
+   - Check for conflicting constraints
+   - Note missing information
+
+2. **Ask Questions**
+   - Use AskUserQuestion with clear options
+   - Prioritize blocking questions
+   - Group related questions
+
+3. **Record Decisions**
+   - Update session.md with answers
+   - Document design decisions
+   - Note any deferred items
+
+## Question Guidelines
+
+- Keep questions focused and specific
+- Provide 2-4 clear options when possible
+- Include recommended option with rationale
+- Use multiSelect when choices aren't exclusive
 `,
     },
     {
@@ -298,52 +298,52 @@ Detect and resolve ambiguities before implementation.
             allowedTools: ['Read', 'Grep', 'Glob', 'EnterPlanMode', 'TodoWrite'],
             disallowedTools: ['Edit', 'Write', 'Bash'],
         },
-        content: `# 🪺 Nest Phase
-
-Plan the implementation approach for user approval.
-
-## Workflow
-
-1. **Enter Plan Mode**
-   - Use EnterPlanMode for non-trivial tasks
-   - Gather full context before planning
-
-2. **Design Approach**
-   - Outline file changes needed
-   - Identify dependencies
-   - Plan execution order
-
-3. **Create Plan**
-   - Write structured implementation plan
-   - Include verification steps
-   - Note rollback strategy
-
-4. **Get Approval**
-   - Use ExitPlanMode to present plan
-   - Wait for user confirmation
-   - Adjust based on feedback
-
-## Plan Template
-
-\`\`\`markdown
-## Summary
-Brief description of what will be implemented
-
-## Files to Modify
-- file1.ts - description
-- file2.ts - description
-
-## Files to Create
-- newfile.ts - purpose
-
-## Execution Steps
-1. Step one
-2. Step two
-...
-
-## Verification
-- How to verify success
-\`\`\`
+        content: `# 🪺 Nest Phase
+
+Plan the implementation approach for user approval.
+
+## Workflow
+
+1. **Enter Plan Mode**
+   - Use EnterPlanMode for non-trivial tasks
+   - Gather full context before planning
+
+2. **Design Approach**
+   - Outline file changes needed
+   - Identify dependencies
+   - Plan execution order
+
+3. **Create Plan**
+   - Write structured implementation plan
+   - Include verification steps
+   - Note rollback strategy
+
+4. **Get Approval**
+   - Use ExitPlanMode to present plan
+   - Wait for user confirmation
+   - Adjust based on feedback
+
+## Plan Template
+
+\`\`\`markdown
+## Summary
+Brief description of what will be implemented
+
+## Files to Modify
+- file1.ts - description
+- file2.ts - description
+
+## Files to Create
+- newfile.ts - purpose
+
+## Execution Steps
+1. Step one
+2. Step two
+...
+
+## Verification
+- How to verify success
+\`\`\`
 `,
     },
     {
@@ -359,33 +359,33 @@ Brief description of what will be implemented
             effort: 'low',
             allowedTools: ['Read', 'TodoWrite'],
         },
-        content: `# 🥚 Hatch Phase
-
-Break the approved plan into atomic, trackable tasks.
-
-## Workflow
-
-1. **Decompose Plan**
-   - Split into atomic tasks
-   - Identify dependencies
-   - Order by execution sequence
-
-2. **Create Todos**
-   - Use TodoWrite with clear items
-   - Include both content and activeForm
-   - Mark first task as in_progress
-
-3. **Validate Coverage**
-   - Check all plan items are covered
-   - Include verification tasks
-   - Add cleanup tasks if needed
-
-## Todo Guidelines
-
-- Each todo should be completable in one action
-- Include success criteria
-- Order reflects execution sequence
-- Group related tasks
+        content: `# 🥚 Hatch Phase
+
+Break the approved plan into atomic, trackable tasks.
+
+## Workflow
+
+1. **Decompose Plan**
+   - Split into atomic tasks
+   - Identify dependencies
+   - Order by execution sequence
+
+2. **Create Todos**
+   - Use TodoWrite with clear items
+   - Include both content and activeForm
+   - Mark first task as in_progress
+
+3. **Validate Coverage**
+   - Check all plan items are covered
+   - Include verification tasks
+   - Add cleanup tasks if needed
+
+## Todo Guidelines
+
+- Each todo should be completable in one action
+- Include success criteria
+- Order reflects execution sequence
+- Group related tasks
 `,
     },
     {
@@ -401,33 +401,33 @@ Break the approved plan into atomic, trackable tasks.
             effort: 'medium',
             allowedTools: ['Read', 'Edit', 'Write', 'Bash', 'Glob', 'Grep', 'TodoWrite'],
         },
-        content: `# 🦖 Hunt Phase
-
-Execute implementation tasks methodically.
-
-## Workflow
-
-1. **Execute Todos**
-   - Work through TodoWrite items in order
-   - Mark each as complete when done
-   - Update session.md focus as you work
-
-2. **Track Progress**
-   - Complete one task before starting next
-   - Note any blockers immediately
-   - Update progress signals
-
-3. **Maintain Context**
-   - Keep session.md current
-   - Track file changes
-   - Note decisions made during implementation
-
-## Best Practices
-
-- Read files before editing
-- Test changes incrementally
-- Commit logical chunks
-- Update todos as you complete them
+        content: `# 🦖 Hunt Phase
+
+Execute implementation tasks methodically.
+
+## Workflow
+
+1. **Execute Todos**
+   - Work through TodoWrite items in order
+   - Mark each as complete when done
+   - Update session.md focus as you work
+
+2. **Track Progress**
+   - Complete one task before starting next
+   - Note any blockers immediately
+   - Update progress signals
+
+3. **Maintain Context**
+   - Keep session.md current
+   - Track file changes
+   - Note decisions made during implementation
+
+## Best Practices
+
+- Read files before editing
+- Test changes incrementally
+- Commit logical chunks
+- Update todos as you complete them
 `,
     },
     {
@@ -443,38 +443,38 @@ Execute implementation tasks methodically.
             effort: 'low',
             allowedTools: ['Read', 'Bash', 'Edit', 'TodoWrite'],
         },
-        content: `# ⏳ Aging Phase
-
-Verify implementation through testing and validation.
-
-## Workflow
-
-1. **Run Tests**
-   - Execute test suite
-   - Review failures
-   - Fix issues found
-
-2. **Verify Build**
-   - Run build command
-   - Check for errors
-   - Validate output
-
-3. **Check Lint**
-   - Run linter
-   - Fix violations
-   - Verify clean
-
-4. **Manual Verification**
-   - Test key functionality
-   - Verify requirements met
-   - Check edge cases
-
-## Success Criteria
-
-- All tests passing
-- Build succeeds
-- No lint errors
-- Requirements verified
+        content: `# ⏳ Aging Phase
+
+Verify implementation through testing and validation.
+
+## Workflow
+
+1. **Run Tests**
+   - Execute test suite
+   - Review failures
+   - Fix issues found
+
+2. **Verify Build**
+   - Run build command
+   - Check for errors
+   - Validate output
+
+3. **Check Lint**
+   - Run linter
+   - Fix violations
+   - Verify clean
+
+4. **Manual Verification**
+   - Test key functionality
+   - Verify requirements met
+   - Check edge cases
+
+## Success Criteria
+
+- All tests passing
+- Build succeeds
+- No lint errors
+- Requirements verified
 `,
     },
     {
@@ -490,41 +490,41 @@ Verify implementation through testing and validation.
             effort: 'low',
             allowedTools: ['Read', 'Edit', 'Write', 'Bash'],
         },
-        content: `# 🦴 Fossil Phase
-
-Archive completed work and prepare for next task.
-
-## Workflow
-
-1. **Document Changes**
-   - Update relevant documentation
-   - Add code comments if needed
-   - Update CHANGELOG if applicable
-
-2. **Clean Session**
-   - Clear completed todos
-   - Resolve blockers
-   - Archive session if significant
-
-3. **Commit Work**
-   - Stage all changes
-   - Write descriptive commit message
-   - Push if appropriate
-
-4. **Prepare Next**
-   - Clear session focus
-   - Note follow-up items
-   - Reset for next task
-
-## Commit Message Template
-
-\`\`\`
-<type>(<scope>): <description>
-
-<body>
-
-Co-Authored-By: Claude <noreply@anthropic.com>
-\`\`\`
+        content: `# 🦴 Fossil Phase
+
+Archive completed work and prepare for next task.
+
+## Workflow
+
+1. **Document Changes**
+   - Update relevant documentation
+   - Add code comments if needed
+   - Update CHANGELOG if applicable
+
+2. **Clean Session**
+   - Clear completed todos
+   - Resolve blockers
+   - Archive session if significant
+
+3. **Commit Work**
+   - Stage all changes
+   - Write descriptive commit message
+   - Push if appropriate
+
+4. **Prepare Next**
+   - Clear session focus
+   - Note follow-up items
+   - Reset for next task
+
+## Commit Message Template
+
+\`\`\`
+<type>(<scope>): <description>
+
+<body>
+
+Co-Authored-By: Claude <noreply@anthropic.com>
+\`\`\`
 `,
     },
 ];
@@ -545,49 +545,49 @@ const UTILITY_SKILLS = [
             effort: 'low',
             allowedTools: ['Read', 'Bash', 'mcp__dino__dino_status', 'mcp__dino__dino_task_status'],
         },
-        content: `# dino.handoff
-
-Load context from a previous session handoff.
-
-## Usage
-
-Run \`/dino.handoff\` at the start of a new session to restore context from a previous session.
-
-## What it loads
-
-- **Active plan** from \`.dino/plans/active.json\` - Current implementation plan
-- **Session state** from \`.dino/session.md\` - Focus, phase, blockers
-- **Task checkpoints** from \`.dino/checkpoints/\` - Progress context
-- **Handoff notes** from \`.dino/handoff/latest.md\` - Important notes for continuation
-
-## Instructions
-
-1. Read \`.dino/handoff/latest.md\` if it exists
-2. Read \`.dino/session.md\` for current session state
-3. Check \`.dino/plans/active.json\` for active plan
-4. Use \`mcp__dino__dino_status\` to get session summary
-5. Use \`mcp__dino__dino_task_status\` if tasks are in progress
-6. Summarize the context for the user with clear next steps
-
-## Example Output
-
-\`\`\`
-# Session Handoff
-
-**Last Session:** 2025-01-19 18:30
-**Plan:** dino-hud v2 (3/10 steps)
-**Phase:** iterating
-**Focus:** src/hud/render/
-
-## Next Steps
-1. Create context-health.ts renderer
-2. Update layouts.ts with new format
-3. Test the preview command
-
-## Notes
-- Git branch and model display working
-- Need to test context health thresholds
-\`\`\`
+        content: `# dino.handoff
+
+Load context from a previous session handoff.
+
+## Usage
+
+Run \`/dino.handoff\` at the start of a new session to restore context from a previous session.
+
+## What it loads
+
+- **Active plan** from \`.dino/plans/active.json\` - Current implementation plan
+- **Session state** from \`.dino/session.md\` - Focus, phase, blockers
+- **Task checkpoints** from \`.dino/checkpoints/\` - Progress context
+- **Handoff notes** from \`.dino/handoff/latest.md\` - Important notes for continuation
+
+## Instructions
+
+1. Read \`.dino/handoff/latest.md\` if it exists
+2. Read \`.dino/session.md\` for current session state
+3. Check \`.dino/plans/active.json\` for active plan
+4. Use \`mcp__dino__dino_status\` to get session summary
+5. Use \`mcp__dino__dino_task_status\` if tasks are in progress
+6. Summarize the context for the user with clear next steps
+
+## Example Output
+
+\`\`\`
+# Session Handoff
+
+**Last Session:** 2025-01-19 18:30
+**Plan:** dino-hud v2 (3/10 steps)
+**Phase:** iterating
+**Focus:** src/hud/render/
+
+## Next Steps
+1. Create context-health.ts renderer
+2. Update layouts.ts with new format
+3. Test the preview command
+
+## Notes
+- Git branch and model display working
+- Need to test context health thresholds
+\`\`\`
 `,
     },
     {
@@ -601,47 +601,59 @@ Run \`/dino.handoff\` at the start of a new session to restore context from a pr
             model: 'sonnet',
             context: 'fork',
             effort: 'high',
-            allowedTools: ['Read', 'Edit', 'Write', 'Bash', 'Glob', 'Grep', 'Task', 'TaskCreate', 'TaskUpdate', 'TaskList', 'AskUserQuestion'],
+            allowedTools: [
+                'Read',
+                'Edit',
+                'Write',
+                'Bash',
+                'Glob',
+                'Grep',
+                'Task',
+                'TaskCreate',
+                'TaskUpdate',
+                'TaskList',
+                'AskUserQuestion',
+            ],
         },
-        content: `# 🔄 Ralph Loop
-
-Fresh-context iterative execution for large-scale multi-story work.
-
-## Prerequisites
-
-Before starting Ralph Loop:
-1. Run \`/dino.spec\` and achieve **90%+ confidence**
-2. Have a PRD with stories in the required format
-
-## Algorithm
-
-1. **Initialize** - Parse PRD, create progress file, set max 10 iterations
-2. **Iterate** - For each story:
-   - Create git checkpoint
-   - Build sub-agent context (~2K tokens)
-   - Spawn fresh sub-agent via Task tool
-   - Run test command
-   - If pass: mark complete, commit
-   - If fail: extract learnings, retry (max 2 per story)
-3. **Complete** - Report final status
-
-## Story Format
-
-\`\`\`markdown
-### Story: {title}
-**ID:** {unique_id}
-**Files:** file1.ts, file2.ts
-**Acceptance Criteria:**
-- [ ] Criterion 1
-- [ ] Criterion 2
-**Test Command:** vitest run src/path
-\`\`\`
-
-## Limits
-
-- Max 10 total iterations
-- Max 2 iterations per story (then manual review)
-- Fresh context each iteration (no history accumulation)
+        content: `# 🔄 Ralph Loop
+
+Fresh-context iterative execution for large-scale multi-story work.
+
+## Prerequisites
+
+Before starting Ralph Loop:
+1. Run \`/dino.spec\` and achieve **90%+ confidence**
+2. Have a PRD with stories in the required format
+
+## Algorithm
+
+1. **Initialize** - Parse PRD, create progress file, set max 10 iterations
+2. **Iterate** - For each story:
+   - Create git checkpoint
+   - Build sub-agent context (~2K tokens)
+   - Spawn fresh sub-agent via Task tool
+   - Run test command
+   - If pass: mark complete, commit
+   - If fail: extract learnings, retry (max 2 per story)
+3. **Complete** - Report final status
+
+## Story Format
+
+\`\`\`markdown
+### Story: {title}
+**ID:** {unique_id}
+**Files:** file1.ts, file2.ts
+**Acceptance Criteria:**
+- [ ] Criterion 1
+- [ ] Criterion 2
+**Test Command:** vitest run src/path
+\`\`\`
+
+## Limits
+
+- Max 10 total iterations
+- Max 2 iterations per story (then manual review)
+- Fresh context each iteration (no history accumulation)
 `,
     },
     {
@@ -657,21 +669,21 @@ Before starting Ralph Loop:
             effort: 'low',
             allowedTools: ['Read', 'Bash'],
         },
-        content: `# 📊 Status
-
-Quick check of current session state.
-
-## Usage
-
-Run \`/dino.status\` to see:
-- Current focus area
-- Test/build/lint status
-- Active blockers
-- Recent changes
-
-## Output
-
-Reads \`.dino/session.md\` and displays formatted status.
+        content: `# 📊 Status
+
+Quick check of current session state.
+
+## Usage
+
+Run \`/dino.status\` to see:
+- Current focus area
+- Test/build/lint status
+- Active blockers
+- Recent changes
+
+## Output
+
+Reads \`.dino/session.md\` and displays formatted status.
 `,
     },
     {
@@ -687,57 +699,57 @@ Reads \`.dino/session.md\` and displays formatted status.
             effort: 'high',
             allowedTools: ['Read', 'Edit', 'Write', 'Bash', 'AskUserQuestion', 'Glob', 'Grep'],
         },
-        content: `# 🚀 Release
-
-Release workflow with intelligent documentation updates.
-
-## Workflow
-
-1. **Analyze Context for Doc Updates**
-   - Check if README.md, ARCHITECTURE.md, CLAUDE.md are in context
-   - Detect if changes warrant documentation updates:
-     - New features → README.md
-     - Architecture changes → ARCHITECTURE.md
-     - Pattern/command changes → CLAUDE.md
-   - If file not in context, only read if update is likely needed
-
-2. **Confirm Doc Updates**
-   - Use AskUserQuestion to confirm which docs to update
-   - Options: Update all detected, Select specific, Skip doc updates
-   - Show reasoning for each suggested update
-
-3. **Update Documentation**
-   - Apply confirmed documentation changes
-   - Keep updates focused and minimal
-
-4. **Execute Release**
-   - Run build: \`node build.js\`
-   - Run tests: \`vitest run\`
-   - If tests pass, bump version in package.json
-   - Publish to npm: \`npm publish\`
-   - Verify publish succeeded
-
-5. **Commit and Push**
-   - Stage all changes
-   - Create release commit: \`chore: release vX.Y.Z\`
-   - Push to remote
-
-## Doc Update Detection Rules
-
-| Change Type | Documentation |
-|-------------|---------------|
-| New feature/command | README.md |
-| API changes | README.md, ARCHITECTURE.md |
-| Architecture changes | ARCHITECTURE.md |
-| Pattern changes | CLAUDE.md |
-| Config changes | CLAUDE.md |
-| Bug fixes only | None |
-
-## Context Efficiency
-
-- Uses \`context: inherit\` to leverage already-loaded files
-- Only reads files not in context when update is detected
-- Minimizes token usage by analyzing existing context first
+        content: `# 🚀 Release
+
+Release workflow with intelligent documentation updates.
+
+## Workflow
+
+1. **Analyze Context for Doc Updates**
+   - Check if README.md, ARCHITECTURE.md, CLAUDE.md are in context
+   - Detect if changes warrant documentation updates:
+     - New features → README.md
+     - Architecture changes → ARCHITECTURE.md
+     - Pattern/command changes → CLAUDE.md
+   - If file not in context, only read if update is likely needed
+
+2. **Confirm Doc Updates**
+   - Use AskUserQuestion to confirm which docs to update
+   - Options: Update all detected, Select specific, Skip doc updates
+   - Show reasoning for each suggested update
+
+3. **Update Documentation**
+   - Apply confirmed documentation changes
+   - Keep updates focused and minimal
+
+4. **Execute Release**
+   - Run build: \`node build.js\`
+   - Run tests: \`vitest run\`
+   - If tests pass, bump version in package.json
+   - Publish to npm: \`npm publish\`
+   - Verify publish succeeded
+
+5. **Commit and Push**
+   - Stage all changes
+   - Create release commit: \`chore: release vX.Y.Z\`
+   - Push to remote
+
+## Doc Update Detection Rules
+
+| Change Type | Documentation |
+|-------------|---------------|
+| New feature/command | README.md |
+| API changes | README.md, ARCHITECTURE.md |
+| Architecture changes | ARCHITECTURE.md |
+| Pattern changes | CLAUDE.md |
+| Config changes | CLAUDE.md |
+| Bug fixes only | None |
+
+## Context Efficiency
+
+- Uses \`context: inherit\` to leverage already-loaded files
+- Only reads files not in context when update is detected
+- Minimizes token usage by analyzing existing context first
 `,
     },
     {
@@ -753,97 +765,97 @@ Release workflow with intelligent documentation updates.
             effort: 'low',
             allowedTools: ['Read', 'Glob', 'Write', 'Bash'],
         },
-        content: `# Roadmap Management
-
-Efficiently manage roadmap lifecycle: read, update, and auto-cleanup.
-
-## Trigger Detection
-
-This skill auto-triggers when user prompts contain:
-- "continue roadmap", "roadmap progress", "resume roadmap"
-- "next phase", "what's next on roadmap"
-- "roadmap status", "check roadmap"
-
-## Workflow
-
-### 1. Load Active Roadmaps
-
-Read all files from \`.dino/roadmaps/*.md\`:
-
-\`\`\`bash
-ls .dino/roadmaps/*.md 2>/dev/null
-\`\`\`
-
-For each roadmap found, read and parse:
-- Title (first H1)
-- Phases with status (✅ = done, ⏳ = pending)
-- Current phase (first ⏳ phase)
-
-### 2. Display Summary
-
-Output format:
-\`\`\`
-## Active Roadmaps
-
-### {roadmap-name}
-Progress: {completed}/{total} phases ({percentage}%)
-Current: Phase {N}: {phase-name}
-Next tasks:
-- [ ] Task 1
-- [ ] Task 2
-\`\`\`
-
-### 3. On Completion
-
-When user completes phase work:
-
-1. **Update roadmap file** - Change \`⏳\` to \`✅\` for completed phase
-2. **Check if all complete** - If all phases are \`✅\`:
-   - Move to \`.dino/archives/{roadmap-name}-complete.md\`
-   - Add completion timestamp at top
-   - Remove from active roadmaps
-
-### 4. Auto-Archive Logic
-
-A roadmap is complete when:
-- All \`### Phase\` sections contain \`✅\` in their header
-- OR all \`- [ ]\` items are \`- [x]\`
-
-Archive command:
-\`\`\`bash
-mkdir -p .dino/archives
-mv .dino/roadmaps/{name}.md .dino/archives/{name}-complete.md
-\`\`\`
-
-## Output Minimization
-
-Keep output minimal for token efficiency:
-- Only show current phase details
-- Collapse completed phases to single line
-- Don't repeat full roadmap content
-
-## Integration
-
-Works with:
-- \`/dino.hunt\` - Implementation of roadmap tasks
-- \`/dino.aging\` - Verification before phase completion
-- \`/dino.fossil\` - Archives completed roadmaps
-
-## Example Session
-
-User: "continue roadmap"
-1. Read \`.dino/roadmaps/*.md\`
-2. Output summary of active roadmaps
-3. Show current phase tasks
-4. User completes tasks
-5. Update phase status
-6. If all done, archive roadmap
-
-## Notes
-
-- Roadmaps live in \`.dino/roadmaps/\` (active) or \`.dino/archives/\` (complete)
-- Use \`⏳\` for pending, \`✅\` for complete in phase headers
-- Archived roadmaps include completion date for reference
+        content: `# Roadmap Management
+
+Efficiently manage roadmap lifecycle: read, update, and auto-cleanup.
+
+## Trigger Detection
+
+This skill auto-triggers when user prompts contain:
+- "continue roadmap", "roadmap progress", "resume roadmap"
+- "next phase", "what's next on roadmap"
+- "roadmap status", "check roadmap"
+
+## Workflow
+
+### 1. Load Active Roadmaps
+
+Read all files from \`.dino/roadmaps/*.md\`:
+
+\`\`\`bash
+ls .dino/roadmaps/*.md 2>/dev/null
+\`\`\`
+
+For each roadmap found, read and parse:
+- Title (first H1)
+- Phases with status (✅ = done, ⏳ = pending)
+- Current phase (first ⏳ phase)
+
+### 2. Display Summary
+
+Output format:
+\`\`\`
+## Active Roadmaps
+
+### {roadmap-name}
+Progress: {completed}/{total} phases ({percentage}%)
+Current: Phase {N}: {phase-name}
+Next tasks:
+- [ ] Task 1
+- [ ] Task 2
+\`\`\`
+
+### 3. On Completion
+
+When user completes phase work:
+
+1. **Update roadmap file** - Change \`⏳\` to \`✅\` for completed phase
+2. **Check if all complete** - If all phases are \`✅\`:
+   - Move to \`.dino/archives/{roadmap-name}-complete.md\`
+   - Add completion timestamp at top
+   - Remove from active roadmaps
+
+### 4. Auto-Archive Logic
+
+A roadmap is complete when:
+- All \`### Phase\` sections contain \`✅\` in their header
+- OR all \`- [ ]\` items are \`- [x]\`
+
+Archive command:
+\`\`\`bash
+mkdir -p .dino/archives
+mv .dino/roadmaps/{name}.md .dino/archives/{name}-complete.md
+\`\`\`
+
+## Output Minimization
+
+Keep output minimal for token efficiency:
+- Only show current phase details
+- Collapse completed phases to single line
+- Don't repeat full roadmap content
+
+## Integration
+
+Works with:
+- \`/dino.hunt\` - Implementation of roadmap tasks
+- \`/dino.aging\` - Verification before phase completion
+- \`/dino.fossil\` - Archives completed roadmaps
+
+## Example Session
+
+User: "continue roadmap"
+1. Read \`.dino/roadmaps/*.md\`
+2. Output summary of active roadmaps
+3. Show current phase tasks
+4. User completes tasks
+5. Update phase status
+6. If all done, archive roadmap
+
+## Notes
+
+- Roadmaps live in \`.dino/roadmaps/\` (active) or \`.dino/archives/\` (complete)
+- Use \`⏳\` for pending, \`✅\` for complete in phase headers
+- Archived roadmaps include completion date for reference
 `,
     },
     {
@@ -860,96 +872,96 @@ User: "continue roadmap"
             allowedTools: ['Read', 'Grep', 'Glob', 'AskUserQuestion'],
             disallowedTools: ['Edit', 'Write', 'Bash', 'Task'],
         },
-        content: `# 🔒 Audit Phase
-
-**Strict gatekeeper that validates specifications before implementation.**
-
-This skill is the AUDITOR agent in the three-agent Ralph Gate system. It can also be used standalone to validate any specification.
-
-## Role
-
-You are an EXTREMELY STRICT auditor. Your job is to find problems, not approve things. Implementation should be BLOCKED by default unless everything is perfect.
-
-## Scoring System
-
-### 1. Specification Completeness (25 points)
-
-| Criterion | Points | Check |
-|-----------|--------|-------|
-| Clear problem statement | 5 | What problem are we solving? |
-| Explicit success criteria | 5 | How do we know when done? |
-| Defined scope boundaries | 5 | What is NOT included? |
-| Edge cases identified | 5 | What could go wrong? |
-| Error handling specified | 5 | How to handle failures? |
-
-### 2. Ambiguity Score (MUST BE ZERO)
-
-Check for these ambiguity types:
-
-| Type | Example | Fix Required |
-|------|---------|--------------|
-| Vague verbs | "improve", "enhance", "better" | Specify measurable outcome |
-| Undefined terms | "fast", "clean", "modern" | Define with numbers/criteria |
-| Implicit assumptions | "the usual way" | Make explicit |
-| Conflicting requirements | "fast AND thorough" | Prioritize or resolve |
-| Missing details | "handle errors" | Specify which errors, how |
-
-**Any ambiguity = AUTOMATIC REJECTION**
-
-### 3. PRD Quality (25 points) - For Ralph-eligible tasks
-
-| Criterion | Points | Check |
-|-----------|--------|-------|
-| Stories in correct format | 5 | Markdown headers, fields |
-| Each story has unique ID | 5 | story-1, story-2, etc. |
-| Each story has file list | 5 | Explicit file paths |
-| Each story has acceptance criteria | 5 | Checkbox list |
-| Each story has test command | 5 | Runnable command |
-
-### 4. Risk Mitigation (25 points)
-
-| Criterion | Points | Check |
-|-----------|--------|-------|
-| Security risks addressed | 5 | Input validation, auth, etc. |
-| Performance risks addressed | 5 | Scale, complexity, etc. |
-| Breaking changes identified | 5 | API changes, migrations |
-| Rollback plan exists | 5 | How to undo if needed |
-| Dependencies validated | 5 | External deps checked |
-
-### 5. Research Completeness (25 points) - When research provided
-
-| Criterion | Points | Check |
-|-----------|--------|-------|
-| All patterns documented | 5 | Similar code found |
-| Architecture understood | 5 | Fits existing structure |
-| Integration points mapped | 5 | Connections identified |
-| Test strategy defined | 5 | What tests to add/modify |
-| File impact complete | 5 | All affected files listed |
-
-## Pass/Fail Criteria
-
-| Condition | Result |
-|-----------|--------|
-| Score >= 95 AND ambiguity == 0 | GATE: APPROVED |
-| Score < 95 OR ambiguity > 0 | GATE: REJECTED |
-
-## Auditor Mindset
-
-- Assume the specification is INCOMPLETE until proven otherwise
-- Look for what's MISSING, not just what's wrong
-- Ask "what could go wrong?" for every part
-- Prefer rejection over approval when uncertain
-- Better to ask one more question than to approve prematurely
-
-## Standalone Usage
-
-Can be invoked directly: \`/dino.audit\`
-
-Use when:
-- Validating a specification before implementation
-- Reviewing a PR description
-- Checking requirements completeness
-- Gate-checking before major changes
+        content: `# 🔒 Audit Phase
+
+**Strict gatekeeper that validates specifications before implementation.**
+
+This skill is the AUDITOR agent in the three-agent Ralph Gate system. It can also be used standalone to validate any specification.
+
+## Role
+
+You are an EXTREMELY STRICT auditor. Your job is to find problems, not approve things. Implementation should be BLOCKED by default unless everything is perfect.
+
+## Scoring System
+
+### 1. Specification Completeness (25 points)
+
+| Criterion | Points | Check |
+|-----------|--------|-------|
+| Clear problem statement | 5 | What problem are we solving? |
+| Explicit success criteria | 5 | How do we know when done? |
+| Defined scope boundaries | 5 | What is NOT included? |
+| Edge cases identified | 5 | What could go wrong? |
+| Error handling specified | 5 | How to handle failures? |
+
+### 2. Ambiguity Score (MUST BE ZERO)
+
+Check for these ambiguity types:
+
+| Type | Example | Fix Required |
+|------|---------|--------------|
+| Vague verbs | "improve", "enhance", "better" | Specify measurable outcome |
+| Undefined terms | "fast", "clean", "modern" | Define with numbers/criteria |
+| Implicit assumptions | "the usual way" | Make explicit |
+| Conflicting requirements | "fast AND thorough" | Prioritize or resolve |
+| Missing details | "handle errors" | Specify which errors, how |
+
+**Any ambiguity = AUTOMATIC REJECTION**
+
+### 3. PRD Quality (25 points) - For Ralph-eligible tasks
+
+| Criterion | Points | Check |
+|-----------|--------|-------|
+| Stories in correct format | 5 | Markdown headers, fields |
+| Each story has unique ID | 5 | story-1, story-2, etc. |
+| Each story has file list | 5 | Explicit file paths |
+| Each story has acceptance criteria | 5 | Checkbox list |
+| Each story has test command | 5 | Runnable command |
+
+### 4. Risk Mitigation (25 points)
+
+| Criterion | Points | Check |
+|-----------|--------|-------|
+| Security risks addressed | 5 | Input validation, auth, etc. |
+| Performance risks addressed | 5 | Scale, complexity, etc. |
+| Breaking changes identified | 5 | API changes, migrations |
+| Rollback plan exists | 5 | How to undo if needed |
+| Dependencies validated | 5 | External deps checked |
+
+### 5. Research Completeness (25 points) - When research provided
+
+| Criterion | Points | Check |
+|-----------|--------|-------|
+| All patterns documented | 5 | Similar code found |
+| Architecture understood | 5 | Fits existing structure |
+| Integration points mapped | 5 | Connections identified |
+| Test strategy defined | 5 | What tests to add/modify |
+| File impact complete | 5 | All affected files listed |
+
+## Pass/Fail Criteria
+
+| Condition | Result |
+|-----------|--------|
+| Score >= 95 AND ambiguity == 0 | GATE: APPROVED |
+| Score < 95 OR ambiguity > 0 | GATE: REJECTED |
+
+## Auditor Mindset
+
+- Assume the specification is INCOMPLETE until proven otherwise
+- Look for what's MISSING, not just what's wrong
+- Ask "what could go wrong?" for every part
+- Prefer rejection over approval when uncertain
+- Better to ask one more question than to approve prematurely
+
+## Standalone Usage
+
+Can be invoked directly: \`/dino.audit\`
+
+Use when:
+- Validating a specification before implementation
+- Reviewing a PR description
+- Checking requirements completeness
+- Gate-checking before major changes
 `,
     },
     {
@@ -963,62 +975,71 @@ Use when:
             model: 'opus',
             context: 'fork',
             effort: 'high',
-            allowedTools: ['Read', 'Grep', 'Glob', 'Task', 'Write', 'AskUserQuestion', 'mcp__dino__dino_status', 'mcp__dino__dino_focus_set'],
+            allowedTools: [
+                'Read',
+                'Grep',
+                'Glob',
+                'Task',
+                'Write',
+                'AskUserQuestion',
+                'mcp__dino__dino_status',
+                'mcp__dino__dino_focus_set',
+            ],
         },
-        content: `# 🦖 Ralph Gate - EXECUTE NOW
-
-**YOU MUST EXECUTE THE THREE-AGENT WORKFLOW BELOW. DO NOT JUST DESCRIBE IT.**
-
-## STEP 1: CREATE OUTPUT DIRECTORY
-
-Write to \`.dino/ralph-gate/status.md\` with: "# Ralph Gate Status\\n\\nStatus: PHASE 1 - RESEARCH"
-
-## STEP 2: SPAWN SCOUT AGENT (MANDATORY)
-
-**USE THE TASK TOOL NOW** with these parameters:
-- subagent_type: "Explore"
-- description: "Ralph Gate Scout - Deep Research"
-- prompt: Include the user request, then require: finding all related code with Grep/Glob, mapping dependencies, assessing risks, creating file impact list. Output must be a RESEARCH REPORT with patterns, risk matrix, file list, and draft PRD with stories.
-
-**WAIT FOR SCOUT TO COMPLETE.**
-
-## STEP 3: SAVE SCOUT OUTPUT
-
-Write scout output to \`.dino/ralph-gate/research-report.md\`
-
-## STEP 4: SPAWN AUDITOR AGENT (MANDATORY)
-
-**USE THE TASK TOOL NOW** with:
-- subagent_type: "Plan"
-- model: "opus"
-- description: "Ralph Gate Auditor - Strict Validation"
-- prompt: Include user request + research report. Auditor scores: Specification (25pts), Ambiguity (must be 0), PRD Quality (25pts), Risk (25pts), Research (25pts). Output "GATE: APPROVED" if score >= 95 AND ambiguity == 0, else "GATE: REJECTED" with blocking issues.
-
-**WAIT FOR AUDITOR TO COMPLETE.**
-
-## STEP 5: CHECK GATE RESULT
-
-- IF "GATE: APPROVED" → Continue to Step 6
-- IF "GATE: REJECTED" → Use AskUserQuestion to clarify issues, then re-run Step 4 (max 3 cycles)
-
-## STEP 6: SAVE AUDIT REPORT
-
-Write auditor output to \`.dino/ralph-gate/audit-report.md\`
-
-## STEP 7: SPAWN RALPH EXECUTOR (ONLY IF APPROVED)
-
-**USE THE TASK TOOL NOW** with:
-- subagent_type: "general-purpose"
-- description: "Ralph Loop Executor"
-- prompt: Include gate status and validated PRD. For each story: git checkpoint, implement changes, run test command, commit if pass or retry (max 2). Update \`.dino/ralph-progress.md\` after each story.
-
-## STEP 8: REPORT RESULTS
-
-Save final status to \`.dino/ralph-gate/final-status.md\` and report: stories completed, stories failed, iterations used, files modified.
-
----
-
-**START NOW: Execute Step 1, then Step 2, etc. Do not summarize.**
+        content: `# 🦖 Ralph Gate - EXECUTE NOW
+
+**YOU MUST EXECUTE THE THREE-AGENT WORKFLOW BELOW. DO NOT JUST DESCRIBE IT.**
+
+## STEP 1: CREATE OUTPUT DIRECTORY
+
+Write to \`.dino/ralph-gate/status.md\` with: "# Ralph Gate Status\\n\\nStatus: PHASE 1 - RESEARCH"
+
+## STEP 2: SPAWN SCOUT AGENT (MANDATORY)
+
+**USE THE TASK TOOL NOW** with these parameters:
+- subagent_type: "Explore"
+- description: "Ralph Gate Scout - Deep Research"
+- prompt: Include the user request, then require: finding all related code with Grep/Glob, mapping dependencies, assessing risks, creating file impact list. Output must be a RESEARCH REPORT with patterns, risk matrix, file list, and draft PRD with stories.
+
+**WAIT FOR SCOUT TO COMPLETE.**
+
+## STEP 3: SAVE SCOUT OUTPUT
+
+Write scout output to \`.dino/ralph-gate/research-report.md\`
+
+## STEP 4: SPAWN AUDITOR AGENT (MANDATORY)
+
+**USE THE TASK TOOL NOW** with:
+- subagent_type: "Plan"
+- model: "opus"
+- description: "Ralph Gate Auditor - Strict Validation"
+- prompt: Include user request + research report. Auditor scores: Specification (25pts), Ambiguity (must be 0), PRD Quality (25pts), Risk (25pts), Research (25pts). Output "GATE: APPROVED" if score >= 95 AND ambiguity == 0, else "GATE: REJECTED" with blocking issues.
+
+**WAIT FOR AUDITOR TO COMPLETE.**
+
+## STEP 5: CHECK GATE RESULT
+
+- IF "GATE: APPROVED" → Continue to Step 6
+- IF "GATE: REJECTED" → Use AskUserQuestion to clarify issues, then re-run Step 4 (max 3 cycles)
+
+## STEP 6: SAVE AUDIT REPORT
+
+Write auditor output to \`.dino/ralph-gate/audit-report.md\`
+
+## STEP 7: SPAWN RALPH EXECUTOR (ONLY IF APPROVED)
+
+**USE THE TASK TOOL NOW** with:
+- subagent_type: "general-purpose"
+- description: "Ralph Loop Executor"
+- prompt: Include gate status and validated PRD. For each story: git checkpoint, implement changes, run test command, commit if pass or retry (max 2). Update \`.dino/ralph-progress.md\` after each story.
+
+## STEP 8: REPORT RESULTS
+
+Save final status to \`.dino/ralph-gate/final-status.md\` and report: stories completed, stories failed, iterations used, files modified.
+
+---
+
+**START NOW: Execute Step 1, then Step 2, etc. Do not summarize.**
 `,
     },
 ];
@@ -1036,138 +1057,147 @@ const RESEARCH_SKILL = {
         model: 'sonnet',
         context: 'fork',
         effort: 'medium',
-        allowedTools: ['Read', 'Grep', 'Glob', 'Task', 'WebSearch', 'WebFetch', 'Write', 'AskUserQuestion'],
+        allowedTools: [
+            'Read',
+            'Grep',
+            'Glob',
+            'Task',
+            'WebSearch',
+            'WebFetch',
+            'Write',
+            'AskUserQuestion',
+        ],
         disallowedTools: ['Edit', 'Bash'],
     },
-    content: `# Research Skill
-
-Research technical topics and save findings for future reuse. Avoids redundant web fetches by checking saved research first.
-
-## Usage
-
-\`\`\`
-/research <topic>           # Research and save
-/research list              # List saved research
-/research recall <topic>    # Recall saved research without re-fetching
-\`\`\`
-
-**Examples:**
-- \`/research context engineering\`
-- \`/research react hooks best practices\`
-- \`/research recall typescript generics\`
-
-## Workflow
-
-### 1. Check Saved Research First (CRITICAL)
-
-Before ANY web search, check for existing research:
-
-\`\`\`
-.dino/research/<topic-slug>.md
-.claude/docs/<topic>.md
-\`\`\`
-
-If found and recent (< 30 days), present it directly without web fetching.
-
-### 2. Web Research (only if needed)
-
-Only fetch from web when:
-- No saved research exists
-- Saved research is stale (> 30 days)
-- User explicitly requests fresh research with \`--fresh\`
-
-When researching:
-- Search authoritative sources
-- Cross-reference multiple sources
-- Extract actionable information
-
-### 3. Save Research (ALWAYS)
-
-Save ALL research to \`.dino/research/<topic-slug>.md\` in ready-to-use format:
-
-\`\`\`markdown
----
-topic: <Full Topic Name>
-slug: <topic-slug>
-created: <ISO date>
-updated: <ISO date>
-sources:
-  - url: <source url>
-    title: <source title>
-    accessed: <ISO date>
-tags: [<tag1>, <tag2>]
----
-
-# <Topic Name>
-
-## TL;DR
-<2-3 sentence summary for quick reference>
-
-## Key Facts
-- Fact 1
-- Fact 2
-- Fact 3
-
-## Details
-<Detailed explanation with examples>
-
-## Code Examples (if applicable)
-\\\`\\\`\\\`code
-<ready-to-use code snippets>
-\\\`\\\`\\\`
-
-## Common Pitfalls
-- Pitfall 1
-- Pitfall 2
-
-## See Also
-- Related topic 1
-- Related topic 2
-\`\`\`
-
-### 4. Present to User
-
-After saving, present a summary and note where it's saved.
-
-## File Naming
-
-Convert topic to slug: lowercase, replace spaces with hyphens, remove special chars.
-
-Examples:
-- "Context Engineering" → \`context-engineering.md\`
-- "React Hooks Best Practices" → \`react-hooks-best-practices.md\`
-- "TypeScript Generics" → \`typescript-generics.md\`
-
-## Commands
-
-### \`/research <topic>\`
-1. Check \`.dino/research/\` for existing research
-2. If found and fresh: present it
-3. If not found or stale: research, save, present
-
-### \`/research list\`
-List all saved research files with topics and dates.
-
-### \`/research recall <topic>\`
-Load and present saved research without any web fetching.
-Returns error if no saved research exists.
-
-### \`/research <topic> --fresh\`
-Force fresh research even if saved version exists.
-Updates the saved file with new findings.
-
-## Benefits
-
-- **No redundant fetches**: Same topic researched once, reused many times
-- **Git tracked**: Research persists across sessions and is shared with team
-- **Ready-to-use format**: Code examples, key facts, TL;DR for quick reference
-- **Source tracking**: Know where information came from and when
-
-## Notes
-
-- Research is saved to \`.dino/research/\` which is now git-tracked
-- High-value permanent docs can also go to \`.claude/docs/\`
-- Fork context ensures clean separation from main conversation
+    content: `# Research Skill
+
+Research technical topics and save findings for future reuse. Avoids redundant web fetches by checking saved research first.
+
+## Usage
+
+\`\`\`
+/research <topic>           # Research and save
+/research list              # List saved research
+/research recall <topic>    # Recall saved research without re-fetching
+\`\`\`
+
+**Examples:**
+- \`/research context engineering\`
+- \`/research react hooks best practices\`
+- \`/research recall typescript generics\`
+
+## Workflow
+
+### 1. Check Saved Research First (CRITICAL)
+
+Before ANY web search, check for existing research:
+
+\`\`\`
+.dino/research/<topic-slug>.md
+.claude/docs/<topic>.md
+\`\`\`
+
+If found and recent (< 30 days), present it directly without web fetching.
+
+### 2. Web Research (only if needed)
+
+Only fetch from web when:
+- No saved research exists
+- Saved research is stale (> 30 days)
+- User explicitly requests fresh research with \`--fresh\`
+
+When researching:
+- Search authoritative sources
+- Cross-reference multiple sources
+- Extract actionable information
+
+### 3. Save Research (ALWAYS)
+
+Save ALL research to \`.dino/research/<topic-slug>.md\` in ready-to-use format:
+
+\`\`\`markdown
+---
+topic: <Full Topic Name>
+slug: <topic-slug>
+created: <ISO date>
+updated: <ISO date>
+sources:
+  - url: <source url>
+    title: <source title>
+    accessed: <ISO date>
+tags: [<tag1>, <tag2>]
+---
+
+# <Topic Name>
+
+## TL;DR
+<2-3 sentence summary for quick reference>
+
+## Key Facts
+- Fact 1
+- Fact 2
+- Fact 3
+
+## Details
+<Detailed explanation with examples>
+
+## Code Examples (if applicable)
+\\\`\\\`\\\`code
+<ready-to-use code snippets>
+\\\`\\\`\\\`
+
+## Common Pitfalls
+- Pitfall 1
+- Pitfall 2
+
+## See Also
+- Related topic 1
+- Related topic 2
+\`\`\`
+
+### 4. Present to User
+
+After saving, present a summary and note where it's saved.
+
+## File Naming
+
+Convert topic to slug: lowercase, replace spaces with hyphens, remove special chars.
+
+Examples:
+- "Context Engineering" → \`context-engineering.md\`
+- "React Hooks Best Practices" → \`react-hooks-best-practices.md\`
+- "TypeScript Generics" → \`typescript-generics.md\`
+
+## Commands
+
+### \`/research <topic>\`
+1. Check \`.dino/research/\` for existing research
+2. If found and fresh: present it
+3. If not found or stale: research, save, present
+
+### \`/research list\`
+List all saved research files with topics and dates.
+
+### \`/research recall <topic>\`
+Load and present saved research without any web fetching.
+Returns error if no saved research exists.
+
+### \`/research <topic> --fresh\`
+Force fresh research even if saved version exists.
+Updates the saved file with new findings.
+
+## Benefits
+
+- **No redundant fetches**: Same topic researched once, reused many times
+- **Git tracked**: Research persists across sessions and is shared with team
+- **Ready-to-use format**: Code examples, key facts, TL;DR for quick reference
+- **Source tracking**: Know where information came from and when
+
+## Notes
+
+- Research is saved to \`.dino/research/\` which is now git-tracked
+- High-value permanent docs can also go to \`.claude/docs/\`
+- Fork context ensures clean separation from main conversation
 `,
 };
 /**
@@ -1310,38 +1340,38 @@ function generateMainSkill() {
         model: 'sonnet',
         context: 'inherit',
     });
-    return `${frontmatter}
-
-# 🦖 Dino-Spec Skills (v${VERSION})
-
-Workflow phase skills for structured development.
-
-## Phase Skills
-
-| Skill | Phase | Description |
-|-------|-------|-------------|
-| \`/dino.spec\` | Specification | Analyze prompts, clarify requirements |
-| \`/dino.discover\` | Discovery | Capture requirements |
-| \`/dino.scout\` | Research | Explore options |
-| \`/dino.sniff\` | Clarification | Resolve ambiguities |
-| \`/dino.nest\` | Planning | Design approach |
-| \`/dino.hatch\` | Breakdown | Create tasks |
-| \`/dino.hunt\` | Implementation | Execute tasks |
-| \`/dino.aging\` | Verification | Run tests |
-| \`/dino.fossil\` | Completion | Archive work |
-
-## Utility Skills
-
-| Skill | Description |
-|-------|-------------|
-| \`/dino.ralph\` | Fresh-context iterative execution |
-| \`/dino.status\` | Check session state (--next, --focus, --tips) |
-| \`/dino.release\` | Release workflow with doc updates |
-
-## Usage
-
-Invoke any skill by typing its command (e.g., \`/dino.discover\`).
-Skills automatically use session context from \`.dino/session.md\`.
+    return `${frontmatter}
+
+# 🦖 Dino-Spec Skills (v${VERSION})
+
+Workflow phase skills for structured development.
+
+## Phase Skills
+
+| Skill | Phase | Description |
+|-------|-------|-------------|
+| \`/dino.spec\` | Specification | Analyze prompts, clarify requirements |
+| \`/dino.discover\` | Discovery | Capture requirements |
+| \`/dino.scout\` | Research | Explore options |
+| \`/dino.sniff\` | Clarification | Resolve ambiguities |
+| \`/dino.nest\` | Planning | Design approach |
+| \`/dino.hatch\` | Breakdown | Create tasks |
+| \`/dino.hunt\` | Implementation | Execute tasks |
+| \`/dino.aging\` | Verification | Run tests |
+| \`/dino.fossil\` | Completion | Archive work |
+
+## Utility Skills
+
+| Skill | Description |
+|-------|-------------|
+| \`/dino.ralph\` | Fresh-context iterative execution |
+| \`/dino.status\` | Check session state (--next, --focus, --tips) |
+| \`/dino.release\` | Release workflow with doc updates |
+
+## Usage
+
+Invoke any skill by typing its command (e.g., \`/dino.discover\`).
+Skills automatically use session context from \`.dino/session.md\`.
 `;
 }
 /**