@hailer/mcp 1.3.21 → 1.3.32

package/.claude/skills/hailer-project-protocol/SKILL.md

@@ -1,398 +0,0 @@
----
-name: hailer-project-protocol
-description: Complete Hailer project management workflow schemas, field definitions, and protocols for SDK projects
-version: 1.1.0
----
-
-# Hailer Project Management Protocol
-
-This skill contains the complete Hailer project management workflow schemas, field definitions, and protocols for working with Hailer SDK projects.
-
----
-
-<critical-rules>
-## Overview
-
-Every Hailer workspace uses project management workflows. Claude installs and maintains these automatically using MCP or SDK.
-
-**CRITICAL: Real-Time Updates**
-- Update Hailer items IN REAL-TIME as work progresses
-- Do NOT batch updates - update immediately when status changes
-- When completing a task, update Hailer BEFORE moving to next task
-
-**Context File Hierarchy**
-1. **SESSION-HANDOFF.md** - Previous session state (read first when resuming)
-2. **DEVELOPMENT.md** - Local backup/snapshot of Hailer state
-3. **Hailer Workflows** - Source of truth for project data
-</critical-rules>
-
----
-
-## Workflow 1: Project Planning
-
-**Workflow name:** `Project Planning`
-
-### Phases (in order)
-1. `Planning`
-2. `In Progress`
-3. `On Hold`
-4. `Completed`
-
-### Fields
-
-| Field Name | Field Type | Configuration |
-|------------|------------|---------------|
-| Title | Text | - |
-| Description | Long text | - |
-| Type | Predefined options (single) | Options: `Project`, `Feature`, `Session Handoff`, `PRD` |
-| Project | Activity link | Links to: `Project Planning` workflow |
-| Child Features | Linked from | Linked from: `Project Planning` → `Project` field |
-| Dev Tasks | Linked from | Linked from: `Dev Tasks` → `Feature` field |
-| Goal | Long text | - |
-| Documentation | Long text | - |
-| Technical Notes | Long text | - |
-| Blockers | Long text | - |
-| User Stories | Long text | PRD: As a [user], I want [X] so that [Y] |
-| Acceptance Criteria | Long text | PRD: Checklist of "done" conditions |
-| Technical Constraints | Long text | PRD: Performance, security, compatibility |
-| Out of Scope | Long text | PRD: What this feature does NOT include |
-
-- **Project**: Features use this to link UP to their parent Project
-- **Child Features**: Automatically shows Features that link to this Project
-- **Dev Tasks**: Automatically shows Tasks/Bugs that link to this Feature
-
----
-
-## Workflow 2: Dev Tasks
-
-**Workflow name:** `Dev Tasks`
-
-### Phases (in order)
-1. `Backlog`
-2. `Todo`
-3. `In Progress`
-4. `Review`
-5. `Done`
-
-### Fields
-
-| Field Name | Field Type | Configuration |
-|------------|------------|---------------|
-| Title | Text | - |
-| Description | Long text | - |
-| Type | Predefined options (single) | Options: `Task`, `Bug`, `Tech Debt` |
-| Priority | Predefined options (single) | Options: `HIGH`, `MEDIUM`, `LOW` |
-| Feature | Activity link | Links to: `Project Planning` workflow |
-| Blocked By | Activity link | Links to: `Dev Tasks` workflow |
-| Blocks | Linked from | Linked from: `Dev Tasks` → `Blocked By` field |
-| Related Items | Activity link | Links to: `Dev Tasks` workflow |
-| Related From | Linked from | Linked from: `Dev Tasks` → `Related Items` field |
-| Files Modified | Text | - |
-| Commits | Text | - |
-
-- **Feature**: Links UP to parent Feature in Project Planning
-- **Blocked By**: Links to other Dev Tasks that block this one
-- **Blocks**: Automatically shows Dev Tasks that this task blocks
-- **Related Items**: Links to related Tasks/Bugs (e.g., Bug → Task that caused it)
-
----
-
-## Protocol: Starting in a Workspace
-
-### Step 1: Check for Existing Workflows
-
-**AUTOMATIC CREATION: If workflows don't exist, CREATE THEM.**
-
-Look for workflows named exactly:
-- `Project Planning`
-- `Dev Tasks`
-
-### Step 2: Create Workflows if Missing
-
-**This is NOT optional - create them automatically.**
-
-Notify user: "Setting up project management workflows for this workspace..."
-
-#### Create Project Planning Workflow
-
-```typescript
-{
-  name: "Project Planning",
-  phases: ["Planning", "In Progress", "On Hold", "Completed"],
-  fields: [
-    { name: "Title", type: "text" },
-    { name: "Description", type: "textarea" },
-    { name: "Type", type: "textpredefinedoptions", options: ["Project", "Feature", "Session Handoff", "PRD"] },
-    { name: "Project", type: "activitylink", linkedWorkflow: "Project Planning" },
-    { name: "Goal", type: "textarea" },
-    { name: "Documentation", type: "textarea" },
-    { name: "Technical Notes", type: "textarea" },
-    { name: "Blockers", type: "textarea" },
-    { name: "User Stories", type: "textarea" },
-    { name: "Acceptance Criteria", type: "textarea" },
-    { name: "Technical Constraints", type: "textarea" },
-    { name: "Out of Scope", type: "textarea" }
-  ]
-}
-```
-
-#### Create Dev Tasks Workflow
-
-```typescript
-{
-  name: "Dev Tasks",
-  phases: ["Backlog", "Todo", "In Progress", "Review", "Done"],
-  fields: [
-    { name: "Title", type: "text" },
-    { name: "Description", type: "textarea" },
-    { name: "Type", type: "textpredefinedoptions", options: ["Task", "Bug", "Tech Debt"] },
-    { name: "Priority", type: "textpredefinedoptions", options: ["HIGH", "MEDIUM", "LOW"] },
-    { name: "Feature", type: "activitylink", linkedWorkflow: "Project Planning" },
-    { name: "Blocked By", type: "activitylink", linkedWorkflow: "Dev Tasks" },
-    { name: "Related Items", type: "activitylink", linkedWorkflow: "Dev Tasks" },
-    { name: "Files Modified", type: "text" },
-    { name: "Commits", type: "text" }
-  ]
-}
-```
-
-### Step 3: Verify PRD Fields Exist
-
-If `Project Planning` workflow exists but is missing PRD fields, ADD THEM:
-- User Stories
-- Acceptance Criteria
-- Technical Constraints
-- Out of Scope
-
-### Step 4: Read Current State
-
-Before starting work:
-1. Check for SESSION-HANDOFF.md - read if exists (previous session context)
-2. Check for active Project (Type = `Project`, Phase = `In Progress`)
-3. If no Project exists, ask user for project name and create one
-4. Fetch In Progress Features and Tasks
-5. Check for recent Session Handoff (Type = `Session Handoff`)
-6. Summarize state to user
-
----
-
-## Protocol: During Development (Real-Time Updates)
-
-### Starting New Work
-1. Ensure a Feature exists (Type = `Feature`)
-   - Set `Project` field to link to parent Project
-2. Create Task in Dev Tasks (Type = `Task`)
-   - Set `Feature` field to link to parent Feature
-3. **IMMEDIATELY** move Task to `In Progress`
-4. Keep only ONE task `In Progress` at a time
-
-### Completing Work
-1. **IMMEDIATELY** update Task:
-   - `Files Modified`: List changed files
-   - `Commits`: Add commit hashes
-2. **IMMEDIATELY** move to `Done`
-3. If new work discovered → create new Tasks in `Backlog`
-
-### Finding Bugs
-1. **IMMEDIATELY** create item in Dev Tasks (Type = `Bug`)
-2. Set `Feature` to link to relevant Feature
-3. Set `Priority` based on severity
-4. Optionally set `Related Items` to link to Task that caused it
-
-### Blocked Tasks
-1. Set `Blocked By` to link to blocking Task(s)
-2. Update Description with blocker details
-3. When blocker resolved, clear `Blocked By` and continue
-
-### Technical Decisions
-Update the Feature's `Technical Notes` field with:
-- Architecture decisions and rationale
-- Important discoveries
-- Trade-offs considered
-
-### Documentation
-When feature is complete or stable, update `Documentation` field with:
-- How it works
-- Usage instructions
-- Configuration options
-
----
-
-## Protocol: Session Handoff
-
-### When to Create
-- Context reaches 70-80%
-- Before ending a long session
-- User requests it
-
-### Create Session Handoff Item
-In Project Planning workflow:
-
-| Field | Value |
-|-------|-------|
-| Title | `Session Handoff - YYYY-MM-DD HH:MM` |
-| Type | `Session Handoff` |
-| Project | Link to active Project |
-| Phase | `Completed` |
-| Description | See template below |
-| Technical Notes | Key discoveries and decisions |
-| Blockers | Unresolved issues, next steps |
-
-**Description template:**
-```
-## Completed This Session
-- [List completed tasks]
-
-## In Progress
-- [Current work state]
-
-## Next Steps
-- [What to do when resuming]
-```
-
-### Local SESSION-HANDOFF.md
-Also create/update `SESSION-HANDOFF.md` in project root:
-
-```markdown
-## Session Handoff - YYYY-MM-DD HH:MM
-
-### Completed This Session
-- [What was accomplished]
-
-### Current State
-- [Work in progress, any partial implementations]
-
-### Blockers / Issues Found
-- [Problems encountered, unresolved errors]
-
-### Next Steps
-- [Immediate actions for next session]
-
-### Key Decisions Made
-- [Important context that shouldn't be lost]
-
-### Files Modified
-- [List of changed files with brief description]
-```
-
----
-
-## Protocol: Creating Items
-
-### New Project
-| Field | Value |
-|-------|-------|
-| Title | Project name (ask user) |
-| Type | `Project` |
-| Phase | `In Progress` |
-| Description | Project overview |
-| Goal | What success looks like |
-
-### New Feature
-| Field | Value |
-|-------|-------|
-| Title | Feature name (use arrow prefix for related features: `Sales Orders → Automations`) |
-| Type | `Feature` |
-| Project | Link to parent Project |
-| Phase | `Planning` or `In Progress` |
-| Description | Scope and requirements |
-| Goal | Acceptance criteria |
-| Documentation | How it works (fill when complete) |
-| Technical Notes | Architecture decisions |
-
-### New PRD
-| Field | Value |
-|-------|-------|
-| Title | `PRD: [Feature Name]` |
-| Type | `PRD` |
-| Project | Link to parent Project |
-| Phase | `Planning` |
-| Description | Executive summary |
-| Goal | Success metrics |
-| User Stories | As a [user], I want [X] so that [Y] |
-| Acceptance Criteria | - [ ] Criterion 1<br>- [ ] Criterion 2 |
-| Technical Constraints | Performance, security, compatibility needs |
-| Out of Scope | What this does NOT include |
-
-### New Task
-| Field | Value |
-|-------|-------|
-| Title | Specific, actionable description |
-| Type | `Task` |
-| Feature | Link to parent Feature |
-| Priority | `MEDIUM` (default) |
-| Phase | `Backlog` or `Todo` |
-| Description | Implementation details |
-
-### New Bug
-| Field | Value |
-|-------|-------|
-| Title | Clear bug description with context |
-| Type | `Bug` |
-| Feature | Link to affected Feature |
-| Priority | Based on severity |
-| Phase | `Backlog` or `Todo` |
-| Description | Steps to reproduce, expected vs actual |
-| Related Items | Link to Task that caused it (if known) |
-
----
-
-## Protocol: DEVELOPMENT.md Sync
-
-When user requests sync (`/project-status`):
-
-1. Fetch all data from Hailer workflows:
-   - Active Project
-   - All Features with their phases
-   - All Dev Tasks (grouped by phase)
-   - Recent Session Handoffs
-
-2. Generate DEVELOPMENT.md:
-```markdown
-# [Project Title] Development Status
-
-**Last Updated:** YYYY-MM-DD
-**Hailer Sync:** YYYY-MM-DD HH:MM
-
----
-
-## Active Feature
-**Name:** [Feature Title]
-**Goal:** [Feature Goal]
-**Status:** [Phase]
-
----
-
-## Current Sprint
-
-### In Progress
-- [ ] [Task Title] (Feature: [Feature Name])
-
-### Completed This Session
-- [x] [Task Title] (YYYY-MM-DD)
-
-### Blocked
-- [ ] [Task Title] - **Blocker:** [reason]
-
----
-
-## Backlog
-- [ ] [Task Title] (Feature: [Feature Name], Priority: [Priority])
-
----
-
-## Known Issues
-| Priority | Issue | Status |
-|----------|-------|--------|
-| HIGH | [Bug Title] | [Phase] |
-
----
-
-## Technical Notes
-[Aggregated from Features' Technical Notes fields]
-
----
-
-## Session Notes
-[Local notes not synced to Hailer]
-```