Initial commit: .claude folder with agents and skills

.claude/skills/create-plan/SKILL.md

@@ -0,0 +1,70 @@
+---
+name: create-plan
+description: convert structure outline into a detailed implementation plan
+---
+
+# Create Plan
+
+You are in the final Plan Writing phase. Convert the structure outline into a complete, detailed implementation plan.
+
+## Steps
+
+1. **Read all input files FULLY**:
+   - Use Read tool WITHOUT limit/offset to read all provided file paths
+   - `ls .humanlayer/tasks/TASKNAME` to find all related documents in the task directory
+   - Read everything in the task directory to build full context
+
+2. **Read relevant code files**:
+   - Read any source files mentioned in the research, design, or structure documents
+   - Build context for writing specific code examples
+
+3. **Read the plan template**:
+
+`Read({SKILLBASE}/references/plan_template.md)`
+
+4. **Write the implementation plan**:
+   - Write to `.humanlayer/tasks/ENG-XXXX-description/YYYY-MM-DD-plan.md`
+   - Convert each phase from the structure outline into detailed implementation steps
+   - Include specific code examples for each change
+   - Add both automated and manual success criteria
+
+## Plan Writing Guidelines
+
+- Each phase should be independently testable
+- Include specific code examples, not just descriptions
+- Automated verification should be runnable commands
+- Manual verification should be specific, actionable steps
+- Pause for human confirmation between phases
+
+## Output
+
+1. **Read the final output template**:
+
+`Read({SKILLBASE}/references/plan_final_answer.md)`
+
+2. Respond with a summary following the template, including GitHub permalinks
+
+<guidance>
+## Cloud Permalinks
+
+When you write or edit documents in .humanlayer/tasks/, a cloud permalink is automatically provided in the hook response.
+- The permalink appears as `additionalContext` after Write/Edit/MultiEdit operations
+- Use this permalink in your final output for easy navigation
+- Example format: `http(s)://{DOMAIN}/artifacts/{artifactId}`
+
+## Markdown Formatting
+
+When writing markdown files that contain code blocks showing other markdown (like README examples or SKILL.md templates), use 4 backticks (````) for the outer fence so inner 3-backtick code blocks don't prematurely close it:
+
+````markdown
+# Example README
+## Installation
+```bash
+npm install example
+```
+````
+
+## Validation Design
+
+Not every phase requires manual validation, don't put steps for manual validation just to have them. 
+</guidance>

.claude/skills/create-plan/references/plan_final_answer.md

@@ -0,0 +1,28 @@
+### Status
+
+- Document: [.humanlayer/tasks/ENG-XXXX-description/YYYY-MM-DD-plan.md](cloud permalink from hook)
+- Ticket: [ENG-XXXX](ticket URL if known, otherwise omit link)
+- Phases: [count]
+
+### Phase Summary
+
+1. [Phase 1 title]: [brief description]
+2. [Phase 2 title]: [brief description]
+...
+
+### Key Implementation Details
+
+- [notable code change or pattern]
+- ...
+
+### Next Steps
+
+To proceed to implementation, use a prompt like
+
+```text
+use the setup-worktree skill for [.humanlayer/tasks/ENG-XXXX-description/YYYY-MM-DD-plan.md]
+```
+
+---
+
+You can view the full document here: [YYYY-MM-DD-plan.md](cloud permalink from hook)

.claude/skills/create-plan/references/plan_template.md

@@ -0,0 +1,108 @@
+---
+task: eng-xxxx-description
+type: plan
+repo: [current repository]
+branch: [current branch name]
+sha: [result of git rev-parse HEAD]
+---
+
+# [Feature/Task Name] Implementation Plan
+
+## Overview
+
+[Brief description of what we're implementing and why]
+
+## Current State Analysis
+
+[What exists now, what's missing, key constraints discovered]
+
+### Key Discoveries:
+- [Important finding with file:line reference]
+- [Pattern to follow]
+- [Constraint to work within]
+
+## Desired End State
+
+[A specification of the desired end state after this plan is complete, and how to verify it]
+
+## What We're NOT Doing
+
+[Explicitly list out-of-scope items to prevent scope creep]
+
+## Implementation Approach
+
+[High-level strategy and reasoning]
+
+---
+
+## Phase 1: [Descriptive Name]
+
+### Overview
+[What this phase accomplishes]
+
+### Changes Required:
+
+#### 1.1 [Component/File Group]
+
+**File**: `path/to/file.ext`
+**Changes**: [Summary of changes] - [around line X | add after Y | etc etc]
+
+```diff
+// Specific code to add/modify
++ export function [name]() {
+     // existing logic...
++    [code changes to make]
++ 
++ }
+
+export interface [name]{ 
+   // existing fiels (a, b, c, d, e)
++  [new fields to add]
++  [new fields to add]
+}
+```
+
+
+#### 1.2 [Another Component/File Group]
+
+**File**: `path/to/file.ext`
+**Changes**: [Summary of changes]
+
+...
+
+### Success Criteria:
+
+#### Automated Verification:
+- [ ] [Migration applies cleanly: `bun run ...`]
+- [ ] [Type checking passes: `bun run biome`]
+- [ ] [Tests pass: `bun run test`]
+- [ ] [other automated verification as appropriate: curl, sql queries, etc]
+
+<optional if="manual validation relevant">
+#### Manual Verification:
+- [ ] [manual step 1]
+- [ ] [manual step 2]
+- [ ] [manual step 3]
+
+**Implementation Note**: After completing this phase and all automated verification passes, pause here for manual confirmation from the human that the manual testing was successful before proceeding to the next phase.
+</optional>
+
+---
+
+## Phase 2: [Descriptive Name]
+
+### Overview
+[What this phase accomplishes]
+
+### Changes Required:
+
+#### 2.1 [Component/File Group]
+
+**File**: `path/to/file.ext`
+**Changes**: [Summary of changes]
+
+### Success Criteria:
+
+[Similar structure with both automated and manual success criteria...]
+
+---