claude-code-orchestrator-kit 1.4.1 → 1.4.15

package/.claude/skills/load-project-context/SKILL.md

@@ -1,89 +0,0 @@
----
-name: load-project-context
-description: Load project structure and navigation for complex tasks. Use when exploring unfamiliar parts of codebase or starting complex multi-file tasks.
-trigger: When exploring unfamiliar code areas, planning complex features, or needing project structure overview
----
-
-# Load Project Context
-
-Loads the project index file to understand project structure without reading the entire codebase.
-
-## When to Use
-
-- Before exploring unfamiliar parts of the codebase
-- When planning complex multi-file changes
-- When you need to understand where specific functionality lives
-- At the start of complex orchestrator workflows
-
-## When NOT to Use
-
-- For simple, single-file tasks
-- When you already know the file locations
-- For trivial bug fixes
-
-## Algorithm
-
-1. Check if `.claude/project-index.md` exists
-2. If exists:
-   - Read the file
-   - Return the content for agent consumption
-3. If not exists:
-   - Inform that project index is not configured
-   - Suggest creating one from template
-
-## Implementation
-
-```markdown
-### Step 1: Check for project index
-
-Read the file `.claude/project-index.md`
-
-### Step 2: If file exists
-
-Return the full content. The agent should use this to:
-- Understand project structure
-- Identify key directories for the task
-- Find relevant patterns and conventions
-
-### Step 3: If file does not exist
-
-Return this message:
-"Project index not found. To create one:
-1. Copy `.claude/templates/project-index.template.md` to `.claude/project-index.md`
-2. Customize for your project structure
-3. Keep under 150 lines for token efficiency"
-```
-
-## Output Format
-
-The skill returns the project index content directly, which includes:
-- Architecture overview with links
-- Core domains with key directories
-- Patterns and conventions
-- Recent changes
-
-## Token Cost
-
-- File read: ~100-200 tokens (if index is well-maintained at <150 lines)
-- No additional processing overhead
-
-## Example Usage
-
-```
-Agent: I need to understand where authentication is handled in this project.
-
-[Invokes load-project-context skill]
-
-Skill returns project-index.md content showing:
-- Auth pattern: "Supabase Auth + RLS policies"
-- Key directory: "packages/api/src/middleware/" for auth middleware
-
-Agent now knows exactly where to look without scanning entire codebase.
-```
-
-## Maintenance
-
-The project index should be updated:
-- When major architectural changes occur
-- Weekly for "Recent Changes" section
-- When new domains/packages are added

package/.claude/skills/resume-session/SKILL.md

@@ -1,164 +0,0 @@
----
-name: resume-session
-description: Resume a previously saved session by loading context and recent log entries. Use at start of orchestrator workflows to check for existing sessions.
-trigger: At the start of health workflows, or when user asks to continue previous work
----
-
-# Resume Session
-
-Checks for and loads a previously saved session context, enabling seamless workflow continuation.
-
-## When to Use
-
-- At the start of health orchestrator workflows (automatic)
-- When user explicitly asks to continue previous work
-- After session restart or context switch
-
-## When NOT to Use
-
-- For new workflows with no prior context
-- When user explicitly wants to start fresh
-
-## Algorithm
-
-### Step 1: Check for Existing Session
-
-Check if `.tmp/current/session/context.md` exists.
-
-### Step 2: Validate Freshness
-
-If file exists, check the "Updated" timestamp:
-- If < 24 hours old: Session is valid
-- If > 24 hours old: Session is stale, ask user
-
-### Step 3: Load Context
-
-Read `.tmp/current/session/context.md` and extract:
-- Current workflow and phase
-- Last action and next steps
-- Git state
-- Quality gate status
-
-### Step 4: Load Recent Log Entries
-
-Read last 10 entries from `.tmp/current/session/log.md`:
-- Recent decisions
-- Issues encountered
-- Learnings
-
-### Step 5: Present Resume Option
-
-If valid session found, present to user:
-```
-Found previous session:
-- Workflow: health-bugs
-- Phase: 3/7 (Staged Fixing)
-- Last action: Fixed auth validation
-- Age: 2 hours ago
-
-Options:
-1. Resume from where you left off
-2. Start fresh (archive current session)
-```
-
-### Step 6: On Resume
-
-Return combined context for orchestrator to continue:
-```markdown
-## Resuming Session
-
-### Current State
-[Content from context.md]
-
-### Recent Decisions
-[Last 5 entries from log.md]
-
-### Next Actions
-[From context.md Next Steps section]
-```
-
-### Step 7: On Start Fresh
-
-If user chooses fresh start:
-1. Move current session files to `.tmp/archive/session-[timestamp]/`
-2. Return empty context
-3. Orchestrator starts Phase 1
-
-## Implementation
-
-```markdown
-### Check session exists
-
-Read `.tmp/current/session/context.md`
-
-If not found:
-  Return "No previous session found. Starting fresh."
-
-### Validate timestamp
-
-Extract "Updated: YYYY-MM-DDTHH:MM:SS" from file
-Calculate age in hours
-
-If age > 24:
-  Ask user: "Session is [X] hours old. Resume or start fresh?"
-
-### Load and return
-
-Read context.md fully
-Read last 500 lines of log.md (covers ~10 entries)
-Return combined content
-```
-
-## Output Format
-
-### When session found:
-```
-Previous session found:
-- Workflow: health-bugs
-- Phase: 3/7 (Staged Fixing)
-- Age: 2h 15m
-- Last: Fixed auth validation in src/auth.ts
-
-Resume? [Y/n]
-```
-
-### When no session:
-```
-No previous session found. Starting fresh workflow.
-```
-
-### When stale:
-```
-Found stale session (26 hours old):
-- Workflow: health-security
-- Phase: 2/5
-
-[R]esume anyway, [A]rchive and start fresh, or [C]ancel?
-```
-
-## Token Cost
-
-- Context read: ~100-150 tokens
-- Log read (last 10 entries): ~200-300 tokens
-- Total: ~300-450 tokens (only when resuming)
-
-## Related Skills
-
-- `save-session-context` — Save current state for later
-- `load-project-context` — Load project structure
-
-## Integration with Orchestrators
-
-Health orchestrators should call this skill in Phase 0:
-
-```markdown
-## Phase 0: Session Check
-
-1. Invoke `resume-session` skill
-2. If valid session:
-   - Ask user: Resume or fresh?
-   - If resume: Jump to saved phase
-3. If no session:
-   - Proceed to Phase 1
-4. Create new session context
-```

package/.claude/skills/save-session-context/SKILL.md

@@ -1,123 +0,0 @@
----
-name: save-session-context
-description: Save current session state for later resumption. Use after completing workflow phases or before ending a session.
-trigger: After completing a workflow phase, before session end, or when switching to different task
----
-
-# Save Session Context
-
-Saves the current workflow state to enable seamless session resumption.
-
-## When to Use
-
-- After completing each phase in health orchestrator workflows
-- Before ending a long-running session
-- When switching context to a different task
-- After significant progress that should be preserved
-
-## When NOT to Use
-
-- For simple, quick tasks that don't need resumption
-- When workflow is fully complete (clean up instead)
-
-## Algorithm
-
-### Step 1: Gather Current State
-
-Collect the following information:
-- Current workflow name and phase
-- Priority level and completion counts
-- Last completed action
-- List of modified files (from git status)
-
-### Step 2: Get Git State
-
-Run `git status` and `git log -1` to capture:
-- Current branch
-- Uncommitted files count
-- Last commit hash and message
-
-### Step 3: Determine Next Steps
-
-Based on current phase and workflow, identify:
-- Immediate next action
-- Following 2-3 actions
-
-### Step 4: Write Context File
-
-Write to `.tmp/current/session/context.md`:
-
-```markdown
-# Session Context
-
-> Auto-generated by save-session-context skill. Updated: [ISO timestamp]
-
-## Current State
-
-- **Workflow:** [workflow-name]
-- **Phase:** [current]/[total] ([phase-name])
-- **Priority:** [priority-level] ([completed] of [total] fixed)
-- **Last Action:** [description]
-
-## Active Files
-
-[List from git status]
-
-## Next Steps
-
-1. [Next action]
-2. [Following action]
-3. [Third action]
-
-## Git State
-
-- **Branch:** [branch-name]
-- **Uncommitted:** [count] files
-- **Last Commit:** [hash] "[message]"
-
-## Quality Gate Status
-
-- **Type-check:** [status]
-- **Build:** [status]
-- **Tests:** [status]
-
-## Resume Instructions
-
-To continue this session:
-1. Read this file to understand current state
-2. Read `session-log.md` for recent decisions
-3. Continue from "Next Steps" section
-```
-
-### Step 5: Confirm Save
-
-Output confirmation message with file path.
-
-## Implementation Notes
-
-```bash
-# Get git state
-git status --porcelain | wc -l  # Uncommitted count
-git log -1 --format="%h %s"     # Last commit
-git branch --show-current       # Current branch
-```
-
-## Output
-
-Confirmation message:
-```
-Session context saved to .tmp/current/session/context.md
-- Workflow: health-bugs
-- Phase: 3/7 (Staged Fixing)
-- Uncommitted: 2 files
-```
-
-## Token Cost
-
-- Execution: ~50 tokens for git commands
-- Output: 0 (write-only operation)
-
-## Related Skills
-
-- `resume-session` — Read saved context to continue
-- `run-quality-gate` — Update quality gate status in context

package/.claude/templates/project-index.template.md

@@ -1,67 +0,0 @@
-# Project Index
-
-> Quick navigation for AI agents. Updated: YYYY-MM-DD
->
-> **Purpose:** This file helps agents understand project structure without reading entire codebase.
-> **Usage:** Read by `load-project-context` skill when exploring unfamiliar areas.
-
-## Architecture
-
-- **[ARCHITECTURE.md](docs/ARCHITECTURE.md)** — System design, diagrams, data flow
-- **[CLAUDE.md](CLAUDE.md)** — Behavioral rules, orchestration patterns
-
-## Core Domains
-
-### [Domain 1 Name]
-- **[path/to/domain/](path/to/domain/)** — Brief description of what this domain does
-  - Key: `src/` — Main source code
-  - Key: `types/` — TypeScript types and interfaces
-  - Pattern: [Describe the main pattern used, e.g., "Repository pattern", "MVC"]
-
-### [Domain 2 Name]
-- **[path/to/domain/](path/to/domain/)** — Brief description
-  - Key: `components/` — UI components
-  - Key: `hooks/` — Custom React hooks
-
-## Shared Code
-
-- **[packages/shared/](packages/shared/)** — Shared utilities, types, constants
-  - Key: `utils/` — Helper functions
-  - Key: `types/` — Shared TypeScript types
-
-## Configuration
-
-- **[.env.example](.env.example)** — Environment variables template
-- **[tsconfig.json](tsconfig.json)** — TypeScript configuration
-- **[package.json](package.json)** — Dependencies and scripts
-
-## Patterns & Conventions
-
-- **Auth:** [How authentication is implemented]
-- **State:** [State management approach]
-- **Styling:** [CSS/styling approach]
-- **Testing:** [Testing framework and patterns]
-- **Error Handling:** [How errors are handled]
-
-## Key Entry Points
-
-| Purpose | File | Description |
-|---------|------|-------------|
-| App entry | `src/index.ts` | Main application entry point |
-| API routes | `src/routes/` | All API endpoints |
-| Database | `src/db/` | Database connection and queries |
-
-## Recent Changes (last 7 days)
-
-- YYYY-MM-DD: [Brief description of change]
-- YYYY-MM-DD: [Brief description of change]
-
----
-
-## Usage Notes
-
-1. Keep this file under 150 lines
-2. Update "Recent Changes" weekly
-3. Only include KEY directories and files
-4. Annotations should be 1 line max
-5. Link to detailed docs, don't duplicate content

package/.claude/templates/session/context.template.md

@@ -1,40 +0,0 @@
-# Session Context
-
-> Auto-generated by save-session-context skill. Updated: YYYY-MM-DDTHH:MM:SS
-
-## Current State
-
-- **Workflow:** [workflow-name]
-- **Phase:** [current]/[total] ([phase-name])
-- **Priority:** [priority-level] ([completed] of [total] [type])
-- **Last Action:** [brief description of last completed action]
-
-## Active Files
-
-- `path/to/file1.ts` — [status: Modified/Created/Deleted], [not committed/committed]
-- `path/to/file2.ts` — [status], [commit status]
-
-## Next Steps
-
-1. [Next immediate action]
-2. [Following action]
-3. [Action after that]
-
-## Git State
-
-- **Branch:** [current-branch-name]
-- **Uncommitted:** [count] files
-- **Last Commit:** [short-hash] "[commit-message]"
-
-## Quality Gate Status
-
-- **Type-check:** [PASS/FAIL/NOT_RUN]
-- **Build:** [PASS/FAIL/NOT_RUN]
-- **Tests:** [PASS/FAIL/NOT_RUN]
-
-## Resume Instructions
-
-To continue this session:
-1. Read this file to understand current state
-2. Read `session-log.md` for recent decisions and issues
-3. Continue from "Next Steps" section

package/.claude/templates/session/log.template.md

@@ -1,72 +0,0 @@
-# Session Log
-
-> Decisions, issues, and learnings from this session.
-> Newest entries at the top.
-
----
-
-## YYYY-MM-DDTHH:MM:SS
-
-### [Category]: [Brief Title]
-
-**Context:** [What were you trying to do]
-
-**Issue/Decision:** [What happened or what decision was made]
-
-**Resolution:** [How it was resolved or why this decision was made]
-
-**Learning:** [Optional - what to remember for future]
-
----
-
-## Entry Categories
-
-Use these categories for consistency:
-
-- **Decision** — Architectural or implementation choice made
-- **Issue** — Problem encountered and how it was solved
-- **Discovery** — Something learned about the codebase
-- **Blocker** — Something that stopped progress (and resolution)
-- **Rollback** — Change that was reverted and why
-
----
-
-## Example Entries
-
-### 2025-11-27T14:30:00
-
-### Decision: Auth validation approach
-
-**Context:** Multiple auth checks scattered across codebase
-
-**Issue/Decision:** Chose middleware-based approach over per-route validation
-
-**Resolution:** Created `authMiddleware.ts` in `src/middleware/`
-
-**Learning:** Check existing patterns in `middleware/` before adding new auth logic
-
----
-
-### 2025-11-27T15:00:00
-
-### Issue: TypeScript error after fix
-
-**Context:** Fixed auth validation, but broke type inference
-
-**Issue/Decision:** Type 'string | undefined' not assignable to 'string'
-
-**Resolution:** Added nullish coalescing `?? ''` fallback
-
----
-
-### 2025-11-27T15:30:00
-
-### Blocker: Missing dependency
-
-**Context:** Tried to use zod validation
-
-**Issue/Decision:** zod not installed in this package
-
-**Resolution:** Added to package.json, ran pnpm install
-
-**Learning:** Check package.json before using external libraries

package/.github/BRANCH_PROTECTION.md

@@ -1,137 +0,0 @@
-# Branch Protection Rules Configuration
-
-**Task**: T088 - Configure branch protection rules for main branch
-**Status**: Configuration instructions (requires GitHub admin access)
-
-## Required Configuration
-
-Branch protection rules must be configured in GitHub repository settings for the `main` branch.
-
-### Access Path
-1. Go to repository Settings
-2. Navigate to Branches → Branch protection rules
-3. Click "Add rule" or edit existing rule for `main`
-
-### Required Settings
-
-#### 1. Branch Name Pattern
-- Pattern: `main`
-
-#### 2. Protect Matching Branches
-Enable the following protections:
-
-**Require status checks to pass before merging**
-- ✅ Require status checks to pass before merging
-- ✅ Require branches to be up to date before merging
-- Required status checks:
-  - `test / test (20.x)` - Test workflow must pass
-  - `build / build (20.x)` - Build workflow must pass
-
-**Require pull request reviews before merging**
-- ✅ Require pull request reviews before merging
-- Required number of approvals: 1
-- ✅ Dismiss stale pull request approvals when new commits are pushed
-- ✅ Require review from Code Owners (if CODEOWNERS file exists)
-
-**Restrict who can push to matching branches**
-- ✅ Restrict pushes that create matching branches
-- Allowed to push: Repository administrators only
-
-**Additional Protections**
-- ✅ Require linear history (prevent merge commits)
-- ✅ Require deployments to succeed before merging (when staging is configured)
-- ❌ Allow force pushes (disabled)
-- ❌ Allow deletions (disabled)
-
-#### 3. Rules Applied to Administrators
-- ✅ Include administrators (recommended for consistency)
-
-## Validation Checklist
-
-After configuration, verify:
-
-- [ ] Push to `main` without PR is blocked
-- [ ] PR cannot be merged with failing tests
-- [ ] PR cannot be merged with failing build
-- [ ] PR requires at least 1 approval
-- [ ] Force push to `main` is blocked
-- [ ] Branch deletion is blocked
-
-## Testing Branch Protection
-
-### Test 1: Direct Push (Should Fail)
-```bash
-# Try to push directly to main (should be blocked)
-git checkout main
-git commit --allow-empty -m "test: direct push"
-git push origin main
-# Expected: Error - branch protection rules prevent direct push
-```
-
-### Test 2: PR Without Approval (Should Block)
-```bash
-# Create feature branch and PR
-git checkout -b test/branch-protection
-git commit --allow-empty -m "test: pr without approval"
-git push origin test/branch-protection
-# Create PR via GitHub UI
-# Try to merge without approval
-# Expected: Merge button disabled until approved
-```
-
-### Test 3: PR With Failing Tests (Should Block)
-```bash
-# Create branch with failing test
-git checkout -b test/failing-tests
-# Modify code to break tests
-git add . && git commit -m "test: failing tests"
-git push origin test/failing-tests
-# Create PR
-# Expected: Status checks fail, merge blocked
-```
-
-### Test 4: Valid PR Flow (Should Succeed)
-```bash
-# Create valid feature branch
-git checkout -b feature/valid-change
-# Make valid changes
-git add . && git commit -m "feat: valid change"
-git push origin feature/valid-change
-# Create PR, wait for tests to pass, get approval
-# Expected: Can merge after all checks pass and approval received
-```
-
-## Automation via GitHub CLI (Alternative)
-
-If you prefer to configure via CLI instead of UI:
-
-```bash
-# Install GitHub CLI if not already installed
-# https://cli.github.com/
-
-# Enable branch protection
-gh api repos/{owner}/{repo}/branches/main/protection \
-  --method PUT \
-  --field required_status_checks[strict]=true \
-  --field required_status_checks[contexts][]=test \
-  --field required_status_checks[contexts][]=build \
-  --field required_pull_request_reviews[required_approving_review_count]=1 \
-  --field required_pull_request_reviews[dismiss_stale_reviews]=true \
-  --field restrictions=null \
-  --field enforce_admins=true \
-  --field allow_force_pushes=false \
-  --field allow_deletions=false \
-  --field required_linear_history=true
-```
-
-## Notes
-
-- **Stage 0 Scope**: Branch protection configuration is documented but may be applied later when repository is actively developed
-- **Production Readiness**: Enable all protections before deploying to production
-- **Team Size**: Adjust approval count based on team size (1 for small teams, 2+ for larger teams)
-
-## Status
-
-**Implementation Status**: ✅ Documented
-**Configuration Status**: ⏳ Pending (requires repository admin to apply settings)
-**Validation Status**: ⏳ Pending (test after configuration applied)