haiku-method 2.2.0

package/providers/spec.md

@@ -0,0 +1,67 @@
+---
+category: spec
+description: Bidirectional spec provider — sync specifications and knowledge between H·AI·K·U and documentation platforms
+---
+
+# Spec Provider — Default Instructions
+
+## Inbound: Provider → H·AI·K·U
+
+### During Elaboration
+- Search for existing specifications, PRDs, or design docs related to the intent
+- Pull content and distill into H·AI·K·U context (intent references, unit criteria)
+- Reference specific spec documents in intent.md Context section
+
+### During Stage Elaboration
+- Verify referenced specs haven't changed since the previous stage
+- Check for updated specs before elaborating units
+- Pull cross-studio knowledge: if this intent was triggered by another studio, read the source studio's outputs from the spec provider
+
+### Translation (Provider → H·AI·K·U)
+
+| Provider Concept | H·AI·K·U Concept | Translation |
+|---|---|---|
+| PRD / Requirements doc | Intent context + criteria | Distill requirements into verifiable completion criteria |
+| Design doc / RFC | Stage input reference | Link as input, extract technical constraints |
+| Meeting notes / decisions | Intent knowledge | Distill decisions into intent.md Context section |
+| Wiki page | Stage output (from another studio) | Read as cross-studio input if referenced |
+
+**Key principle:** Provider documents are often verbose, unstructured, and full of context that isn't actionable. Claude distills to the minimum needed: what are the requirements, what are the constraints, what are the decisions. Not a copy — a translation.
+
+## Outbound: H·AI·K·U → Provider
+
+### During Output Persistence
+- Stage outputs scoped as `project` or `intent` can be pushed to the spec provider
+- Write intent knowledge (discovery docs, design briefs, behavioral specs) to the provider in its native format
+- This enables cross-studio data flow: the software studio's design brief in Confluence is readable by the marketing studio's content stage
+
+### During Reflection
+- Push reflection summaries to the spec provider for organizational visibility
+- Write settings recommendations as a decision record
+
+### Translation (H·AI·K·U → Provider)
+
+| H·AI·K·U Concept | Provider Concept | Translation |
+|---|---|---|
+| Discovery document | Wiki page / design doc | Restructure for the provider's format (headings, templates) |
+| Design brief | Linked design doc | Push as structured document with provider-native formatting |
+| Behavioral spec | PRD or spec doc | Format as the team's standard spec template |
+| Reflection summary | Decision record / retrospective | Distill into the team's retro format |
+
+**Key principle:** Don't push markdown frontmatter to Confluence. Push the *content* in the format the provider's audience expects. Claude translates H·AI·K·U's internal representation into whatever the provider needs.
+
+## Sync: Cross-Studio Knowledge
+
+The spec provider is the primary channel for cross-studio data flow:
+
+```
+Studio A (sales) completes → pushes deal context to Confluence
+Studio B (customer-success) starts → reads deal context from Confluence
+```
+
+Claude mediates both directions. The spec provider doesn't need to understand H·AI·K·U's schema — Claude reads the provider's content and produces H·AI·K·U artifacts, or reads H·AI·K·U artifacts and produces provider content.
+
+## Provider Config
+
+Provider-specific configuration lives under `providers.spec.config` in `.haiku/settings.yml`.
+Schema: `${CLAUDE_PLUGIN_ROOT}/schemas/providers/{type}.schema.json`

package/providers/ticketing.md

@@ -0,0 +1,101 @@
+---
+category: ticketing
+description: Bidirectional ticketing provider — sync H·AI·K·U state to/from issue trackers
+---
+
+# Ticketing Provider — Default Instructions
+
+## Inbound: Provider → H·AI·K·U
+
+On session start, check the provider for events that affect active intents:
+
+- **New tickets** created outside H·AI·K·U that reference the intent epic → surface as potential new units
+- **Status changes** on unit tickets made by humans → update unit status in H·AI·K·U
+- **Comments/feedback** added to tickets → load as context for the current stage's hats
+- **Assignments** changed → note ownership changes in intent state
+
+### Translation (Provider → H·AI·K·U)
+
+The provider's data model may not match H·AI·K·U's frontmatter. Claude distills:
+
+| Provider Concept | H·AI·K·U Concept | Translation |
+|---|---|---|
+| Epic / Parent Issue | Intent | Map title, description, acceptance criteria |
+| Sub-task / Child Issue | Unit | Map to unit with completion criteria from ticket description |
+| Sprint / Iteration | Bolt | Map sprint assignment to current iteration context |
+| Status (To Do / In Progress / Done) | Unit status (pending / active / completed) | Direct mapping via status categories |
+| Blocked flag / link | depends_on | Map blocking relationships to DAG dependencies |
+| Labels / Components | unit_types / stage | Infer stage context from labels |
+| Story points / Estimate | (informational) | Include in unit context, not enforced |
+
+**Key principle:** Not all provider data has a H·AI·K·U equivalent. Claude reads what's useful, ignores what isn't, and never forces provider data into fields that don't fit.
+
+## Outbound: H·AI·K·U → Provider
+
+### Ticket Creation (During Decomposition)
+- **Epic handling:**
+  - If `epic` is already set in intent.md frontmatter (provided by product), link all tickets to that existing epic — do NOT create a new one
+  - If `epic` is empty, create one **epic** per intent (title from intent, description from Problem + Solution) and store the key in intent.md frontmatter: `epic: PROJ-123`
+- **Every unit ticket MUST be linked to the intent epic** — the epic is the single parent that groups all unit work. Only skip if `config.epic_link` is explicitly `"none"`.
+- Map unit `depends_on` to ticket **blocked-by** relationships
+- Store ticket key in unit frontmatter: `ticket: PROJ-124`
+
+### Status Sync (During Execution)
+- **Builder starts unit** → Move ticket to In Progress
+- **Unit passes review** → Move ticket to Done
+- **Unit blocked** → Flag ticket as Blocked, add blocker description as comment
+- **Reviewer rejects** → Add review feedback as ticket comment, keep In Progress
+- **Stage completes** → Update epic status/progress
+
+### Translation (H·AI·K·U → Provider)
+
+| H·AI·K·U Concept | Provider Concept | Translation |
+|---|---|---|
+| Intent title + description | Epic title + description | Direct, with markdown → provider format |
+| Unit spec + criteria | Ticket description + checklist | Structure as Overview, Criteria, Dependencies, Notes |
+| Unit depends_on | Blocked-by links | Create issue links using configured link types |
+| Stage review findings | Ticket comments | Post review summary as structured comment |
+| Intent completion | Epic status → Done | Update when all stages complete |
+
+### Ticket Content
+
+**CRITICAL**: Always pass description strings with real newlines (multiline), never escaped `\n` literals.
+
+Structure ticket descriptions with these sections (omit any that are empty):
+
+1. **Overview** — unit description (the prose from the unit file, not just the title)
+2. **Completion Criteria** — checklist (`- [ ] criterion`)
+3. **Dependencies** — blocked-by units with ticket keys if known
+4. **Technical Notes** — implementation guidance, constraints, or architectural notes
+
+The goal is a ticket that gives a person full context without needing to read `.haiku/` files.
+
+## Sync: Event Discovery
+
+On session start (or when `/haiku:pickup` is invoked), check the provider for relevant events:
+
+```
+1. Load active intent's epic key from frontmatter
+2. Query provider for changes since last sync timestamp
+3. Surface: new comments, status changes, new sub-tickets, assignment changes
+4. Update local state to reflect provider changes
+5. Record sync timestamp in intent state
+```
+
+This is pull-based — not real-time. It runs when the user starts working.
+
+## Provider Config
+
+Provider-specific configuration lives under `providers.ticketing.config` in `.haiku/settings.yml`.
+Schema: `${CLAUDE_PLUGIN_ROOT}/schemas/providers/{type}.schema.json`
+
+**Never create top-level provider keys** (e.g., no top-level `jira:` key). All config goes under `providers.ticketing.config`.
+
+When config fields are present, use them for ticket creation:
+- `issue_type` / `issue_type_id` → set on created tickets
+- `labels` → apply discipline-mapped labels to each unit ticket
+- `story_points: required` → estimate and set story points
+- `epic_link: required` → link all tickets to the intent epic
+- `issue_links: required` → create Blocks/Blocked-By links from unit `depends_on`
+- `link_types` → use configured link type names (defaults: "Blocks" / "Is Blocked By")
+- `details` → additional ticket content requirements

package/schemas/providers/canva.schema.json

@@ -0,0 +1,29 @@
+{
+	"$schema": "http://json-schema.org/draft-07/schema#",
+	"$id": "https://haikumethod.ai/schemas/providers/canva.schema.json",
+	"title": "Canva Provider Config",
+	"description": "Provider-specific configuration for Canva design provider",
+	"type": "object",
+	"properties": {
+		"brand_kit_id": {
+			"type": "string",
+			"description": "Canva Brand Kit ID for consistent branding"
+		},
+		"default_folder": {
+			"type": "string",
+			"description": "Default Canva folder path for organizing designs"
+		},
+		"export_format": {
+			"type": "string",
+			"enum": ["png", "jpg", "pdf"],
+			"default": "png",
+			"description": "Default export format for design assets"
+		},
+		"url_template": {
+			"type": "string",
+			"description": "URL template for linking to Canva designs. Variables: {key} (Canva design ID)",
+			"default": "https://canva.com/design/{key}"
+		}
+	},
+	"additionalProperties": false
+}

package/schemas/providers/confluence.schema.json

@@ -0,0 +1,31 @@
+{
+	"$schema": "http://json-schema.org/draft-07/schema#",
+	"$id": "https://haiku.dev/schemas/providers/confluence.schema.json",
+	"title": "Confluence Provider Config",
+	"description": "Provider-specific configuration for Confluence spec provider",
+	"type": "object",
+	"properties": {
+		"space_key": {
+			"type": "string",
+			"description": "Confluence space key"
+		},
+		"cloud_id": {
+			"type": "string",
+			"description": "Atlassian site URL or cloud ID"
+		},
+		"parent_page_id": {
+			"type": "string",
+			"description": "Parent page ID under which spec pages are created"
+		},
+		"template_id": {
+			"type": "string",
+			"description": "Confluence page template ID for new spec pages"
+		},
+		"url_template": {
+			"type": "string",
+			"description": "URL template for linking to Confluence pages. Variables: {cloud_id} (Atlassian site URL), {space_key} (Confluence space key), {key} (page ID)",
+			"default": "https://{cloud_id}/wiki/spaces/{space_key}/pages/{key}"
+		}
+	},
+	"additionalProperties": false
+}

package/schemas/providers/discord.schema.json

@@ -0,0 +1,18 @@
+{
+	"$schema": "http://json-schema.org/draft-07/schema#",
+	"$id": "https://haiku.dev/schemas/providers/discord.schema.json",
+	"title": "Discord Provider Config",
+	"description": "Provider-specific configuration for Discord comms provider",
+	"type": "object",
+	"properties": {
+		"guild_id": {
+			"type": "string",
+			"description": "Discord server (guild) ID"
+		},
+		"channel_id": {
+			"type": "string",
+			"description": "Default Discord channel ID for notifications"
+		}
+	},
+	"additionalProperties": false
+}

package/schemas/providers/excalidraw.schema.json

@@ -0,0 +1,22 @@
+{
+	"$schema": "http://json-schema.org/draft-07/schema#",
+	"$id": "https://haikumethod.ai/schemas/providers/excalidraw.schema.json",
+	"title": "Excalidraw Provider Config",
+	"description": "Provider-specific configuration for Excalidraw design provider",
+	"type": "object",
+	"properties": {
+		"mcp_mode": {
+			"type": "string",
+			"enum": ["remote", "local"],
+			"default": "remote",
+			"description": "Whether to use the remote Excalidraw service or a local instance"
+		},
+		"style": {
+			"type": "string",
+			"enum": ["hand-drawn", "architect", "artist", "cartoonist"],
+			"default": "hand-drawn",
+			"description": "Default drawing style for generated designs"
+		}
+	},
+	"additionalProperties": false
+}

package/schemas/providers/figma.schema.json

@@ -0,0 +1,27 @@
+{
+	"$schema": "http://json-schema.org/draft-07/schema#",
+	"$id": "https://haiku.dev/schemas/providers/figma.schema.json",
+	"title": "Figma Provider Config",
+	"description": "Provider-specific configuration for Figma design provider",
+	"type": "object",
+	"properties": {
+		"project_id": {
+			"type": "string",
+			"description": "Figma project ID"
+		},
+		"team_id": {
+			"type": "string",
+			"description": "Figma team ID"
+		},
+		"file_key": {
+			"type": "string",
+			"description": "Figma file key for the primary design file"
+		},
+		"url_template": {
+			"type": "string",
+			"description": "URL template for linking to Figma files. Variables: {key} (Figma file key)",
+			"default": "https://figma.com/file/{key}"
+		}
+	},
+	"additionalProperties": false
+}

package/schemas/providers/github-git.schema.json

@@ -0,0 +1,30 @@
+{
+	"$schema": "http://json-schema.org/draft-07/schema#",
+	"$id": "https://haiku.dev/schemas/providers/github-git.schema.json",
+	"title": "GitHub Git Provider Config",
+	"description": "Provider-specific configuration for GitHub git storage",
+	"type": "object",
+	"properties": {
+		"auto_push": {
+			"type": "boolean",
+			"default": true,
+			"description": "Push to remote after every state commit. Disable for offline-first workflows."
+		},
+		"auto_pr": {
+			"type": "boolean",
+			"default": true,
+			"description": "Automatically create a pull request at intent completion"
+		},
+		"default_branch": {
+			"type": "string",
+			"default": "main",
+			"description": "Base branch for pull requests (target branch)"
+		},
+		"remote": {
+			"type": "string",
+			"default": "origin",
+			"description": "Git remote name to push to and create PRs against"
+		}
+	},
+	"additionalProperties": false
+}

package/schemas/providers/github-issues.schema.json

@@ -0,0 +1,57 @@
+{
+	"$schema": "http://json-schema.org/draft-07/schema#",
+	"$id": "https://haiku.dev/schemas/providers/github-issues.schema.json",
+	"title": "GitHub Issues Provider Config",
+	"description": "Provider-specific configuration for GitHub Issues ticketing",
+	"type": "object",
+	"properties": {
+		"labels": {
+			"type": "object",
+			"description": "Map of unit discipline to GitHub label arrays",
+			"additionalProperties": {
+				"type": "array",
+				"items": { "type": "string" }
+			}
+		},
+		"story_points": {
+			"type": "string",
+			"enum": ["required", "optional", "none"],
+			"default": "none",
+			"description": "Whether to set story point estimates (requires GitHub Projects custom field)"
+		},
+		"epic_link": {
+			"type": "string",
+			"enum": ["required", "optional", "none"],
+			"default": "required",
+			"description": "Whether to link unit issues to a milestone or tracked-by parent issue"
+		},
+		"issue_links": {
+			"type": "string",
+			"enum": ["required", "optional", "none"],
+			"default": "required",
+			"description": "Whether to create task list references from unit depends_on DAG"
+		},
+		"milestone": {
+			"type": "string",
+			"description": "GitHub milestone name or number to use as the epic equivalent"
+		},
+		"project_number": {
+			"type": "integer",
+			"description": "GitHub Projects (v2) board number to add issues to"
+		},
+		"details": {
+			"type": "object",
+			"description": "Additional issue content requirements (field name to requirement level)",
+			"additionalProperties": {
+				"type": "string",
+				"enum": ["required", "optional", "none"]
+			}
+		},
+		"url_template": {
+			"type": "string",
+			"description": "URL template for linking to GitHub issues. Variables: {owner} (repo owner), {repo} (repo name), {number} (issue number)",
+			"default": "https://github.com/{owner}/{repo}/issues/{number}"
+		}
+	},
+	"additionalProperties": false
+}

package/schemas/providers/gitlab-issues.schema.json

@@ -0,0 +1,81 @@
+{
+	"$schema": "http://json-schema.org/draft-07/schema#",
+	"$id": "https://haiku.dev/schemas/providers/gitlab-issues.schema.json",
+	"title": "GitLab Issues Provider Config",
+	"description": "Provider-specific configuration for GitLab Issues ticketing",
+	"type": "object",
+	"properties": {
+		"project_id": {
+			"type": "string",
+			"description": "GitLab project ID or path (e.g., 'my-group/my-project')"
+		},
+		"issue_type": {
+			"type": "string",
+			"default": "issue",
+			"enum": ["issue", "incident", "test_case"],
+			"description": "Default GitLab issue type for unit tickets"
+		},
+		"labels": {
+			"type": "object",
+			"description": "Map of unit discipline to GitLab label arrays",
+			"additionalProperties": {
+				"type": "array",
+				"items": { "type": "string" }
+			}
+		},
+		"story_points": {
+			"type": "string",
+			"enum": ["required", "optional", "none"],
+			"default": "none",
+			"description": "Whether to set weight on unit issues"
+		},
+		"epic_link": {
+			"type": "string",
+			"enum": ["required", "optional", "none"],
+			"default": "required",
+			"description": "Whether to link unit issues to a GitLab epic"
+		},
+		"issue_links": {
+			"type": "string",
+			"enum": ["required", "optional", "none"],
+			"default": "required",
+			"description": "Whether to create blocking relationships from unit depends_on DAG"
+		},
+		"link_types": {
+			"type": "object",
+			"description": "GitLab link type names for DAG relationships",
+			"properties": {
+				"blocks": {
+					"type": "string",
+					"default": "blocks",
+					"description": "Link type for 'blocks' direction"
+				},
+				"blocked_by": {
+					"type": "string",
+					"default": "is_blocked_by",
+					"description": "Link type for 'blocked by' direction"
+				}
+			},
+			"additionalProperties": false
+		},
+		"milestone": {
+			"type": "string",
+			"description": "GitLab milestone title to assign unit issues to"
+		},
+		"details": {
+			"type": "object",
+			"description": "Additional issue content requirements (field name to requirement level)",
+			"additionalProperties": {
+				"type": "string",
+				"enum": ["required", "optional", "none"]
+			}
+		},
+		"url_template": {
+			"type": "string",
+			"description": "URL template for linking to GitLab issues. Variables: {host} (GitLab host), {project} (project path), {number} (issue number)",
+			"default": "https://{host}/{project}/-/issues/{number}"
+		}
+	},
+	"required": ["project_id"],
+	"additionalProperties": false
+}

package/schemas/providers/google-docs.schema.json

@@ -0,0 +1,23 @@
+{
+	"$schema": "http://json-schema.org/draft-07/schema#",
+	"$id": "https://haiku.dev/schemas/providers/google-docs.schema.json",
+	"title": "Google Docs Provider Config",
+	"description": "Provider-specific configuration for Google Docs spec provider",
+	"type": "object",
+	"properties": {
+		"folder_id": {
+			"type": "string",
+			"description": "Google Drive folder ID where spec documents are stored"
+		},
+		"template_doc_id": {
+			"type": "string",
+			"description": "Google Docs template document ID for new spec pages"
+		},
+		"url_template": {
+			"type": "string",
+			"description": "URL template for linking to Google Docs. Variables: {key} (Google Docs document ID)",
+			"default": "https://docs.google.com/document/d/{key}"
+		}
+	},
+	"additionalProperties": false
+}

package/schemas/providers/hubspot.schema.json

@@ -0,0 +1,41 @@
+{
+	"$schema": "http://json-schema.org/draft-07/schema#",
+	"$id": "https://haiku.dev/schemas/providers/hubspot.schema.json",
+	"title": "HubSpot CRM Provider Config",
+	"description": "Provider-specific configuration for HubSpot CRM",
+	"type": "object",
+	"properties": {
+		"pipeline_id": {
+			"type": "string",
+			"description": "HubSpot deal pipeline ID to monitor"
+		},
+		"stage_mapping": {
+			"type": "object",
+			"description": "Map HubSpot deal stages to H·AI·K·U studio stages",
+			"additionalProperties": {
+				"type": "string"
+			},
+			"examples": [{
+				"appointmentscheduled": "research",
+				"qualifiedtobuy": "qualification",
+				"presentationscheduled": "proposal",
+				"decisionmakerboughtin": "negotiation",
+				"closedwon": "close",
+				"closedlost": "close"
+			}]
+		},
+		"sync_activities": {
+			"type": "boolean",
+			"default": true,
+			"description": "Log H·AI·K·U stage transitions as HubSpot activities"
+		},
+		"trigger_on_stage": {
+			"type": "array",
+			"items": { "type": "string" },
+			"description": "HubSpot stages that should surface as intent creation suggestions",
+			"examples": [["closedwon", "qualifiedtobuy"]]
+		}
+	},
+	"required": [],
+	"additionalProperties": false
+}

package/schemas/providers/jira.schema.json

@@ -0,0 +1,90 @@
+{
+	"$schema": "http://json-schema.org/draft-07/schema#",
+	"$id": "https://haiku.dev/schemas/providers/jira.schema.json",
+	"title": "Jira Provider Config",
+	"description": "Provider-specific configuration for Jira ticketing",
+	"type": "object",
+	"properties": {
+		"project_key": {
+			"type": "string",
+			"description": "Jira project key (e.g., PROJ)"
+		},
+		"cloud_id": {
+			"type": "string",
+			"description": "Atlassian site URL or cloud ID"
+		},
+		"issue_type": {
+			"type": "string",
+			"default": "Task",
+			"description": "Default issue type name for unit tickets"
+		},
+		"issue_type_id": {
+			"type": "string",
+			"description": "Jira issue type ID (overrides issue_type name lookup)"
+		},
+		"labels": {
+			"type": "object",
+			"description": "Map of unit discipline to Jira label arrays",
+			"additionalProperties": {
+				"type": "array",
+				"items": { "type": "string" }
+			},
+			"examples": [{ "backend": ["Elixir"], "frontend": ["React", "TypeScript"] }]
+		},
+		"story_points": {
+			"type": "string",
+			"enum": ["required", "optional", "none"],
+			"default": "none",
+			"description": "Whether to estimate and set story points on unit tickets"
+		},
+		"story_points_field": {
+			"type": "string",
+			"default": "story_points",
+			"description": "Jira field ID for story points (e.g., 'customfield_10014'). Varies per Jira instance."
+		},
+		"epic_link": {
+			"type": "string",
+			"enum": ["required", "optional", "none"],
+			"default": "required",
+			"description": "Whether to link all unit tickets to the intent epic"
+		},
+		"issue_links": {
+			"type": "string",
+			"enum": ["required", "optional", "none"],
+			"default": "required",
+			"description": "Whether to create Blocks/Blocked-By links from unit depends_on DAG"
+		},
+		"link_types": {
+			"type": "object",
+			"description": "Jira link type names for DAG relationships",
+			"properties": {
+				"blocks": {
+					"type": "string",
+					"default": "Blocks",
+					"description": "Link type name for 'blocks' direction"
+				},
+				"blocked_by": {
+					"type": "string",
+					"default": "Is Blocked By",
+					"description": "Link type name for 'blocked by' direction"
+				}
+			},
+			"additionalProperties": false
+		},
+		"details": {
+			"type": "object",
+			"description": "Additional ticket content requirements (field name to requirement level)",
+			"additionalProperties": {
+				"type": "string",
+				"enum": ["required", "optional", "none"]
+			}
+		},
+		"url_template": {
+			"type": "string",
+			"description": "URL template for linking to Jira issues. Variables: {cloud_id} (Atlassian site URL), {key} (issue key, e.g. PROJ-123)",
+			"default": "https://{cloud_id}/browse/{key}"
+		}
+	},
+	"required": ["project_key"],
+	"additionalProperties": false
+}