feed-the-machine 1.6.1 → 1.7.1

package/ftm-routine/SKILL.md

@@ -1,170 +1,170 @@
----
-name: ftm-routine
-description: Execute named, recurring multi-step workflows from YAML definitions. Use when user says "routine", "run routine", "ftm-routine", "morning triage", or names a known routine.
----
-
-# FTM Routine Runner
-
-Routines are named, recurring multi-step workflows defined as YAML in `~/.ftm/routines/`. Each routine specifies steps that combine skill invocations, MCP operations, and approval gates.
-
-## Routine Format
-
-Routines are stored as YAML files in `~/.ftm/routines/`:
-
-```yaml
-name: morning-triage
-description: Check all inboxes, prioritize, and plan the day
-trigger: manual  # only "manual" for v1, future: "schedule", "event"
-tags: [triage, daily, ops]
-
-steps:
-  - name: Check Jira backlog
-    action: mcp
-    tool: jira_search
-    params:
-      jql: "assignee = currentUser() AND status != Done ORDER BY priority DESC"
-    approval: none  # no approval needed for read operations
-
-  - name: Check Freshservice tickets
-    action: mcp
-    tool: get_tickets
-    params:
-      filter: "agent_id:me AND status:2"  # open tickets assigned to me
-    approval: none
-
-  - name: Check Slack mentions
-    action: mcp
-    tool: slack_get_channel_history
-    params:
-      channel: "general"
-      limit: 20
-    approval: none
-
-  - name: Check email
-    action: mcp
-    tool: search_emails
-    params:
-      query: "is:unread"
-      max_results: 10
-    approval: none
-
-  - name: Synthesize and prioritize
-    action: skill
-    skill: ftm-mind
-    input: "Based on the above: prioritize today's work. What's urgent? What can wait?"
-    approval: review  # show synthesis for user review before proceeding
-
-  - name: Create today's plan
-    action: skill
-    skill: ftm-mind
-    input: "Create a plan for today's top 3 priorities"
-    approval: approve  # full plan approval before execution
-```
-
-## Invocation
-
-```
-/ftm-routine morning-triage
-```
-
-Or via ftm-mind when it detects a routine name:
-```
-/ftm run my morning triage
-```
-
-## Execution Flow
-
-1. **Load routine** — Read `~/.ftm/routines/[name].yml`
-2. **Validate** — Check all referenced MCP tools and skills are available
-3. **Present as plan** — Convert routine steps to the standard plan format:
-   ```
-   Routine: morning-triage — "Check all inboxes, prioritize, and plan the day"
-
-   1. Check Jira backlog (auto)
-   2. Check Freshservice tickets (auto)
-   3. Check Slack mentions (auto)
-   4. Check email (auto)
-   5. Synthesize and prioritize (review)
-   6. Create today's plan (approve)
-
-   Steps 1-4 run automatically. Step 5 pauses for your review.
-   Step 6 requires your approval before execution.
-
-   Say "go" to start.
-   ```
-4. **Execute** — Run steps in order, respecting approval gates:
-   - `approval: none` — execute automatically, show results
-   - `approval: review` — execute, show results, wait for "continue" or "stop"
-   - `approval: approve` — show plan, wait for "go" before executing
-
-## Step Types
-
-| Action | Description | Example |
-|---|---|---|
-| `mcp` | Call an MCP tool directly | `jira_search`, `slack_post_message` |
-| `skill` | Invoke an FTM skill | `ftm-mind`, `ftm-debug`, `ftm-brainstorm` |
-| `bash` | Run a shell command | `npm test`, `git status` |
-
-## Creating Routines
-
-Users create routines by:
-1. Writing YAML directly to `~/.ftm/routines/[name].yml`
-2. Saving a successful plan as a routine: "save as routine" (future enhancement)
-3. Asking ftm-mind: "create a routine for my morning triage"
-
-## Listing Routines
-
-```
-/ftm-routine list
-```
-Shows all routines in `~/.ftm/routines/` with name and description.
-
-## Example Routines
-
-### morning-triage
-Check Jira, Freshservice, Slack, email → synthesize → prioritize → plan
-
-### deploy-checklist
-Run tests → check CI → review changelog → create release tag → monitor
-
-### new-hire-setup
-Create accounts → set permissions → send welcome email → schedule onboarding
-
-### incident-response
-Check Sentry → check logs → notify channel → create Jira ticket → start investigation
-
-## Requirements
-
-- reference: `~/.ftm/routines/` | required | YAML routine definitions directory
-- config: `~/.claude/ftm-config.yml` | optional | model preferences for skill-type steps
-
-## Risk
-
-- level: medium_write
-- scope: executes MCP tool calls, skill invocations, and bash commands as defined by the routine; external-facing mutations depend entirely on routine definition; approval gates in the routine control which steps require user confirmation
-- rollback: depends on individual routine steps; steps with approval: approve gate let user review before execution; MCP writes (Jira, Slack, email) may not be reversible
-
-## Approval Gates
-
-- trigger: routine step with approval: approve | action: show plan for that step and wait for "go" before executing
-- trigger: routine step with approval: review | action: execute step, show results, wait for "continue" or "stop"
-- trigger: routine step with approval: none | action: execute automatically and show results
-- complexity_routing: micro → auto | small → auto | medium → plan_first (show full routine plan first) | large → plan_first | xl → always_ask
-
-## Fallbacks
-
-- condition: routine YAML file not found | action: show "Routine not found" with list of available routines from ~/.ftm/routines/
-- condition: MCP tool referenced in routine not available | action: report unavailable tool, ask user whether to skip that step or abort
-- condition: skill referenced in routine not available | action: report unavailable skill, ask user whether to skip or abort
-- condition: bash command in step fails with non-zero exit | action: report failure output, ask user whether to continue or abort
-
-## Capabilities
-
-- mcp: various | optional | determined by individual routine definitions
-- cli: various | optional | bash steps in routine definitions
-- env: none required directly
-
-## Event Payloads
-
-### (none)
-ftm-routine does not emit its own events. Events are emitted by the MCPs and skills invoked during routine execution.
+---
+name: ftm-routine
+description: Execute named, recurring multi-step workflows from YAML definitions. Use when user says "routine", "run routine", "ftm-routine", "morning triage", or names a known routine.
+---
+
+# FTM Routine Runner
+
+Routines are named, recurring multi-step workflows defined as YAML in `~/.ftm/routines/`. Each routine specifies steps that combine skill invocations, MCP operations, and approval gates.
+
+## Routine Format
+
+Routines are stored as YAML files in `~/.ftm/routines/`:
+
+```yaml
+name: morning-triage
+description: Check all inboxes, prioritize, and plan the day
+trigger: manual  # only "manual" for v1, future: "schedule", "event"
+tags: [triage, daily, ops]
+
+steps:
+  - name: Check Jira backlog
+    action: mcp
+    tool: jira_search
+    params:
+      jql: "assignee = currentUser() AND status != Done ORDER BY priority DESC"
+    approval: none  # no approval needed for read operations
+
+  - name: Check Freshservice tickets
+    action: mcp
+    tool: get_tickets
+    params:
+      filter: "agent_id:me AND status:2"  # open tickets assigned to me
+    approval: none
+
+  - name: Check Slack mentions
+    action: mcp
+    tool: slack_get_channel_history
+    params:
+      channel: "general"
+      limit: 20
+    approval: none
+
+  - name: Check email
+    action: mcp
+    tool: search_emails
+    params:
+      query: "is:unread"
+      max_results: 10
+    approval: none
+
+  - name: Synthesize and prioritize
+    action: skill
+    skill: ftm-mind
+    input: "Based on the above: prioritize today's work. What's urgent? What can wait?"
+    approval: review  # show synthesis for user review before proceeding
+
+  - name: Create today's plan
+    action: skill
+    skill: ftm-mind
+    input: "Create a plan for today's top 3 priorities"
+    approval: approve  # full plan approval before execution
+```
+
+## Invocation
+
+```
+/ftm-routine morning-triage
+```
+
+Or via ftm-mind when it detects a routine name:
+```
+/ftm run my morning triage
+```
+
+## Execution Flow
+
+1. **Load routine** — Read `~/.ftm/routines/[name].yml`
+2. **Validate** — Check all referenced MCP tools and skills are available
+3. **Present as plan** — Convert routine steps to the standard plan format:
+   ```
+   Routine: morning-triage — "Check all inboxes, prioritize, and plan the day"
+
+   1. Check Jira backlog (auto)
+   2. Check Freshservice tickets (auto)
+   3. Check Slack mentions (auto)
+   4. Check email (auto)
+   5. Synthesize and prioritize (review)
+   6. Create today's plan (approve)
+
+   Steps 1-4 run automatically. Step 5 pauses for your review.
+   Step 6 requires your approval before execution.
+
+   Say "go" to start.
+   ```
+4. **Execute** — Run steps in order, respecting approval gates:
+   - `approval: none` — execute automatically, show results
+   - `approval: review` — execute, show results, wait for "continue" or "stop"
+   - `approval: approve` — show plan, wait for "go" before executing
+
+## Step Types
+
+| Action | Description | Example |
+|---|---|---|
+| `mcp` | Call an MCP tool directly | `jira_search`, `slack_post_message` |
+| `skill` | Invoke an FTM skill | `ftm-mind`, `ftm-debug`, `ftm-brainstorm` |
+| `bash` | Run a shell command | `npm test`, `git status` |
+
+## Creating Routines
+
+Users create routines by:
+1. Writing YAML directly to `~/.ftm/routines/[name].yml`
+2. Saving a successful plan as a routine: "save as routine" (future enhancement)
+3. Asking ftm-mind: "create a routine for my morning triage"
+
+## Listing Routines
+
+```
+/ftm-routine list
+```
+Shows all routines in `~/.ftm/routines/` with name and description.
+
+## Example Routines
+
+### morning-triage
+Check Jira, Freshservice, Slack, email → synthesize → prioritize → plan
+
+### deploy-checklist
+Run tests → check CI → review changelog → create release tag → monitor
+
+### new-hire-setup
+Create accounts → set permissions → send welcome email → schedule onboarding
+
+### incident-response
+Check Sentry → check logs → notify channel → create Jira ticket → start investigation
+
+## Requirements
+
+- reference: `~/.ftm/routines/` | required | YAML routine definitions directory
+- config: `~/.claude/ftm-config.yml` | optional | model preferences for skill-type steps
+
+## Risk
+
+- level: medium_write
+- scope: executes MCP tool calls, skill invocations, and bash commands as defined by the routine; external-facing mutations depend entirely on routine definition; approval gates in the routine control which steps require user confirmation
+- rollback: depends on individual routine steps; steps with approval: approve gate let user review before execution; MCP writes (Jira, Slack, email) may not be reversible
+
+## Approval Gates
+
+- trigger: routine step with approval: approve | action: show plan for that step and wait for "go" before executing
+- trigger: routine step with approval: review | action: execute step, show results, wait for "continue" or "stop"
+- trigger: routine step with approval: none | action: execute automatically and show results
+- complexity_routing: micro → auto | small → auto | medium → plan_first (show full routine plan first) | large → plan_first | xl → always_ask
+
+## Fallbacks
+
+- condition: routine YAML file not found | action: show "Routine not found" with list of available routines from ~/.ftm/routines/
+- condition: MCP tool referenced in routine not available | action: report unavailable tool, ask user whether to skip that step or abort
+- condition: skill referenced in routine not available | action: report unavailable skill, ask user whether to skip or abort
+- condition: bash command in step fails with non-zero exit | action: report failure output, ask user whether to continue or abort
+
+## Capabilities
+
+- mcp: various | optional | determined by individual routine definitions
+- cli: various | optional | bash steps in routine definitions
+- env: none required directly
+
+## Event Payloads
+
+### (none)
+ftm-routine does not emit its own events. Events are emitted by the MCPs and skills invoked during routine execution.

package/ftm-routine.yml

@@ -1,4 +1,4 @@
----
-name: ftm-routine
-description: Execute named, recurring multi-step workflows from YAML definitions. Use when user says "routine", "run routine", "ftm-routine", "morning triage", or names a known routine. Routines are reusable workflows stored in ~/.ftm/routines/ that execute through the normal plan-approve flow.
----
+---
+name: ftm-routine
+description: Execute named, recurring multi-step workflows from YAML definitions. Use when user says "routine", "run routine", "ftm-routine", "morning triage", or names a known routine. Routines are reusable workflows stored in ~/.ftm/routines/ that execute through the normal plan-approve flow.
+---

package/ftm-state/blackboard/capabilities.json

@@ -1,5 +1,5 @@
-{
-  "discovered_at": null,
-  "expires_at": null,
-  "capabilities": []
-}
+{
+  "discovered_at": null,
+  "expires_at": null,
+  "capabilities": []
+}

package/ftm-state/blackboard/capabilities.schema.json

@@ -1,27 +1,27 @@
-{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "title": "FTM Capabilities Snapshot",
-  "type": "object",
-  "required": ["discovered_at", "expires_at", "capabilities"],
-  "properties": {
-    "discovered_at": { "type": "string", "format": "date-time" },
-    "expires_at": { "type": "string", "format": "date-time" },
-    "capabilities": {
-      "type": "array",
-      "items": {
-        "type": "object",
-        "required": ["name", "type", "verified", "confidence"],
-        "properties": {
-          "name": { "type": "string" },
-          "type": { "type": "string", "enum": ["mcp", "cli", "api", "env", "browser"] },
-          "verified": { "type": "boolean" },
-          "last_verified_at": { "type": "string", "format": "date-time" },
-          "operations_verified": { "type": "array", "items": { "type": "string" } },
-          "path": { "type": "string" },
-          "version": { "type": "string" },
-          "confidence": { "type": "string", "enum": ["verified", "known", "inferred", "unavailable"] }
-        }
-      }
-    }
-  }
-}
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "title": "FTM Capabilities Snapshot",
+  "type": "object",
+  "required": ["discovered_at", "expires_at", "capabilities"],
+  "properties": {
+    "discovered_at": { "type": "string", "format": "date-time" },
+    "expires_at": { "type": "string", "format": "date-time" },
+    "capabilities": {
+      "type": "array",
+      "items": {
+        "type": "object",
+        "required": ["name", "type", "verified", "confidence"],
+        "properties": {
+          "name": { "type": "string" },
+          "type": { "type": "string", "enum": ["mcp", "cli", "api", "env", "browser"] },
+          "verified": { "type": "boolean" },
+          "last_verified_at": { "type": "string", "format": "date-time" },
+          "operations_verified": { "type": "array", "items": { "type": "string" } },
+          "path": { "type": "string" },
+          "version": { "type": "string" },
+          "confidence": { "type": "string", "enum": ["verified", "known", "inferred", "unavailable"] }
+        }
+      }
+    }
+  }
+}

package/ftm-state/blackboard/context.json

@@ -1,23 +1,37 @@
-{
-  "current_task": {
-    "id": null,
-    "description": null,
-    "type": null,
-    "started_at": null,
-    "status": null
-  },
-  "recent_decisions": [],
-  "active_constraints": [],
-  "user_preferences": {
-    "communication_style": null,
-    "approval_gates": null,
-    "default_model_profile": null
-  },
-  "session_metadata": {
-    "started_at": null,
-    "last_updated": null,
-    "conversation_id": null,
-    "messages_count": 0,
-    "skills_invoked": []
-  }
-}
+{
+  "current_task": {
+    "id": "hackathon-github-pages-site",
+    "description": "Built and published GitHub Pages site for hackathon team — homepage, playbook, flow map, all interlinked",
+    "type": "hackathon-prep",
+    "started_at": "2026-03-23T00:00:00Z",
+    "status": "completed",
+    "next_action": "none — site is live at klaviyokio.github.io/onboard-the-hackathon"
+  },
+  "recent_decisions": [
+    {
+      "decision": "Used GitHub Pages with static HTML instead of a framework",
+      "reason": "Simple, fast deployment for hackathon team reference pages"
+    },
+    {
+      "decision": "Restored full docx content into playbook.html while keeping coffee-shop design",
+      "reason": "HTML version had trimmed role descriptions — docx had the complete detail"
+    },
+    {
+      "decision": "Fixed flow.html by porting missing elements from agent-flow-map.html",
+      "reason": "Node overlap, missing transcript node, chat bubbles, and annotations"
+    }
+  ],
+  "active_constraints": [],
+  "user_preferences": {
+    "communication_style": "concise, technical",
+    "approval_gates": "user prefers direct action over excessive planning for small changes",
+    "default_model_profile": null
+  },
+  "session_metadata": {
+    "started_at": "2026-03-23T00:00:00Z",
+    "last_updated": "2026-03-23T00:00:00Z",
+    "conversation_id": null,
+    "messages_count": 20,
+    "skills_invoked": []
+  }
+}

package/ftm-state/blackboard/experiences/doom-statusline-fix.json

@@ -0,0 +1,26 @@
+{
+  "id": "doom-statusline-fix",
+  "task_type": "developer-tooling",
+  "tags": ["statusline", "doom-hud", "terminal", "claude-code", "ansi"],
+  "outcome": "success",
+  "timestamp": "2026-03-22T00:00:00Z",
+  "lessons": [
+    "Non-Warp statusline path loads ANSI face art by default — disable by skipping the ansi_faces.json load",
+    "MOOD label (IDDQD etc) is appended in both the overlay state and the Row 3 printf — both need removal",
+    "statusline-setup agent type exists for this kind of work"
+  ],
+  "files_touched": [
+    "~/.claude/scripts/doom-statusline.sh"
+  ],
+  "stakeholders": [],
+  "decisions_made": [
+    {
+      "decision": "Disabled ANSI face loading for non-Warp/non-Kitty terminals",
+      "reason": "User wants clean powerline segments, not pixel art"
+    },
+    {
+      "decision": "Removed MOOD text from Row 3 output and overlay state",
+      "reason": "Matches desired Warp-style layout"
+    }
+  ]
+}

package/ftm-state/blackboard/experiences/hackathon-pages-site.json

@@ -0,0 +1,26 @@
+{
+  "id": "hackathon-pages-site",
+  "timestamp": "2026-03-23T00:00:00Z",
+  "task_type": "hackathon-prep",
+  "tags": ["github-pages", "hackathon", "static-html", "team-site", "onboarding"],
+  "outcome": "success",
+  "lessons": [
+    "GitHub Pages with build_type workflow needs a .github/workflows/pages.yml to deploy",
+    "When porting design between themes, check for missing nodes/paths/annotations — AI generators often drop elements",
+    "Docx content can be extracted with Python zipfile + xml.etree for comparison against HTML versions"
+  ],
+  "files_touched": [
+    "index.html",
+    "playbook.html",
+    "flow.html",
+    "agent-flow-map.html",
+    "agent-flow.html",
+    ".github/workflows/pages.yml"
+  ],
+  "stakeholders": ["hackathon team"],
+  "decisions_made": [
+    "Static HTML on GitHub Pages — no framework needed for reference pages",
+    "Kept coffee-shop design theme across all pages",
+    "Wired all homepage links to actual pages including Slack and GitHub repo"
+  ]
+}

package/ftm-state/blackboard/experiences/hindsight-sso-kickoff.json

@@ -0,0 +1,42 @@
+{
+  "id": "hindsight-sso-kickoff",
+  "timestamp": "2026-03-20T08:30:00Z",
+  "task_type": "sso-implementation",
+  "tags": ["sso", "saml", "okta", "hindsight", "vendor-unblock", "planning"],
+  "outcome": "in_progress",
+  "description": "Hindsight SSO blocker cleared - Ani provided ACS URL + Entity ID. Fetched vendor docs, confirmed SAML 2.0 setup. Created execution plan. Awaiting user decision on browser automation vs manual Okta setup.",
+  "lessons": [
+    "Hindsight uses Clerk for SAML - ACS URL and Entity ID both under clerk.usehindsight.com domain",
+    "SAML only - no OIDC support for Okta",
+    "Required attributes: mail, firstName, lastName (standard Okta mappings)",
+    "Name ID format: EmailAddress",
+    "Post-config: vendor needs Okta Metadata URL to finalize their side",
+    "No SCIM - user management is manual/Okta groups only",
+    "Approval owner: Mindy Regnell (CI team)",
+    "Multiple permission levels exist but details not yet mapped to Okta groups"
+  ],
+  "files_touched": [
+    "~/.claude/eng-buddy/daily/2026-03-20.md",
+    "~/.claude/eng-buddy/daily/daily-index.md",
+    "~/.claude/ftm-state/blackboard/context.json"
+  ],
+  "stakeholders": {
+    "requester": "Alani Setalsingh",
+    "vendor_poc": "Ani Gottiparthy (Ani@usehindsight.com)",
+    "approval_owner": "Mindy Regnell",
+    "initial_users": ["Mindy.Regnell@klaviyo.com", "mokhsira.kurbonova@klaviyo.com", "anvi.vasa@klaviyo.com"]
+  },
+  "decisions_made": [
+    {
+      "decision": "Confirmed SAML 2.0 app type (not OIDC) based on vendor docs",
+      "reason": "Hindsight/Clerk explicitly does not support OIDC for Okta"
+    },
+    {
+      "decision": "Identified need for Okta groups based on multiple permission levels",
+      "reason": "Ticket states different permission levels exist - need to map before group creation"
+    }
+  ],
+  "jira_key": "ITWORK2-9702",
+  "freshservice_ticket": "321024",
+  "confidence": 0.9
+}

package/ftm-state/blackboard/experiences/index.json

@@ -1,9 +1,58 @@
-{
-  "entries": [],
-  "metadata": {
-    "total_count": 0,
-    "last_updated": null,
-    "max_entries": 200,
-    "pruning_strategy": "remove_oldest_low_confidence"
-  }
-}
+{
+  "entries": [
+    {
+      "id": "nordlayer-members-auto-assign",
+      "file": "nordlayer-members-auto-assign.json",
+      "timestamp": "2026-03-19T11:00:00Z",
+      "task_type": "freshservice-workflow-routing",
+      "outcome": "success",
+      "tags": ["freshservice", "nordlayer", "custom-trigger", "approval-bypass", "lambda"]
+    },
+    {
+      "id": "hindsight-sso-kickoff",
+      "file": "hindsight-sso-kickoff.json",
+      "timestamp": "2026-03-20T08:30:00Z",
+      "task_type": "sso-implementation",
+      "outcome": "in_progress",
+      "tags": ["sso", "saml", "okta", "hindsight", "vendor-unblock", "planning"]
+    },
+    {
+      "id": "learning-ragnarok-api-access",
+      "file": "learning-ragnarok-api-access.json",
+      "timestamp": "2026-03-20T08:40:00Z",
+      "task_type": "environment-knowledge",
+      "outcome": "success",
+      "tags": ["ragnarok", "okta", "api-access", "environment", "learning"]
+    },
+    {
+      "id": "doom-statusline-fix",
+      "file": "doom-statusline-fix.json",
+      "timestamp": "2026-03-22T00:00:00Z",
+      "task_type": "developer-tooling",
+      "outcome": "success",
+      "tags": ["statusline", "doom-hud", "terminal", "claude-code", "ansi"]
+    },
+    {
+      "id": "hackathon-pages-site",
+      "file": "hackathon-pages-site.json",
+      "timestamp": "2026-03-23T00:00:00Z",
+      "task_type": "hackathon-prep",
+      "outcome": "success",
+      "tags": ["github-pages", "hackathon", "static-html", "team-site", "onboarding"]
+    },
+    {
+      "id": "saml2aws-stale-session-fix",
+      "file": "saml2aws-stale-session-fix.json",
+      "timestamp": "2026-03-24T00:00:00Z",
+      "task_type": "troubleshooting",
+      "outcome": "success",
+      "tags": ["saml2aws", "okta", "aws", "browser-provider", "session-cache", "authentication"]
+    }
+  ],
+  "metadata": {
+    "total_count": 6,
+    "last_updated": "2026-03-24T00:00:00Z",
+    "max_entries": 200,
+    "pruning_strategy": "remove_oldest_low_confidence"
+  }
+}