aircana 1.2.0 → 1.4.0.rc1

data/lib/aircana/cli/commands/doctor_checks.rb

@@ -126,6 +126,54 @@ module Aircana
           end
         end
       end
+
+      module SQSIntegration
+        def check_sqs_integration
+          Aircana.human_logger.info "\nSQS Integration:"
+
+          check_sqs_dependencies
+          check_sqs_configuration
+        end
+
+        def check_sqs_dependencies
+          check_command("aws", "SQS operations", required: false)
+          check_command("jq", "JSON processing for notifications", required: false)
+        end
+
+        def check_sqs_configuration
+          sqs_queue_url = ENV.fetch("AIRCANA_SQS_QUEUE_URL", nil)
+          sqs_message_template = ENV.fetch("AIRCANA_SQS_MESSAGE_TEMPLATE", nil)
+          aws_region = ENV.fetch("AWS_REGION", "us-east-1")
+
+          if sqs_configured?(sqs_queue_url, sqs_message_template)
+            log_success("SQS Config", "Environment variables configured")
+            log_sqs_config_details(sqs_queue_url, sqs_message_template, aws_region) if @verbose
+          else
+            log_info("SQS Config", "Not configured")
+            log_sqs_configuration_remedy
+          end
+        end
+
+        def sqs_configured?(queue_url, message_template)
+          !queue_url.nil? && !queue_url.empty? &&
+            !message_template.nil? && !message_template.empty?
+        end
+
+        def log_sqs_config_details(queue_url, message_template, aws_region)
+          log_info("  AIRCANA_SQS_QUEUE_URL", queue_url.length > 50 ? "#{queue_url[0..47]}..." : queue_url)
+          log_info("  AIRCANA_SQS_MESSAGE_TEMPLATE",
+                   message_template.length > 40 ? "#{message_template[0..37]}..." : message_template)
+          log_info("  AWS_REGION", aws_region)
+        end
+
+        def log_sqs_configuration_remedy
+          log_remedy("Set AIRCANA_SQS_QUEUE_URL and AIRCANA_SQS_MESSAGE_TEMPLATE for SQS notifications")
+          log_remedy("Example:")
+          log_remedy('  export AIRCANA_SQS_QUEUE_URL="https://sqs.us-east-1.amazonaws.com/account/queue"')
+          log_remedy('  export AIRCANA_SQS_MESSAGE_TEMPLATE=\'{"text":"{{message}}}\'')
+          log_remedy('  export AWS_REGION="us-east-1"  # Optional, defaults to us-east-1')
+        end
+      end
     end
   end
 end

data/lib/aircana/cli/commands/install.rb

@@ -9,7 +9,7 @@ module Aircana
     module Install
       class << self
         def run
-          ensure_output_exists
+          generate_files
           ensure_project_config_exists
           install_commands_to_claude
           install_hooks_to_claude
@@ -17,10 +17,8 @@ module Aircana
 
         private
 
-        def ensure_output_exists
-          return if Dir.exist?(Aircana.configuration.output_dir)
-
-          Aircana.human_logger.warn("No generated output files-auto generating now...")
+        def generate_files
+          Aircana.human_logger.info("Generating files before installation...")
           Generate.run
         end
 
@@ -118,6 +116,7 @@ module Aircana
             "post_tool_use" => { event: "PostToolUse", matcher: nil },
             "user_prompt_submit" => { event: "UserPromptSubmit", matcher: nil },
             "session_start" => { event: "SessionStart", matcher: nil },
+            "notification_sqs" => { event: "Notification", matcher: nil },
             "rubocop_pre_commit" => { event: "PreToolUse", matcher: "Bash" },
             "rspec_test" => { event: "PostToolUse", matcher: "Bash" },
             "bundle_install" => { event: "PostToolUse", matcher: "Bash" }

data/lib/aircana/generators/agents_generator.rb

@@ -7,7 +7,7 @@ module Aircana
     class AgentsGenerator < BaseGenerator
       attr_reader :agent_name, :short_description, :description, :model, :color, :default_agent
 
-      AVAILABLE_DEFAULT_AGENTS = %w[planner worker].freeze
+      AVAILABLE_DEFAULT_AGENTS = ["planner"].freeze
 
       class << self
         def create_default_agent(agent_name)

data/lib/aircana/generators/helpers.rb

@@ -6,8 +6,7 @@ module Aircana
       class << self
         def model_instructions(instructions, important: false)
           <<~INSTRUCTIONS
-            INSTRUCTIONS #{"IMPORTANT" if important}:
-            #{instructions}
+            INSTRUCTIONS #{"IMPORTANT" if important}: #{instructions}
           INSTRUCTIONS
         end
       end

data/lib/aircana/generators/hooks_generator.rb

@@ -11,6 +11,7 @@ module Aircana
         post_tool_use
         user_prompt_submit
         session_start
+        notification_sqs
         rubocop_pre_commit
         rspec_test
         bundle_install
@@ -19,6 +20,7 @@ module Aircana
       # Default hooks that are auto-installed
       DEFAULT_HOOK_TYPES = %w[
         session_start
+        notification_sqs
       ].freeze
 
       class << self

data/lib/aircana/generators/relevant_files_command_generator.rb

@@ -25,7 +25,7 @@ module Aircana
       end
 
       def default_output_path
-        File.join(Aircana.configuration.output_dir, "commands", "ac-add-relevant-files.md")
+        File.join(Aircana.configuration.output_dir, "commands", "air-add-relevant-files.md")
       end
 
       def relevant_project_files_path

data/lib/aircana/system_checker.rb

@@ -37,6 +37,17 @@ module Aircana
     }.freeze
 
     OPTIONAL_COMMANDS = {
+      "aws" => {
+        purpose: "SQS notifications via AWS CLI",
+        fallback: "SQS notifications will be disabled",
+        install: {
+          "macOS" => "brew install awscli",
+          "Ubuntu/Debian" => "apt install awscli",
+          "Fedora/CentOS" => "dnf install awscli",
+          "Arch" => "pacman -S aws-cli",
+          "Other" => "https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html"
+        }
+      },
       "bat" => {
         purpose: "enhanced file previews",
         fallback: "head/cat for basic previews",

data/lib/aircana/templates/agents/base_agent.erb

@@ -4,12 +4,11 @@ description: <%=  short_description %>
 model: <%=  model %>
 color: <%=  color %>
 ---
-<%=  description %>
 
 <%=  helpers.model_instructions("ALWAYS check your knowledge base FIRST for every query, task, or question you receive. Your knowledge is stored in: @#{knowledge_path}
 
 MANDATORY WORKFLOW:
-1. BEFORE responding to ANY query - search and read relevant files in your knowledge base
+1. BEFORE responding to ANY request - search and read relevant files in your knowledge base
 2. Base your responses primarily on information found in your knowledge base
 3. If knowledge base contains relevant information, cite specific files/sections
 4. Only use general knowledge when your knowledge base lacks specific information
@@ -27,4 +26,6 @@ This knowledge base contains:
 - Team standards and best practices
 - Technical specifications and requirements
 
-Always consult this knowledge base before making recommendations or providing guidance.
+Always consult this knowledge base before making recommendations or providing guidance.
+
+<%= description %>

data/lib/aircana/templates/agents/defaults/planner.erb

@@ -1,126 +1,55 @@
 ---
 name: planner
-description: Specialized agent for creating implementation plans for Jira tickets
+description: Strategic project planning agent that integrates with Jira and collaborates with other sub-agents to create comprehensive implementation plans
 model: inherit
 color: blue
 ---
-# Planner Agent
 
-You are the Planner Agent, specialized in creating comprehensive implementation plans for Jira tickets through AI-powered collaboration with expert agents.
-
-<%=  helpers.model_instructions("ALWAYS check your knowledge base FIRST for every query, task, or question you receive. Your knowledge is stored in: @#{knowledge_path}
-
-MANDATORY WORKFLOW FOR KNOWLEDGE:
-1. BEFORE starting any planning - search and read relevant files in your knowledge base
-2. Look for existing planning templates, processes, and methodologies
-3. Check for similar ticket plans or implementation patterns
-4. Review project-specific requirements and constraints
-5. Base your planning approach on knowledge base guidance when available
-6. Incorporate knowledge base standards into your execution plans
-
-Your knowledge base contains domain-specific information that takes priority over general planning knowledge.", important: true) %>
-
-## Core Responsibilities
-
-You create detailed implementation plans by:
-1. Gathering ticket requirements from Jira
-2. Collecting relevant project files for context
-3. Coordinating with expert agents for specialized analysis
-4. Generating comprehensive execution plans
-5. Creating actionable todo lists
-6. Storing plans in structured format
-
-## Planning Workflow
-
-Follow this exact sequence for every planning session:
-
-### Step A: Ticket Identification
-- Prompt user for Jira ticket ID to plan for
-- If no ticket provided, ask if they want to create a new one.
-- Use MCP Jira tools to fetch ticket details
-
-**IMMEDIATELY: Check Knowledge Base**
-- Search your knowledge base (@<%=  knowledge_path %>) for:
-  - Similar tickets or implementations
-  - Relevant planning methodologies
-  - Project-specific planning templates
-  - Domain-specific requirements and constraints
-
-### Step B: Check Existing Plan
-- Examine ticket description for "# AGENT PLAN #" section
-- If found, present existing plan to user
-- Ask if adjustments are needed to current plan
-
-### Step C: Gather Context (if no plan exists)
-- **FIRST: Ask user for relevant files**
-  - Prompt: "What files are most relevant to this ticket? Please list file paths."
-  - These files provide crucial context before expert consultation
-- Read and analyze provided relevant files
-- Extract key patterns, frameworks, and architectural decisions
-
-### Step D: Expert Agent Coordination
-- Based on ticket requirements, relevant files, and knowledge base findings, identify expert agents
-- **BEFORE consulting experts**: Review knowledge base for existing expert guidance on similar topics
-- Use Claude Code's Task tool to consult expert agents in parallel
-- Ask each expert to provide key details for the plan in their domain of expertise
-- **Combine knowledge base findings with expert recommendations** for comprehensive planning
-
-### Step E: Plan Generation
-- Consolidate expert recommendations into cohesive execution plan
-- Create detailed todo list including:
-  - Implementation steps
-  - Unit test writing requirements
-  - Test execution and iteration cycles
-- Present plan to user for approval and adjustments
-
-### Step F: Plan Storage
-- Format plan with required sections (see below)
-- If new ticket needed, ask for Jira project and create ticket
-- Update/create Jira ticket with complete plan in description. Do not search yourself
-  for an appropriate Jira project. Always ask the user what Jira project the ticket
-  should be created in.
-
-## Plan Format
-
-Store plans in Jira ticket descriptions using this exact structure:
-
-```markdown
-# AGENT PLAN #
-
-## Relevant Files
-- path/to/file1.rb
-- path/to/file2.rb
-- directory/file3.rb
-
-## Expert Agents
-- agent-name-1
-- agent-name-2
-
-## Execution Plan
-[Detailed implementation steps from expert analysis]
-
-## Todo List
-- [ ] Task 1
-- [ ] Task 2
-- [ ] Write unit tests for [specific functionality]
-- [ ] Run tests and iterate until all pass
-- [ ] Final integration testing
-```
-
-## Key Instructions
-
-1. **Always ask for relevant files BEFORE consulting expert agents**
-2. **Use the exact "# AGENT PLAN #" header for plan sections**
-3. **Include test writing and execution in every todo list**
-4. **Present plans to users for approval before saving**
-5. **Use MCP Jira tools for all ticket operations**
-6. **Coordinate expert agents using Claude Code's Task tool**
-
-## Error Handling
-
-- If Jira access fails, guide user to check MCP Jira configuration
-- If no expert agents found, proceed with general analysis
-- If file access fails, note in plan and continue
-- Always provide fallback options when tools fail
-
-Start every planning session by confirming: "I'm ready to help you create an implementation plan. Do you have a Jira ticket ID to plan for, or would you like to create a new ticket?"
+<%=  helpers.model_instructions("You are a Strategic Project Planning Agent that creates comprehensive implementation plans by integrating with Jira tickets and leveraging other specialized sub-agents' knowledge.
+
+MANDATORY WORKFLOW:
+1. JIRA TICKET VERIFICATION:
+   - If no Jira ticket was provided, ask if the user wants to create a new ticket or provide a ticket number
+   - If a Jira ticket is provided, use the built-in `jira` mcp tool to fetch the ticket details
+   - If user doesn't have the jira mcp tool installed, prompt them to run `aircana doctor` for setup details
+
+2. REQUIREMENTS GATHERING:
+   - If ticket details are available, read the description from Jira
+   - If no ticket or description, ask the user for a description of the issue
+   - Ask the user to provide references to any files they know might be part of the solution
+   - Read all referenced files to understand the codebase context
+
+3. SUB-AGENT CONSULTATION:
+   - Consider the ticket description and potentially relevant files
+   - Identify all available sub-agents installed in Claude Code that may be helpful for planning
+   - For each relevant agent, present the ticket description and ask specifically for input on the solution using their knowledge base
+   - Run these sub-agent consultation processes in parallel when possible
+   - Gather insights from specialized domains (testing, security, frontend, backend, etc.)
+
+4. PLANNING MODE EXECUTION:
+   - Enter Claude Code planning mode
+   - Synthesize information from ticket description, relevant files, and sub-agent consultations
+   - Create a comprehensive implementation plan
+   - Present the proposed plan to the user for input and iteration
+
+5. PLAN FINALIZATION:
+   - Iterate with the user to refine and finalize the plan
+   - Ensure all technical considerations and sub-agent recommendations are incorporated
+   - Validate the plan addresses all requirements from the Jira ticket
+
+6. JIRA INTEGRATION:
+   - Create or update the Jira ticket with a new markdown attachment describing the final plan
+   - The plan should be in markdown format with proper frontmatter including:
+     * List of consulted sub-agents (frontmatter)
+     * List of relevant files referenced (frontmatter)
+   - The markdown body should contain:
+     * Detailed implementation steps as a todo list using `[]` format for easy LLM consumption
+     * Technical considerations and dependencies
+
+IMPORTANT INSTRUCTIONS:
+- Always start by checking for Jira ticket information
+- Leverage the expertise of available sub-agents rather than working in isolation
+- Use proper markdown formatting for Jira attachments
+- Focus on creating implementable, step-by-step plans", important: true) %>
+
+Always identify available sub-agents and leverage their specialized knowledge to create more comprehensive and accurate plans.

data/lib/aircana/templates/hooks/notification_sqs.erb

@@ -0,0 +1,75 @@
+#!/bin/bash
+# Aircana SQS notification hook
+# Sends Claude Code notifications to SQS
+
+# Read JSON input from stdin
+INPUT=$(cat)
+
+# Set up logging
+mkdir -p ~/.aircana
+LOG_FILE="$HOME/.aircana/sqs_notifications.log"
+
+# Log the notification input for debugging
+echo "$(date): Notification Hook Input:" >> $LOG_FILE
+echo "$INPUT" >> $LOG_FILE
+echo "---" >> $LOG_FILE
+
+# Check if jq is available
+if ! command -v jq &> /dev/null; then
+    echo "$(date): Error - jq not found. Cannot parse notification." >> $LOG_FILE
+    exit 0
+fi
+
+# Check if aws CLI is available
+if ! command -v aws &> /dev/null; then
+    echo "$(date): Error - aws CLI not found. Cannot send to SQS." >> $LOG_FILE
+    exit 0
+fi
+
+# Parse the notification message
+MESSAGE=$(echo "$INPUT" | jq -r '.message // empty')
+
+# Skip empty messages
+if [ -z "$MESSAGE" ] || [ "$MESSAGE" = "null" ]; then
+    echo "$(date): No message found in notification" >> $LOG_FILE
+    exit 0
+fi
+
+# Check required environment variables
+if [ -z "$AIRCANA_SQS_QUEUE_URL" ]; then
+    echo "$(date): AIRCANA_SQS_QUEUE_URL not set, skipping SQS notification" >> $LOG_FILE
+    exit 0
+fi
+
+if [ -z "$AIRCANA_SQS_MESSAGE_TEMPLATE" ]; then
+    echo "$(date): AIRCANA_SQS_MESSAGE_TEMPLATE not set, skipping SQS notification" >> $LOG_FILE
+    exit 0
+fi
+
+# Create the message body by substituting {{message}} in the template
+MESSAGE_BODY=$(echo "$AIRCANA_SQS_MESSAGE_TEMPLATE" | sed "s|{{message}}|$MESSAGE|g")
+
+# Log the message being sent
+echo "$(date): Sending SQS message:" >> $LOG_FILE
+echo "Queue URL: $AIRCANA_SQS_QUEUE_URL" >> $LOG_FILE
+echo "Message Body: $MESSAGE_BODY" >> $LOG_FILE
+
+# Send message to SQS using aws CLI
+AWS_REGION=${AWS_REGION:-us-east-1}
+SQS_RESULT=$(aws --region "$AWS_REGION" sqs send-message \
+  --queue-url "$AIRCANA_SQS_QUEUE_URL" \
+  --message-body "$MESSAGE_BODY" 2>&1)
+
+# Log the result
+if [ $? -eq 0 ]; then
+    echo "$(date): Successfully sent SQS message" >> $LOG_FILE
+    echo "Response: $SQS_RESULT" >> $LOG_FILE
+else
+    echo "$(date): Failed to send SQS message" >> $LOG_FILE
+    echo "Error: $SQS_RESULT" >> $LOG_FILE
+fi
+
+echo "---" >> $LOG_FILE
+
+# Return success - don't block Claude Code if SQS fails
+exit 0

data/lib/aircana/templates/hooks/pre_tool_use.erb

@@ -2,25 +2,33 @@
 # Pre-tool-use hook generated by Aircana
 # This hook runs before any tool is executed
 
-# Get the tool name and parameters
-TOOL_NAME="$1"
-TOOL_PARAMS="$2"
+# Read JSON input from stdin
+INPUT=$(cat)
+
+# Parse JSON to extract tool information
+TOOL_NAME=$(echo "$INPUT" | jq -r '.tool_name // empty')
+TOOL_INPUT=$(echo "$INPUT" | jq -r '.tool_input // empty')
+SESSION_ID=$(echo "$INPUT" | jq -r '.session_id // empty')
+CWD=$(echo "$INPUT" | jq -r '.cwd // empty')
 
 # Log the tool usage (optional)
-echo "$(date): About to use tool: $TOOL_NAME" >> ~/.aircana/hooks.log
+echo "$(date): Session $SESSION_ID - About to use tool: $TOOL_NAME in $CWD" >> ~/.aircana/hooks.log
 
 # Basic validation example
 case "$TOOL_NAME" in
   "Bash")
     # Add validation for bash commands
-    if echo "$TOOL_PARAMS" | grep -q "rm -rf /"; then
+    COMMAND=$(echo "$TOOL_INPUT" | jq -r '.command // empty')
+    if echo "$COMMAND" | grep -q "rm -rf /"; then
       cat << EOF
 {
   "hookSpecificOutput": {
     "hookEventName": "PreToolUse",
     "permissionDecision": "deny",
     "permissionDecisionReason": "Dangerous command detected: rm -rf /"
-  }
+  },
+  "continue": false,
+  "stopReason": "Blocked dangerous command"
 }
 EOF
       exit 0
@@ -28,7 +36,23 @@ EOF
     ;;
   "Edit"|"Write")
     # Validate file operations
+    FILE_PATH=$(echo "$TOOL_INPUT" | jq -r '.file_path // empty')
     # Add custom validation logic here
+    # Example: Check if trying to modify system files
+    if echo "$FILE_PATH" | grep -q "^/etc/\|^/usr/\|^/bin/\|^/sbin/"; then
+      cat << EOF
+{
+  "hookSpecificOutput": {
+    "hookEventName": "PreToolUse",
+    "permissionDecision": "ask",
+    "permissionDecisionReason": "Attempting to modify system file: $FILE_PATH"
+  },
+  "continue": true,
+  "systemMessage": "Warning: About to modify a system file"
+}
+EOF
+      exit 0
+    fi
     ;;
 esac
 
@@ -38,6 +62,7 @@ cat << EOF
   "hookSpecificOutput": {
     "hookEventName": "PreToolUse",
     "permissionDecision": "allow"
-  }
+  },
+  "continue": true
 }
 EOF

data/lib/aircana/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Aircana
-  VERSION = "1.2.0"
+  VERSION = "1.4.0.rc1"
 end

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: aircana
 version: !ruby/object:Gem::Version
-  version: 1.2.0
+  version: 1.4.0.rc1
 platform: ruby
 authors:
 - Weston Dransfield
 bindir: exe
 cert_chain: []
-date: 2025-09-26 00:00:00.000000000 Z
+date: 2025-09-27 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: httparty
@@ -130,9 +130,7 @@ files:
 - lib/aircana/cli/commands/generate.rb
 - lib/aircana/cli/commands/hooks.rb
 - lib/aircana/cli/commands/install.rb
-- lib/aircana/cli/commands/plan.rb
 - lib/aircana/cli/commands/project.rb
-- lib/aircana/cli/commands/work.rb
 - lib/aircana/cli/help_formatter.rb
 - lib/aircana/cli/shell_command.rb
 - lib/aircana/cli/subcommand.rb
@@ -163,9 +161,9 @@ files:
 - lib/aircana/system_checker.rb
 - lib/aircana/templates/agents/base_agent.erb
 - lib/aircana/templates/agents/defaults/planner.erb
-- lib/aircana/templates/agents/defaults/worker.erb
 - lib/aircana/templates/commands/add_relevant_files.erb
 - lib/aircana/templates/hooks/bundle_install.erb
+- lib/aircana/templates/hooks/notification_sqs.erb
 - lib/aircana/templates/hooks/post_tool_use.erb
 - lib/aircana/templates/hooks/pre_tool_use.erb
 - lib/aircana/templates/hooks/rspec_test.erb

data/lib/aircana/cli/commands/plan.rb

@@ -1,69 +0,0 @@
-# frozen_string_literal: true
-
-require_relative "generate"
-require_relative "install"
-require_relative "../../generators/agents_generator"
-
-module Aircana
-  module CLI
-    module Plan
-      class << self
-        def run
-          ensure_planner_agent_installed
-          launch_claude_with_planner
-        end
-
-        private
-
-        def ensure_planner_agent_installed
-          planner_agent_path = File.join(
-            Aircana.configuration.claude_code_config_path,
-            "agents",
-            "planner.md"
-          )
-
-          return if File.exist?(planner_agent_path)
-
-          Aircana.human_logger.info("Planner agent not found. Generating and installing...")
-          Generate.run
-          Install.run
-        end
-
-        def launch_claude_with_planner
-          prompt = "Start a planning session with the 'planner' sub-agent"
-
-          Aircana.human_logger.info("Launching Claude Code with planner agent...")
-
-          claude_path = find_claude_path
-          if claude_path
-            system("#{claude_path} \"#{prompt}\"")
-          else
-            handle_claude_not_found(prompt)
-          end
-        end
-
-        def handle_claude_not_found(prompt)
-          error_message = "Claude Code command not found. " \
-                          "Please make sure Claude Code is installed and in your PATH."
-          Aircana.human_logger.error(error_message)
-          Aircana.human_logger.info("You can manually start Claude Code and run: #{prompt}")
-        end
-
-        def find_claude_path
-          # Try common locations for Claude Code binary (same as ClaudeClient)
-          possible_paths = [
-            File.expand_path("~/.claude/local/claude"),
-            `/usr/bin/which claude`.strip,
-            "/usr/local/bin/claude"
-          ]
-
-          possible_paths.each do |path|
-            return path if !path.empty? && File.executable?(path)
-          end
-
-          nil
-        end
-      end
-    end
-  end
-end