@tgoodington/intuition 8.1.2 → 8.1.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tgoodington/intuition",
-  "version": "8.1.2",
+  "version": "8.1.3",
   "description": "Trunk-and-branch workflow system for Claude Code: prompt, plan, design, engineer, build with iterative branching. Code spec creation, domain-agnostic design exploration with ECD framework, and file-based handoffs through project memory.",
   "keywords": [
     "claude-code",

package/skills/intuition-initialize/references/design_brief_template.md

@@ -1,64 +0,0 @@
-# Design Brief Template
-
-> **Path note:** `{context_path}` resolves to `docs/project_notes/trunk/` for the trunk context, or `docs/project_notes/branches/{name}/` for a branch context. Shared files (`key_facts.md`, `decisions.md`, `issues.md`, `bugs.md`) always remain at `docs/project_notes/`.
-
-> **Generated by:** `/intuition-handoff` (Planning→Design transition, updated per design item)
-> **Consumed by:** `/intuition-design`
-> **Overwritten for:** each design item in the loop
-
----
-
-## Current Item
-
-**[Item Name]** — [Brief description from plan]
-
----
-
-## Plan Context
-
-[1-2 paragraph summary of what the plan says about this item]
-
----
-
-## Task Details
-
-- **Plan Tasks**: [Task numbers from plan.md]
-- **Description**: [From plan.md]
-- **Acceptance Criteria**: [From plan.md]
-- **Dependencies**: [From plan.md]
-
----
-
-## Design Rationale
-
-[Why plan flagged this for design — what needs elaboration before execution can proceed]
-
----
-
-## Prior Design Context
-
-[If this is not the first design item: 1-2 sentences about what was designed in previous items that may be relevant. If first item, omit this section.]
-
----
-
-## Constraints
-
-- [From plan's architectural decisions]
-- [From discovery constraints]
-- [From prior design decisions, if any]
-
----
-
-## Design Queue
-
-- [x] Item 1 (completed) -> design_spec_item_1.md
-- **Item 2 (current)**
-- [ ] Item 3 (pending)
-
----
-
-## References
-
-- Plan: `{context_path}/plan.md`
-- Discovery: `{context_path}/discovery_brief.md`
-- Prior design specs: [list completed spec files, if any]

package/skills/intuition-initialize/references/discovery_output_template.json

@@ -1,19 +0,0 @@
-{
-  "_comment": "Discovery output template - structured analysis from Waldo's discovery dialogue",
-  "_description": "This template defines the shape of discovery_output.json, generated by /intuition-discovery and consumed by /intuition-handoff. It captures key findings, assumptions, constraints, and decisions that inform planning.",
-
-  "key_facts_to_add": [],
-  "_key_facts_to_add_description": "Array of important facts discovered. Each entry: { category (string), fact (string), source (string) }. Example: { \"category\": \"Architecture\", \"fact\": \"API uses GraphQL\", \"source\": \"codebase review\" }",
-
-  "assumptions": [],
-  "_assumptions_description": "Array of assumptions made during discovery. Each entry: { statement (string), confidence (string: 'high'/'medium'/'low'), source (string) }. Example: { \"statement\": \"Users expect real-time updates\", \"confidence\": \"medium\", \"source\": \"user interviews\" }",
-
-  "new_constraints": [],
-  "_new_constraints_description": "Array of constraints or limitations discovered. Each entry: { constraint (string), impact (string), source (string) }. Example: { \"constraint\": \"Legacy database schema is immutable\", \"impact\": \"Must use adapter pattern\", \"source\": \"technical audit\" }",
-
-  "suggested_decisions": [],
-  "_suggested_decisions_description": "Array of strategic decisions Waldo recommends for planning. Each entry: { topic (string), recommendation (string), rationale (string) }. Example: { \"topic\": \"State Management\", \"recommendation\": \"Use Redux\", \"rationale\": \"Existing patterns in codebase\" }",
-
-  "follow_up_for_planning": [],
-  "_follow_up_for_planning_description": "Array of topics that planning should investigate further. Each entry: { topic (string), priority (string: 'high'/'medium'/'low'), context (string) }. Example: { \"topic\": \"Performance bottlenecks\", \"priority\": \"high\", \"context\": \"Mobile users experiencing slow load times\" }"
-}

package/skills/intuition-initialize/references/execution_brief_template.md

@@ -1,160 +0,0 @@
-# Engineering Brief Template
-
-> **Path note:** `{context_path}` resolves to `docs/project_notes/trunk/` for the trunk context, or `docs/project_notes/branches/{name}/` for a branch context. Shared files (`key_facts.md`, `decisions.md`, `issues.md`, `bugs.md`) always remain at `docs/project_notes/`.
-
-> **Generated by:** `/intuition-handoff` (Design→Engineer or Planning→Engineer transition)
-> **Consumed by:** `/intuition-engineer`
-> **Frozen for:** engineering phase (don't modify during engineering)
-
----
-
-## Plan Title
-
-**[One-line summary of what will be implemented]**
-
----
-
-## Plan Summary
-
-**Overview:** [2-3 sentence summary of what the plan accomplishes]
-
-**Scope:** [What's included and excluded from this plan]
-
-**Key changes:**
-- Change 1
-- Change 2
-- Change 3
-
----
-
-## Objective
-
-**What will be different after execution:** [Concrete outcome]
-
-**Measurable impact:** [How success is measured]
-
----
-
-## Discovery Context
-
-**Problem solved:** [Reference the original problem from discovery]
-
-**User value:** [What users gain]
-
-**Technical rationale:** [Why this approach was chosen]
-
----
-
-## Design Specifications
-
-[List all design specs produced during the design phase, if any:]
-- `design_spec_[item1].md` — [One-line summary]
-- `design_spec_[item2].md` — [One-line summary]
-
-**IMPORTANT:** Execute agents MUST read these specs before implementing flagged tasks. Implement exactly what's specified. If ambiguity is found, escalate to user — do not make design decisions autonomously.
-
-[If no design phase was run, omit this section.]
-
----
-
-## Plan Overview
-
-**Architecture approach:** [High-level design strategy]
-
-**Implementation phases:**
-1. Phase 1: [Major milestone]
-2. Phase 2: [Major milestone]
-3. Phase 3: [Major milestone]
-
-**Key dependencies:** [What must happen before what]
-
----
-
-## Task Summary
-
-**Total tasks:** [Number]
-
-**Task categories:**
-- Infrastructure/Setup: [Count]
-- Feature Implementation: [Count]
-- Testing: [Count]
-- Documentation: [Count]
-
-[Mark which tasks have associated design specs]
-
----
-
-## Acceptance Criteria
-
-**Functional requirements met:**
-- [ ] Requirement 1
-- [ ] Requirement 2
-- [ ] Requirement 3
-
-**Non-functional requirements:**
-- [ ] Performance target 1
-- [ ] Reliability target 1
-- [ ] Maintainability target 1
-
-**Testing complete:**
-- [ ] Unit tests pass
-- [ ] Integration tests pass
-- [ ] Manual testing verified
-
----
-
-## Quality Gates
-
-**Code quality:**
-- [ ] No linting errors
-- [ ] Test coverage > [X%]
-- [ ] No console errors in target environments
-
-**Documentation:**
-- [ ] Code comments added for non-obvious logic
-- [ ] README updated
-- [ ] Related docs updated
-
-**Deployment readiness:**
-- [ ] Backwards compatibility verified (or migration plan documented)
-- [ ] Performance verified
-- [ ] Error handling tested
-
----
-
-## Known Risks
-
-**Risk 1:** [Description]
-- Likelihood: [high/medium/low]
-- Impact: [high/medium/low]
-- Mitigation: [What will be done]
-
-**Risk 2:** [Description]
-- Likelihood: [high/medium/low]
-- Impact: [high/medium/low]
-- Mitigation: [What will be done]
-
----
-
-## Architectural Decisions
-
-**Decision 1:** [What was decided]
-- Rationale: [Why this choice]
-- Alternatives considered: [What else could have been done]
-- Trade-offs: [What's given up]
-
----
-
-## References
-
-- Plan file: `{context_path}/plan.md`
-- Planning brief: `{context_path}/planning_brief.md`
-- Design specs: `{context_path}/design_spec_*.md`
-- State file: `docs/project_notes/.project-memory-state.json`
-- Related docs: [Links to relevant documentation]
-
----
-
-## Notes for Executor
-
-[Any guidance for execution — context about approach, team norms, debugging strategies, or gotchas to watch for]

package/skills/intuition-initialize/references/planning_brief_template.md

@@ -1,101 +0,0 @@
-# Planning Brief Template
-
-> **Path note:** `{context_path}` resolves to `docs/project_notes/trunk/` for the trunk context, or `docs/project_notes/branches/{name}/` for a branch context. Shared files (`key_facts.md`, `decisions.md`, `issues.md`, `bugs.md`) always remain at `docs/project_notes/`.
-
-> **Generated by:** `/intuition-handoff` (Prompt→Planning transition)
-> **Consumed by:** `/intuition-plan`
-> **Frozen for:** planning phase (don't modify during plan approval or execution)
-
----
-
-## Problem Title
-
-**[One-line problem statement]**
-
----
-
-## Discovery Summary
-
-**Key findings from prompt refinement:**
-- Fact 1
-- Fact 2
-- Fact 3
-
-**Assumptions made:**
-- Assumption 1 (confidence: high/medium/low)
-- Assumption 2 (confidence: high/medium/low)
-
----
-
-## Problem Statement
-
-**Context:** [Background and how we got here]
-
-**The problem:** [Clear, specific description of what needs to be solved]
-
-**Why it matters:** [Business or technical impact]
-
----
-
-## Goals & Success Criteria
-
-**Primary goal:** [What success looks like]
-
-**Success criteria:**
-- [ ] Criterion 1 (measurable)
-- [ ] Criterion 2 (measurable)
-- [ ] Criterion 3 (measurable)
-
----
-
-## User Context
-
-**Affected users:** [Who is impacted]
-
-**User needs:** [What users expect or require]
-
-**Current experience:** [How it works now, what's broken]
-
----
-
-## Key Constraints
-
-- **Constraint 1:** [Description and impact]
-- **Constraint 2:** [Description and impact]
-- **Constraint 3:** [Description and impact]
-
----
-
-## Architectural Context
-
-**Current architecture:** [Relevant systems, patterns, technologies]
-
-**Integration points:** [Where this connects to existing code]
-
-**Technology stack:** [Relevant languages, frameworks, libraries]
-
----
-
-## Assumptions & Risks
-
-**Key assumptions:**
-- Assumption 1 (confidence level)
-- Assumption 2 (confidence level)
-
-**Known risks:**
-- Risk 1: [Description, likelihood, impact]
-- Risk 2: [Description, likelihood, impact]
-
----
-
-## References
-
-- Discovery output: `{context_path}/discovery_output.json`
-- Discovery brief: `{context_path}/discovery_brief.md`
-- Related docs: [Links to relevant documentation]
-
----
-
-## Notes for Planner
-
-[Any guidance for the planning phase when approaching this problem - context that shapes how the plan should be structured]

package/skills/intuition-initialize/references/project_plan_template.md

@@ -1,151 +0,0 @@
-# Project Plan Template
-
-This file demonstrates the format for creating a comprehensive project plan. Use this template during first-time activation to collaboratively build a shared understanding of the project with the user.
-
-## Format
-
-A project plan should include:
-- Metadata (creation date, current status)
-- Project overview (brief description of what you're building)
-- Goals (primary objectives)
-- Current phase (where you are in the development lifecycle)
-- Architecture overview (high-level technical approach)
-- Completed milestones (what's been done)
-- Next steps (actionable items)
-- Open questions (unresolved decisions)
-- Notes (additional context)
-
-## Example Structure
-
----
-
-# Project Plan: [Project Name]
-
-**Created:** 2025-01-15
-**Last Updated:** 2025-01-20
-**Status:** Planning / In Implementation / Complete
-
-## Project Overview
-
-[2-3 sentence description of what you're building and why]
-
-**Example:**
-Building a contact management API using FastAPI and AlloyDB on GCP. The API will provide CRUD operations for contacts with authentication and will be deployed to Cloud Run with CI/CD via GitHub Actions.
-
-## Goals
-
-[Primary objectives for this project - what success looks like]
-
-**Example:**
-- Create a production-ready REST API for contact management
-- Implement secure authentication and authorization
-- Deploy to GCP Cloud Run with automated CI/CD
-- Achieve <100ms response time for read operations
-- Support 1000+ concurrent users
-
-## Current Phase
-
-[Where you are in the development lifecycle]
-
-**Possible phases:**
-- Discovery / Planning
-- Initial Setup / Scaffolding
-- MVP Development
-- Feature Enhancement
-- Testing & Refinement
-- Production Deployment
-- Maintenance & Support
-
-**Example:**
-MVP Development - Core CRUD operations implemented, working on authentication integration.
-
-## Architecture Overview
-
-[High-level technical approach - key technologies and how they fit together]
-
-**Example:**
-- **Backend:** FastAPI (Python 3.11) with Pydantic validation
-- **Database:** AlloyDB for PostgreSQL with Alembic migrations
-- **Authentication:** OAuth 2.0 with Google Sign-In
-- **Deployment:** Cloud Run (containerized with Docker)
-- **CI/CD:** GitHub Actions with Workload Identity Federation
-- **Infrastructure:** Pulumi for IaC
-- **Monitoring:** Cloud Logging and Cloud Monitoring
-
-## Completed Milestones
-
-[What's been accomplished so far - include dates for context]
-
-**Example:**
-- **2025-01-10:** Initial project setup and repository creation
-  - Created FastAPI project structure
-  - Set up development environment with Poetry
-  - Configured pre-commit hooks and linting
-
-- **2025-01-12:** Database setup completed
-  - Provisioned AlloyDB cluster in GCP
-  - Implemented Alembic migrations
-  - Created Contact model with SQLAlchemy
-
-- **2025-01-15:** Core CRUD operations implemented
-  - Added POST /contacts endpoint
-  - Added GET /contacts and GET /contacts/{id} endpoints
-  - Added PUT and DELETE endpoints
-  - Implemented input validation with Pydantic
-
-## Next Steps
-
-[Actionable checklist items - what needs to be done next]
-
-**Example:**
-- [ ] Implement OAuth 2.0 authentication
-  - [ ] Set up Google OAuth client credentials
-  - [ ] Add authentication middleware to FastAPI
-  - [ ] Protect endpoints with auth decorators
-- [ ] Write unit tests for CRUD operations
-  - [ ] Set up pytest with coverage
-  - [ ] Test happy paths and error cases
-  - [ ] Achieve 80%+ code coverage
-- [ ] Create Dockerfile and container image
-  - [ ] Write optimized multi-stage Dockerfile
-  - [ ] Test local container build
-  - [ ] Push to Artifact Registry
-- [ ] Set up CI/CD pipeline
-  - [ ] Configure GitHub Actions workflow
-  - [ ] Set up Workload Identity Federation
-  - [ ] Automate deployments to Cloud Run
-
-## Open Questions
-
-[Unresolved items that need decisions or clarification]
-
-**Example:**
-- How should we handle rate limiting? (per-user vs. global)
-- Do we need pagination for GET /contacts? What page size?
-- Should we implement soft deletes or hard deletes?
-- What monitoring alerts do we need to set up?
-- Do we need a staging environment or just dev/prod?
-
-## Notes
-
-[Additional context, constraints, or important information]
-
-**Example:**
-- AlloyDB cluster is in `us-central1` - all other resources should use same region
-- OAuth client ID is approved for company domain only
-- Cloud Run quotas: max 10 instances to control costs
-- Database backup retention: 7 days (configured in AlloyDB)
-- Team timezone: PST - schedule deployments accordingly
-
----
-
-## Tips
-
-- Update the plan regularly as the project evolves
-- Move completed next steps to the milestones section with dates
-- Keep the overview concise - details go in other memory files
-- Use open questions to track decisions that need to be made
-- Reference architectural decisions by ADR number (e.g., "See ADR-003")
-- Mark deprecated goals or cancelled features clearly
-- Keep next steps actionable and specific
-- Break large tasks into smaller checklist items