@tgoodington/intuition 11.0.1 → 11.1.0

package/skills/intuition-enuncia-initialize/references/bugs_template.md

@@ -0,0 +1,41 @@
+# Bug Log Template
+
+This file demonstrates the format for logging bugs and their solutions. Keep entries brief and chronological.
+
+## Format
+
+Each bug entry should include:
+- Date (YYYY-MM-DD)
+- Brief description of the bug/issue
+- Solution or fix applied
+- Any prevention notes (optional)
+
+Use bullet lists for simplicity. Older entries can be manually removed when they become irrelevant.
+
+## Example Entries
+
+### 2025-01-15 - Docker Architecture Mismatch
+- **Issue**: Container failing to start with "exec format error"
+- **Root Cause**: Built on ARM64 Mac but deploying to AMD64 Cloud Run
+- **Solution**: Added `--platform linux/amd64` to docker build command
+- **Prevention**: Always specify platform in Dockerfile and build scripts
+
+### 2025-01-20 - Cloud Scheduler HTTPS Requirement
+- **Issue**: Cloud Scheduler jobs failing with "URL must use HTTPS"
+- **Root Cause**: Forgot Cloud Run URLs require HTTPS by default
+- **Solution**: Updated all scheduler job URLs from http:// to https://
+- **Prevention**: Remember GCP services enforce HTTPS; check URLs in infrastructure code
+
+### 2025-01-22 - Database Connection Pool Exhaustion
+- **Issue**: API returning 500 errors under load
+- **Root Cause**: Connection pool size too small (default 5)
+- **Solution**: Increased pool_size to 20 and max_overflow to 10 in SQLAlchemy config
+- **Prevention**: Load test APIs before production deployment
+
+## Tips
+
+- Keep descriptions under 2-3 lines
+- Focus on what was learned, not exhaustive details
+- Include enough context for future reference
+- Date entries so you know how recent the issue is
+- Periodically clean out very old entries (6+ months)

package/skills/intuition-enuncia-initialize/references/claude_template.md

@@ -0,0 +1,33 @@
+## Project Workflow and Memory System
+
+This project uses the Enuncia pipeline (`@tgoodington/intuition`). Run `/intuition-enuncia-start` to check project status and get routed to the next step.
+
+### Memory Files
+
+Project memory is maintained in `docs/project_notes/` for consistency across sessions:
+
+- **bugs.md** — Bug log with dates, solutions, and prevention notes
+- **decisions.md** — Architectural Decision Records (ADRs) with context and trade-offs
+- **key_facts.md** — Project configuration, credentials, ports, important URLs
+- **issues.md** — Work log with ticket IDs, descriptions, and URLs
+- **project_map.md** — Living architecture document, updated as the project evolves
+
+### Memory-Aware Protocols
+
+**Before proposing architectural changes:**
+- Check `docs/project_notes/decisions.md` for existing decisions
+- Verify the proposed approach doesn't conflict with past choices
+- If it does conflict, acknowledge the existing decision and explain why a change is warranted
+
+**When encountering errors or bugs:**
+- Search `docs/project_notes/bugs.md` for similar issues
+- Apply known solutions if found
+- Document new bugs and solutions when resolved
+
+**When looking up project configuration:**
+- Check `docs/project_notes/key_facts.md` for credentials, ports, URLs, service accounts
+- Prefer documented facts over assumptions
+
+**When completing work on tickets:**
+- Log completed work in `docs/project_notes/issues.md`
+- Include ticket ID, date, brief description, and URL

package/skills/intuition-enuncia-initialize/references/decisions_template.md

@@ -0,0 +1,92 @@
+# Architectural Decisions Template
+
+This file demonstrates the format for logging architectural decisions (ADRs). Use bullet lists for clarity.
+
+## Format
+
+Each decision should include:
+- Date and ADR number
+- Context (why the decision was needed)
+- Decision (what was chosen)
+- Alternatives considered
+- Consequences (trade-offs, implications)
+
+## Example Entries
+
+### ADR-001: Use Workload Identity Federation for GitHub Actions (2025-01-10)
+
+**Context:**
+- Need secure authentication from GitHub Actions to GCP
+- Service account keys are deprecated and considered insecure
+- Want to avoid managing long-lived credentials
+
+**Decision:**
+- Use Workload Identity Federation (WIF) for GitHub Actions authentication
+- Configure via `WIF_PROVIDER` and `WIF_SERVICE_ACCOUNT` secrets
+
+**Alternatives Considered:**
+- Service account JSON keys → Rejected: security risk, manual rotation required
+- Environment-specific credentials → Rejected: harder to manage across repos
+
+**Consequences:**
+- ✅ More secure (no long-lived credentials)
+- ✅ Automatic credential rotation
+- ✅ Better audit trail
+- ❌ Slightly more complex initial setup
+- ❌ Requires GitHub OIDC support
+
+### ADR-002: Use Alembic for Database Migrations (2025-01-12)
+
+**Context:**
+- Need version control for database schema changes
+- Multiple developers working on database schema
+- Want to avoid manual SQL scripts and migration conflicts
+
+**Decision:**
+- Use Alembic as the database migration tool
+- Store migrations in `alembic/versions/` directory
+- Use auto-generate feature for model changes
+
+**Alternatives Considered:**
+- Raw SQL scripts → Rejected: no versioning, error-prone
+- Flask-Migrate → Rejected: too tied to Flask framework
+- Django migrations → Rejected: using FastAPI, not Django
+
+**Consequences:**
+- ✅ Version-controlled schema changes
+- ✅ Automatic migration generation from models
+- ✅ Easy rollback capability
+- ❌ Learning curve for team
+- ❌ Must remember to generate migrations after model changes
+
+### ADR-003: Use AlloyDB Instead of Cloud SQL (2025-01-15)
+
+**Context:**
+- Need PostgreSQL-compatible database in GCP
+- Require high availability and automatic backups
+- Performance-critical application with complex queries
+
+**Decision:**
+- Use AlloyDB for PostgreSQL instead of Cloud SQL
+- Configure with automated backups and point-in-time recovery
+
+**Alternatives Considered:**
+- Cloud SQL PostgreSQL → Rejected: slower query performance
+- Self-managed PostgreSQL on GCE → Rejected: high operational overhead
+- Firestore → Rejected: need relational data model and SQL
+
+**Consequences:**
+- ✅ Better query performance (2-4x faster than Cloud SQL)
+- ✅ PostgreSQL compatibility
+- ✅ Managed service (automated backups, HA)
+- ❌ Higher cost than Cloud SQL
+- ❌ Newer service, less community documentation
+
+## Tips
+
+- Number decisions sequentially (ADR-001, ADR-002, etc.)
+- Always include date for context
+- Be honest about trade-offs (use ✅ and ❌)
+- Keep alternatives brief but clear
+- Update decisions if they're revisited/changed
+- Focus on "why" not "how" (implementation details go elsewhere)

package/skills/intuition-enuncia-initialize/references/intuition_readme_template.md

@@ -0,0 +1,50 @@
+# Intuition (Enuncia Pipeline)
+
+A discovery-driven workflow system for Claude Code. Transforms project visions into structured deliverables through foundational discovery, experience-slice decomposition, technical design, and verified implementation.
+
+## Workflow
+
+```
+/intuition-enuncia-discovery → /intuition-enuncia-compose → /intuition-enuncia-design →
+  /intuition-enuncia-execute → /intuition-enuncia-verify → complete
+        ↓
+  /intuition-enuncia-start → create branch or /intuition-debugger
+```
+
+Run `/clear` before each phase skill to keep context clean.
+
+The first cycle is the **trunk**. After trunk completes, create **branches** for new features or changes.
+
+## Skills
+
+| Skill | What it does |
+|-------|-------------|
+| `/intuition-enuncia-start` | Detects where you left off, routes to next step |
+| `/intuition-enuncia-discovery` | Foundational project discovery — Who, Where, What, Why |
+| `/intuition-enuncia-compose` | Maps experience slices, decomposes into buildable tasks |
+| `/intuition-enuncia-design` | Technical design — enriches tasks with specs, updates project map |
+| `/intuition-enuncia-execute` | Delegates production to subagents, verifies outputs |
+| `/intuition-enuncia-verify` | Wires code into project, runs toolchain and tests |
+| `/intuition-enuncia-handoff` | Branch creation and context management |
+| `/intuition-initialize` | Sets up project memory (you already ran this) |
+| `/intuition-meander` | Thought partner — reason through problems collaboratively |
+| `/intuition-think-tank` | Rapid expert-panel analysis |
+| `/intuition-debugger` | Expert diagnostic and resolution service |
+
+## Quick Start
+
+### First cycle (trunk)
+
+1. `/intuition-enuncia-start` — see where you are
+2. `/intuition-enuncia-discovery` — articulate what you're building and why
+3. `/intuition-enuncia-compose` — decompose into experience slices and tasks
+4. `/intuition-enuncia-design` — technical design for each task group
+5. `/intuition-enuncia-execute` — build from specs
+6. `/intuition-enuncia-verify` — wire in, test, prove it works (code projects)
+
+Run `/clear` before each phase skill.
+
+### After trunk completes
+
+- `/intuition-enuncia-start` — see project status, create a branch, or start fresh
+- `/intuition-debugger` — investigate hard problems

package/skills/intuition-enuncia-initialize/references/issues_template.md

@@ -0,0 +1,76 @@
+# Issues/Work Log Template
+
+This file demonstrates the format for logging work completed on tickets. Keep it simple - just enough to remember what was done. Full details live in Jira/GitHub.
+
+## Format
+
+Each entry should include:
+- Date (YYYY-MM-DD)
+- Ticket ID
+- Brief description (1-2 lines)
+- URL to ticket (if available)
+- Status (optional: completed, in-progress, blocked)
+
+Use bullet lists for simplicity. This is NOT a replacement for your ticket system - it's a quick reference log.
+
+## Example Entries
+
+### 2025-01-15 - PROJ-123: Implement Contact API
+- **Status**: Completed
+- **Description**: Created FastAPI endpoints for contact CRUD operations with validation
+- **URL**: https://jira.company.com/browse/PROJ-123
+- **Notes**: Added unit tests, coverage at 85%
+
+### 2025-01-16 - PROJ-124: Fix Docker Build Issues
+- **Status**: Completed
+- **Description**: Fixed architecture mismatch for Cloud Run deployment
+- **URL**: https://jira.company.com/browse/PROJ-124
+- **Notes**: See bugs.md for details on the fix
+
+### 2025-01-18 - PROJ-125: Database Migration to AlloyDB
+- **Status**: Completed
+- **Description**: Migrated from Cloud SQL to AlloyDB with Pulumi infrastructure code
+- **URL**: https://jira.company.com/browse/PROJ-125
+- **Notes**: Multi-phase migration completed over 3 days
+
+### 2025-01-20 - GH-45: Add OAuth2 Authentication
+- **Status**: In Progress
+- **Description**: Implementing OAuth2 flow with Google provider
+- **URL**: https://github.com/company/repo/issues/45
+- **Notes**: Backend complete, frontend integration pending
+
+### 2025-01-22 - PROJ-130: Performance Optimization
+- **Status**: Blocked
+- **Description**: Optimize slow queries in contact search endpoint
+- **URL**: https://jira.company.com/browse/PROJ-130
+- **Notes**: Waiting for DBA review of proposed indexes
+
+## Alternative Format (Grouped by Week)
+
+### Week of 2025-01-15
+
+**Completed:**
+- PROJ-123: Contact API implementation → https://jira.company.com/browse/PROJ-123
+- PROJ-124: Docker build fix → https://jira.company.com/browse/PROJ-124
+
+**In Progress:**
+- PROJ-125: AlloyDB migration (phase 2 of 3)
+
+### Week of 2025-01-22
+
+**Completed:**
+- PROJ-125: AlloyDB migration completed → https://jira.company.com/browse/PROJ-125
+- GH-45: OAuth2 backend done → https://github.com/company/repo/issues/45
+
+**Blocked:**
+- PROJ-130: Query optimization (waiting on DBA) → https://jira.company.com/browse/PROJ-130
+
+## Tips
+
+- Keep descriptions brief (1-2 lines max)
+- Always include ticket URL for easy reference
+- Update status if work gets blocked or resumed
+- Optional: Group by week or sprint for better organization
+- Don't duplicate ticket details - link to source of truth
+- Clean out very old entries periodically (3+ months)
+- Include both Jira and GitHub tickets as appropriate

package/skills/intuition-enuncia-initialize/references/key_facts_template.md

@@ -0,0 +1,158 @@
+# Key Facts Template
+
+This file demonstrates the format for storing project constants, configuration, and frequently-needed **non-sensitive** information. Organize by category using bullet lists.
+
+## ⚠️ SECURITY WARNING: What NOT to Store Here
+
+**NEVER store passwords, API keys, or sensitive credentials in this file.** This file is typically committed to version control and should only contain non-sensitive reference information.
+
+**❌ NEVER store:**
+- Passwords or passphrases
+- API keys or authentication tokens
+- Service account JSON keys or credentials
+- Database passwords
+- OAuth client secrets
+- Private keys or certificates
+- Session tokens
+- Any secret values from environment variables
+
+**✅ SAFE to store:**
+- Database hostnames, ports, and cluster names
+- Client names and project identifiers
+- JIRA project keys and Confluence space names
+- AWS/GCP account names and profile names
+- API endpoint URLs (public URLs only)
+- Service account email addresses (not the keys!)
+- GCP project IDs and region names
+- Docker registry names
+- Environment names and deployment targets
+
+**Where to store secrets:**
+- `.env` files (excluded via `.gitignore`)
+- Password managers (1Password, LastPass, Bitwarden)
+- Secrets managers (AWS Secrets Manager, GCP Secret Manager, HashiCorp Vault)
+- CI/CD environment variables (GitHub Secrets, GitLab Variables)
+- Platform credential stores (Kubernetes Secrets, Cloud Run)
+
+## Format
+
+Organize information into logical categories:
+- GCP/Cloud configuration
+- Database connection details (hostnames, ports, cluster names)
+- API endpoints (URLs only, not credentials)
+- Local development setup (ports, service names)
+- Important URLs
+- Service accounts and permissions (emails and roles, not keys)
+
+Use bullet lists for simplicity and easy scanning.
+
+## Example Structure
+
+### GCP Project Information
+
+**Current Project:**
+- Project ID: `my-company-prod`
+- Project Number: `123456789012`
+- Region: `us-central1`
+- Zone: `us-central1-a`
+
+**Old Project (Deprecated):**
+- Project ID: `my-company-dev-old`
+- Migration Date: 2025-01-10
+- Status: Archived, do not use
+
+### Database Configuration
+
+**AlloyDB Cluster:**
+- Cluster Name: `prod-cluster`
+- Instance Name: `prod-primary`
+- Region: `us-central1`
+- Private IP: `10.0.0.5`
+- Port: `5432`
+- Database Name: `contacts`
+
+**Connection:**
+- Use AlloyDB Auth Proxy for local development
+- Proxy command: `./alloydb-auth-proxy "projects/my-company-prod/locations/us-central1/clusters/prod-cluster/instances/prod-primary"`
+- Local port: `5432`
+
+**Authentication:**
+- Service Account (email only): `alloydb-client@my-company-prod.iam.gserviceaccount.com`
+- Service Account Key: Stored in `.env` as `GOOGLE_APPLICATION_CREDENTIALS` (not in git!)
+- Connection String Template: `postgresql://user:${DB_PASSWORD}@localhost:5432/contacts`
+- Password Location: Stored in `.env` file (excluded via `.gitignore`)
+
+### API Configuration
+
+**Backend API:**
+- Production URL: `https://api.mycompany.com`
+- Staging URL: `https://api-staging.mycompany.com`
+- Local Development: `http://localhost:8000`
+
+**Authentication:**
+- OAuth Client ID (public): `123456789-abcdefg.apps.googleusercontent.com`
+- OAuth Client Secret: Stored in GCP Secret Manager as `oauth-client-secret` (not in git!)
+- Local Development Secret: Stored in `.env` as `OAUTH_CLIENT_SECRET` (not in git!)
+- Scopes: `openid email profile`
+
+### Local Development Ports
+
+**Services:**
+- Backend API: `8000`
+- Frontend: `3000`
+- AlloyDB Proxy: `5432`
+- Redis: `6379`
+- Prometheus: `9090`
+
+### Service Accounts
+
+**GitHub Actions:**
+- Service Account: `github-actions@my-company-prod.iam.gserviceaccount.com`
+- Roles: `roles/run.admin`, `roles/secretmanager.secretAccessor`
+- WIF Pool: `projects/123456789012/locations/global/workloadIdentityPools/github-pool`
+
+**Cloud Run Service:**
+- Service Account: `cloud-run-sa@my-company-prod.iam.gserviceaccount.com`
+- Roles: `roles/alloydb.client`, `roles/secretmanager.secretAccessor`
+
+### Important URLs
+
+**Documentation:**
+- API Docs: `https://docs.mycompany.com/api`
+- Internal Wiki: `https://wiki.mycompany.com`
+- Runbook: `https://wiki.mycompany.com/runbook`
+
+**Monitoring:**
+- Cloud Console: `https://console.cloud.google.com/home/dashboard?project=my-company-prod`
+- Logs: `https://console.cloud.google.com/logs?project=my-company-prod`
+- Monitoring: `https://console.cloud.google.com/monitoring?project=my-company-prod`
+
+**Deployment:**
+- Cloud Run Service: `https://console.cloud.google.com/run?project=my-company-prod`
+- Cloud Build: `https://console.cloud.google.com/cloud-build?project=my-company-prod`
+- Artifact Registry: `https://console.cloud.google.com/artifacts?project=my-company-prod`
+
+### Infrastructure as Code
+
+**Pulumi:**
+- Stack: `prod`
+- Backend: `gs://my-company-pulumi-state`
+- Config Passphrase: Stored in team password manager (1Password vault: "Infrastructure")
+- State: Stored in GCS bucket with versioning enabled
+- Note: Never commit `Pulumi.prod.yaml` with unencrypted secrets
+
+**Configuration:**
+- Cloud Run Image: `us-central1-docker.pkg.dev/my-company-prod/app/backend:latest`
+- VPC Connector: `prod-vpc-connector`
+- Max Instances: `10`
+- Min Instances: `1`
+
+## Tips
+
+- Keep entries current (update when things change)
+- Remove deprecated information after migration is complete
+- Include both production and development details
+- Add URLs to make navigation easier
+- Use consistent formatting (same structure for similar items)
+- Group related information together
+- Mark deprecated items clearly with dates

package/skills/intuition-enuncia-initialize/references/project_map_template.md

@@ -0,0 +1,17 @@
+# Project Map
+
+## Overview
+[Filled by compose — what this project is, who it's for, how it's delivered]
+
+## Components
+[Filled by compose — components identified during task decomposition]
+
+## Component Interactions
+[Filled by compose — how components connect]
+
+## What Exists vs What's New
+[Filled by compose — existing, new, and modified items]
+
+## Map History
+| Date | Phase | Change | Reason |
+|------|-------|--------|--------|

package/skills/intuition-enuncia-initialize/references/settings_template.json

@@ -0,0 +1,19 @@
+{
+  "permissions": {
+    "allow": [
+      "WebSearch",
+      "WebFetch",
+      "Task",
+      "Read",
+      "Glob",
+      "Grep",
+      "Bash(grep:*)",
+      "Bash(git status)",
+      "Bash(git diff:*)",
+      "Bash(git add:*)",
+      "Bash(git commit:*)",
+      "Bash(git push:*)",
+      "Bash(git log:*)"
+    ]
+  }
+}

package/skills/intuition-enuncia-initialize/references/state_template.json

@@ -0,0 +1,39 @@
+{
+  "initialized": true,
+  "version": "11.0",
+  "pipeline": "enuncia",
+  "active_context": "trunk",
+  "trunk": {
+    "status": "none",
+    "workflow": {
+      "discovery": {
+        "started": false,
+        "completed": false,
+        "completed_at": null
+      },
+      "compose": {
+        "started": false,
+        "completed": false,
+        "completed_at": null
+      },
+      "design": {
+        "started": false,
+        "completed": false,
+        "completed_at": null
+      },
+      "execute": {
+        "started": false,
+        "completed": false,
+        "completed_at": null
+      },
+      "verify": {
+        "started": false,
+        "completed": false,
+        "completed_at": null
+      }
+    }
+  },
+  "branches": {},
+  "last_handoff": null,
+  "last_handoff_transition": null
+}

package/skills/intuition-enuncia-initialize/references/user_profile_template.json

@@ -0,0 +1,70 @@
+{
+  "_comment": "This file is created in .claude/USER_PROFILE.json and persists across all projects for this user. It captures personal/professional context that follows the user, not project-specific information. Agents naturally discover and update this through conversation. This is NOT project memory—it's user memory.",
+
+  "user": {
+    "name": null,
+    "role": null,
+    "seniority_level": null,
+    "years_experience": null,
+    "organization": {
+      "name": null,
+      "type": null,
+      "industry": null,
+      "location": null
+    },
+    "reports_to": null,
+    "discovery_notes": []
+  },
+
+  "expertise": {
+    "primary_skills": [],
+    "expertise_areas": [],
+    "learning_style": null,
+    "learning_goals": []
+  },
+
+  "communication": {
+    "style": null,
+    "pace": null,
+    "detail_level": null,
+    "decision_making": null
+  },
+
+  "constraints": {
+    "authority_level": null,
+    "typical_availability": null,
+    "team_size": null,
+    "time_zone": null,
+    "technical_environment": {
+      "cloud_providers": [],
+      "preferred_databases": [],
+      "deployment_patterns": []
+    }
+  },
+
+  "motivation": {
+    "primary_drives": [],
+    "cares_about": [],
+    "professional_goals": []
+  },
+
+  "preferences": {
+    "tools_and_frameworks": [],
+    "methodologies": [],
+    "collaboration_tools": []
+  },
+
+  "metadata": {
+    "created_at": "2025-02-04T00:00:00Z",
+    "last_updated": null,
+    "profile_completeness": 0,
+    "source": "Discovered through agent conversations",
+    "projects_contributed_to": [],
+    "confidence_scores": {
+      "role": 0.0,
+      "expertise_areas": 0.0,
+      "communication_style": 0.0,
+      "motivation": 0.0
+    }
+  }
+}

package/skills/intuition-enuncia-start/SKILL.md

@@ -143,7 +143,7 @@ Use AskUserQuestion:
 ## EDGE CASES
 
 - **State exists but active_context references missing branch**: Report inconsistency, suggest `/intuition-enuncia-handoff`.
-- **Workflow fields missing** (partial state): Infer from files — discovery_brief.md means discovery done, outline.json means compose done, specs/ means design done, build_output.json means execute done.
+- **Workflow fields missing** (partial state): Infer from files — discovery_brief.md means discovery done, tasks.json without design fields means compose done, tasks.json with design fields means design done, build_output.json means execute done.
 - **Legacy v8/v9/v10 project**: Detect by checking `state.pipeline` or absence of enuncia workflow fields. Route to `/intuition-start` for the classic pipeline.
 
 ## VOICE