@tgoodington/intuition 11.0.1 → 11.2.0

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

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

@@ -21,13 +21,13 @@ The discovery brief's North Star is the ultimate test: does the running system d
 ## CRITICAL RULES
 
 1. You MUST read `.project-memory-state.json` and resolve context_path before anything else.
-2. You MUST read `{context_path}/discovery_brief.md`, `{context_path}/outline.json`, `{context_path}/build_output.json`, and `{context_path}/project_map.md`.
+2. You MUST read `{context_path}/discovery_brief.md`, `{context_path}/tasks.json`, `{context_path}/build_output.json`, and `docs/project_notes/project_map.md`.
 3. You MUST integrate before testing. Code that isn't wired in can't be meaningfully tested.
 4. You MUST NOT write unit tests that test implementation internals. Tests exercise the system from the outside — smoke tests and experience-slice tests only.
 5. You MUST NOT fix failures that violate user decisions from the specs. Escalate immediately.
 6. You MUST delegate integration tasks and test writing to subagents. Do not write code yourself.
 7. You MUST verify against the discovery brief after all tests pass — does the system deliver the North Star?
-8. You MUST update `{context_path}/project_map.md` if integration reveals new information.
+8. You MUST update `docs/project_notes/project_map.md` if integration reveals new information.
 
 ## CONTEXT PATH RESOLUTION
 
@@ -58,14 +58,13 @@ Step 8: Exit
 
 Read these files:
 1. `{context_path}/discovery_brief.md` — North Star, stakeholders, constraints
-2. `{context_path}/outline.json` — experience slices, tasks, acceptance criteria
+2. `{context_path}/tasks.json` — experience slices, tasks with design enrichment, acceptance criteria
 3. `{context_path}/build_output.json` — what was built, files created/modified, any deviations
-4. `{context_path}/specs/*.md` — design specs for technical context
-5. `{context_path}/project_map.md` — component landscape, interactions
+4. `docs/project_notes/project_map.md` — component landscape, interactions
 
 From build_output.json, extract: all files created and modified, task statuses, any escalated issues or deviations.
 
-From outline.json, extract: experience slices (these become the basis for experience-slice tests).
+From tasks.json, extract: experience slices (these become the basis for experience-slice tests).
 
 ### Gate Check
 
@@ -162,7 +161,7 @@ These are the highest-value tests in the system. They walk through each stakehol
 
 ### Deriving Tests from Experience Slices
 
-Read `outline.json` and extract the experience slices. For each slice that involves code behavior:
+Read `tasks.json` and extract the experience slices. For each slice that involves code behavior:
 
 - **What triggers it**: The test setup
 - **What the stakeholder does**: The test actions
@@ -185,7 +184,7 @@ Test conventions: [from existing tests]
 ### ES-[N]: [Title]
 Stakeholder: [who]
 Journey: [trigger → action → expected outcome]
-Acceptance criteria: [from outline.json]
+Acceptance criteria: [from tasks.json]
 
 ## Rules
 - Test the journey from the stakeholder's perspective
@@ -198,8 +197,7 @@ Acceptance criteria: [from outline.json]
 
 ## Spec Sources (read these for expected behavior)
 - Discovery brief: {context_path}/discovery_brief.md
-- Outline: {context_path}/outline.json
-- Specs: {context_path}/specs/*.md
+- Tasks: {context_path}/tasks.json
 ```
 
 Run the experience slice tests. Classify and fix failures (Step 6).
@@ -237,7 +235,7 @@ After all tests pass, check the running system against the discovery brief:
 
 If something drifts, flag it to the user: "Tests pass, but [specific concern about North Star alignment]."
 
-**Update project map** if integration or testing revealed anything new about how components connect.
+**Update `docs/project_notes/project_map.md`** if integration or testing revealed anything new about how components connect.
 
 ## STEP 8: EXIT
 
@@ -275,7 +273,7 @@ If committing: stage files from build output + integration changes + tests, comm
 When verifying on a branch:
 - Run the FULL test suite (parent + branch tests) to catch compatibility issues
 - Integration must be compatible with parent architecture
-- Update the branch's project map, not the parent's
+- Update `docs/project_notes/project_map.md`
 
 ## RESUME LOGIC