kiro-agent-team 1.0.0

package/.kiro/devlog/devlog-update.bat

@@ -0,0 +1,136 @@
+@echo off
+REM Development Log Auto-Update Script (Windows)
+REM Automatically captures and summarizes daily development progress
+REM Usage: devlog-update.bat
+
+setlocal enabledelayedexpansion
+
+REM Get script directory
+set "SCRIPT_DIR=%~dp0"
+set "DEVLOG_FILE=%SCRIPT_DIR%DEVLOG.md"
+
+echo.
+echo ========================================
+echo Development Log Update System
+echo ========================================
+echo.
+
+REM Get current date
+for /f "tokens=1-3 delims=/ " %%a in ('date /t') do set DATE=%%c/%%a/%%b
+for /f "tokens=1 delims= " %%a in ('time /t') do set TIME=%%a
+
+echo.
+echo Please provide information about today's work:
+echo.
+
+set /p WORK_FOCUS="1. What did you work on today? (Features, bugs, refactoring, etc.): "
+set /p HOURS_SPENT="2. How much time did you spend? (Total hours): "
+if "!HOURS_SPENT!"=="" set HOURS_SPENT=0
+
+set /p ACCOMPLISHMENTS="3. What were your main accomplishments?: "
+set /p CHALLENGES="4. Any challenges or blockers? (Optional - press Enter to skip): "
+set /p DECISIONS="5. Key technical decisions made? (Optional): "
+set /p NEXT_STEPS="6. What's planned for the next session?: "
+set /p LEARNINGS="7. Any new learnings or insights? (Optional): "
+set /p KIRO_USAGE="8. Which Kiro prompts were most helpful? (Optional): "
+
+echo.
+echo Analyzing git activity...
+echo.
+
+REM Check if git is available
+git --version >nul 2>&1
+if errorlevel 1 (
+    echo Note: Git not found or not in PATH - skipping git analysis
+    set COMMITS=0
+    set LINES_ADDED=0
+    set LINES_REMOVED=0
+) else (
+    REM Get commits for today
+    for /f %%a in ('git log --since=%DATE% --oneline 2^>nul ^| find /c /v ""') do set COMMITS=%%a
+    if "!COMMITS!"=="" set COMMITS=0
+    
+    REM Get basic statistics (simplified for Windows batch)
+    set LINES_ADDED=0
+    set LINES_REMOVED=0
+)
+
+echo Today's Commits: !COMMITS!
+echo Lines added: !LINES_ADDED!
+echo Lines removed: !LINES_REMOVED!
+echo.
+
+REM Create temporary entry file
+setlocal enabledelayedexpansion
+(
+    echo.
+    echo ## !DATE! - !WORK_FOCUS! [!HOURS_SPENT!h]
+    echo.
+    echo ### 📊 **Daily Metrics**
+    echo - **Time Spent**: !HOURS_SPENT! hours
+    echo - **Commits Made**: !COMMITS!
+    echo - **Lines Added**: !LINES_ADDED!
+    echo - **Lines Removed**: !LINES_REMOVED!
+    echo - **Net Lines**: !LINES_ADDED-LINES_REMOVED!
+    echo.
+    echo ### 🎯 **Accomplishments**
+    echo - !ACCOMPLISHMENTS!
+    echo.
+    echo ### 💻 **Technical Progress**
+    echo **Recent Commits:**
+    echo - Commits: !COMMITS!
+    echo - Files modified: [will update]
+    echo.
+    echo ### 🚧 **Challenges ^& Solutions**
+    if "!CHALLENGES!"=="" (
+        echo No significant challenges today.
+    ) else (
+        echo !CHALLENGES!
+    )
+    echo.
+    echo ### 🧠 **Key Decisions**
+    if "!DECISIONS!"=="" (
+        echo No major architectural decisions made today.
+    ) else (
+        echo !DECISIONS!
+    )
+    echo.
+    echo ### 📚 **Learnings ^& Insights**
+    if "!LEARNINGS!"=="" (
+        echo Continued building on existing knowledge.
+    ) else (
+        echo !LEARNINGS!
+    )
+    echo.
+    echo ### ⚡ **Kiro CLI Usage**
+    if "!KIRO_USAGE!"=="" (
+        echo Standard prompt usage during development.
+    ) else (
+        echo !KIRO_USAGE!
+    )
+    echo.
+    echo ### 📋 **Next Session Plan**
+    echo - !NEXT_STEPS!
+    echo.
+    echo ---
+    echo.
+) > "%TEMP%\devlog_entry.txt"
+
+REM Append entry to DEVLOG.md
+echo Appending entry to devlog...
+echo.
+
+type "%TEMP%\devlog_entry.txt" >> "!DEVLOG_FILE!"
+
+echo ========================================
+echo Development log updated successfully!
+echo ========================================
+echo.
+echo 📊 Today's Summary:
+echo Focus: !WORK_FOCUS!
+echo Time: !HOURS_SPENT!h
+echo Commits: !COMMITS!
+echo Code changes: +!LINES_ADDED!, -!LINES_REMOVED!
+echo.
+
+endlocal

package/.kiro/devlog/devlog-update.sh

@@ -0,0 +1,275 @@
+#!/bin/bash
+# Development Log Auto-Update Script
+# Automatically captures and summarizes daily development progress
+# Usage: ./devlog-update.sh [optional-hours]
+
+set -e
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+DEVLOG_FILE="$SCRIPT_DIR/DEVLOG.md"
+GIT_DIR="$(git rev-parse --git-dir 2>/dev/null || echo '.git')"
+
+# Color codes for output
+RED='\033[0;31m'
+GREEN='\033[0;32m'
+YELLOW='\033[1;33m'
+BLUE='\033[0;34m'
+NC='\033[0m' # No Color
+
+echo -e "${BLUE}========================================${NC}"
+echo -e "${BLUE}Development Log Update System${NC}"
+echo -e "${BLUE}========================================${NC}"
+
+# Function to get current date formatted
+get_date() {
+    date +"%B %d, %Y (%A)"
+}
+
+# Function to get hackathon day number
+get_hackathon_day() {
+    # Hackathon started January 5, 2026
+    HACKATHON_START="2026-01-05"
+    CURRENT_DATE=$(date +"%Y-%m-%d")
+    
+    # Calculate days difference
+    START_EPOCH=$(date -d "$HACKATHON_START" +%s 2>/dev/null || date -jf "%Y-%m-%d" "$HACKATHON_START" +%s 2>/dev/null)
+    CURRENT_EPOCH=$(date -d "$CURRENT_DATE" +%s 2>/dev/null || date -jf "%Y-%m-%d" "$CURRENT_DATE" +%s 2>/dev/null)
+    
+    if [ ! -z "$START_EPOCH" ] && [ ! -z "$CURRENT_EPOCH" ]; then
+        DAYS_DIFF=$(( ($CURRENT_EPOCH - $START_EPOCH) / 86400 ))
+        echo $((DAYS_DIFF + 1))
+    else
+        echo "1"
+    fi
+}
+
+# Function to gather user information
+gather_user_info() {
+    echo -e "\n${YELLOW}Please provide information about today's work:${NC}\n"
+    
+    # Question 1: What did you work on?
+    echo -e "${BLUE}1. What did you work on today?${NC} (Features, bugs, refactoring, etc.)"
+    read -p "   Answer: " WORK_FOCUS
+    
+    # Question 2: Time spent
+    echo -e "\n${BLUE}2. How much time did you spend?${NC} (Total hours)"
+    read -p "   Hours: " HOURS_SPENT
+    HOURS_SPENT=${HOURS_SPENT:-0}
+    
+    # Question 3: Main accomplishments
+    echo -e "\n${BLUE}3. What were your main accomplishments?${NC} (Brief summary)"
+    read -p "   Answer: " ACCOMPLISHMENTS
+    
+    # Question 4: Challenges
+    echo -e "\n${BLUE}4. Any challenges or blockers?${NC} (Optional - press Enter to skip)"
+    read -p "   Answer: " CHALLENGES
+    
+    # Question 5: Key decisions
+    echo -e "\n${BLUE}5. Key technical decisions made?${NC} (Optional - press Enter to skip)"
+    read -p "   Answer: " DECISIONS
+    
+    # Question 6: Next steps
+    echo -e "\n${BLUE}6. What's planned for the next session?${NC}"
+    read -p "   Answer: " NEXT_STEPS
+    
+    # Question 7: Learnings
+    echo -e "\n${BLUE}7. Any new learnings or insights?${NC} (Optional - press Enter to skip)"
+    read -p "   Answer: " LEARNINGS
+    
+    # Question 8: Kiro usage
+    echo -e "\n${BLUE}8. Which Kiro prompts were most helpful?${NC} (Optional - press Enter to skip)"
+    read -p "   Answer: " KIRO_USAGE
+}
+
+# Function to analyze git activity
+analyze_git_activity() {
+    echo -e "\n${YELLOW}Analyzing git activity...${NC}"
+    
+    # Check if git repo exists
+    if ! git rev-parse --git-dir > /dev/null 2>&1; then
+        echo -e "${YELLOW}  Note: Not in a git repository - skipping git analysis${NC}"
+        return
+    fi
+    
+    # Get today's date range
+    TODAY_START=$(date +"%Y-%m-%d")
+    TODAY_END=$(date +"%Y-%m-%d" -d "tomorrow" 2>/dev/null || date -v+1d +"%Y-%m-%d")
+    
+    # Get commits for today
+    echo -e "\n${BLUE}Today's Commits:${NC}"
+    COMMITS=$(git log --since="$TODAY_START" --until="$TODAY_END" --oneline 2>/dev/null | wc -l)
+    echo "  Total commits: $COMMITS"
+    
+    if [ $COMMITS -gt 0 ]; then
+        echo "  Commit messages:"
+        git log --since="$TODAY_START" --until="$TODAY_END" --pretty=format:"    - %h: %s" 2>/dev/null || true
+    fi
+    
+    # Get line changes
+    echo -e "\n${BLUE}Code Changes:${NC}"
+    STATS=$(git log --since="$TODAY_START" --until="$TODAY_END" --pretty=tformat: --numstat 2>/dev/null | \
+        awk '{add+=$1; del+=$2} END {print add "," del}')
+    
+    LINES_ADDED=$(echo $STATS | cut -d',' -f1)
+    LINES_REMOVED=$(echo $STATS | cut -d',' -f2)
+    LINES_ADDED=${LINES_ADDED:-0}
+    LINES_REMOVED=${LINES_REMOVED:-0}
+    
+    echo "  Lines added: $LINES_ADDED"
+    echo "  Lines removed: $LINES_REMOVED"
+    echo "  Net change: $((LINES_ADDED - LINES_REMOVED))"
+    
+    # Files modified
+    echo -e "\n${BLUE}Files Modified:${NC}"
+    FILES=$(git diff --name-only HEAD~1 HEAD 2>/dev/null | wc -l || echo "N/A")
+    echo "  Total files: $FILES"
+}
+
+# Function to generate devlog entry
+generate_entry() {
+    local DAY=$(get_hackathon_day)
+    local DATE=$(get_date)
+    
+    echo -e "\n${YELLOW}Generating devlog entry...${NC}"
+    
+    cat > /tmp/devlog_entry.txt << EOF
+## Day $DAY ($DATE) - $WORK_FOCUS [$HOURS_SPENT h]
+
+### 📊 **Daily Metrics**
+- **Time Spent**: ${HOURS_SPENT} hours
+- **Commits Made**: $COMMITS
+- **Lines Added**: $LINES_ADDED
+- **Lines Removed**: $LINES_REMOVED
+- **Net Lines**: $((LINES_ADDED - LINES_REMOVED))
+
+### 🎯 **Accomplishments**
+- $ACCOMPLISHMENTS
+
+### 💻 **Technical Progress**
+**Commits Made Today:**
+\`\`\`
+$(git log --since="$TODAY_START" --until="$TODAY_END" --oneline 2>/dev/null || echo "No commits today")
+\`\`\`
+
+**Code Changes:**
+- Files modified: $FILES
+- Lines added: $LINES_ADDED
+- Lines removed: $LINES_REMOVED
+- Net change: $((LINES_ADDED - LINES_REMOVED))
+
+### 🚧 **Challenges & Solutions**
+${CHALLENGES:-"No significant challenges today."}
+
+### 🧠 **Key Decisions**
+${DECISIONS:-"No major architectural decisions made today."}
+
+### 📚 **Learnings & Insights**
+${LEARNINGS:-"Continued building on existing knowledge."}
+
+### ⚡ **Kiro CLI Usage**
+${KIRO_USAGE:-"Standard prompt usage during development."}
+
+### 📋 **Next Session Plan**
+- $NEXT_STEPS
+
+---
+
+EOF
+    
+    echo -e "${GREEN}Entry generated successfully${NC}"
+}
+
+# Function to append entry to devlog
+append_entry() {
+    echo -e "\n${YELLOW}Appending entry to devlog...${NC}"
+    
+    # Read the current devlog
+    local TEMP_FILE="/tmp/devlog_temp.md"
+    
+    # Create new devlog with entry inserted after the "Daily Development Entries" line
+    awk '
+        /^## Daily Development Entries/ {
+            print $0
+            print ""
+            while ((getline line < "/tmp/devlog_entry.txt") > 0) {
+                print line
+            }
+            close("/tmp/devlog_entry.txt")
+            next
+        }
+        { print }
+    ' "$DEVLOG_FILE" > "$TEMP_FILE"
+    
+    mv "$TEMP_FILE" "$DEVLOG_FILE"
+    echo -e "${GREEN}Entry appended to $DEVLOG_FILE${NC}"
+}
+
+# Function to update statistics
+update_statistics() {
+    echo -e "\n${YELLOW}Updating development statistics...${NC}"
+    
+    # Count day entries (## Day X entries)
+    TOTAL_DAYS=$(grep -c "^## Day [0-9]" "$DEVLOG_FILE" || echo "1")
+    
+    # Parse total hours from all entries
+    TOTAL_HOURS=$(grep "Time Spent" "$DEVLOG_FILE" | grep -oE "[0-9]+(\.[0-9]+)?" | \
+        awk '{sum+=$1} END {print sum}' || echo "0")
+    
+    # Get total commits from git
+    TOTAL_COMMITS=$(git rev-list --count HEAD 2>/dev/null || echo "0")
+    
+    # Get cumulative line changes
+    CUMULATIVE_STATS=$(git log --pretty=tformat: --numstat 2>/dev/null | \
+        awk '{add+=$1; del+=$2} END {print add "," del}' || echo "0,0")
+    
+    TOTAL_ADDED=$(echo $CUMULATIVE_STATS | cut -d',' -f1)
+    TOTAL_REMOVED=$(echo $CUMULATIVE_STATS | cut -d',' -f2)
+    
+    # Update statistics in devlog
+    sed -i.bak "
+        s/\*\*Total Development Days\*\*: [0-9]*/\*\*Total Development Days\*\*: $TOTAL_DAYS/
+        s/\*\*Total Hours Logged\*\*: [0-9.]*h/\*\*Total Hours Logged\*\*: ${TOTAL_HOURS}h/
+        s/\*\*Total Commits\*\*: [0-9]*/\*\*Total Commits\*\*: $TOTAL_COMMITS/
+        s/\*\*Lines of Code Added\*\*: [0-9]*/\*\*Lines of Code Added\*\*: $TOTAL_ADDED/
+        s/\*\*Lines of Code Removed\*\*: [0-9]*/\*\*Lines of Code Removed\*\*: $TOTAL_REMOVED/
+    " "$DEVLOG_FILE"
+    
+    rm -f "$DEVLOG_FILE.bak"
+    
+    echo -e "${GREEN}Statistics updated:${NC}"
+    echo "  Total days: $TOTAL_DAYS"
+    echo "  Total hours: ${TOTAL_HOURS}h"
+    echo "  Total commits: $TOTAL_COMMITS"
+    echo "  Lines added: $TOTAL_ADDED"
+    echo "  Lines removed: $TOTAL_REMOVED"
+}
+
+# Main execution
+main() {
+    # Gather user information
+    gather_user_info
+    
+    # Analyze git activity
+    analyze_git_activity
+    
+    # Generate and append entry
+    generate_entry
+    append_entry
+    
+    # Update statistics
+    update_statistics
+    
+    echo -e "\n${GREEN}========================================${NC}"
+    echo -e "${GREEN}Development log updated successfully!${NC}"
+    echo -e "${GREEN}========================================${NC}\n"
+    
+    # Show summary
+    echo -e "${BLUE}📊 Today's Summary:${NC}"
+    echo "  Focus: $WORK_FOCUS"
+    echo "  Time: ${HOURS_SPENT}h"
+    echo "  Commits: $COMMITS"
+    echo "  Code changes: +$LINES_ADDED, -$LINES_REMOVED"
+}
+
+# Run main function
+main

package/.kiro/devlog/feature-completion-hook.bat

@@ -0,0 +1,78 @@
+@echo off
+REM Feature Completion Hook (Windows)
+REM Automatically captures feature milestones when code is committed
+REM Usage: feature-completion-hook.bat "Feature Name" "feature-branch-name"
+
+setlocal enabledelayedexpansion
+
+set "SCRIPT_DIR=%~dp0"
+set "DEVLOG_FILE=%SCRIPT_DIR%DEVLOG.md"
+
+REM Get parameters
+set "FEATURE_NAME=%~1"
+if "!FEATURE_NAME!"=="" set "FEATURE_NAME=Feature"
+
+REM Get current branch if not specified
+if "!FEATURE_BRANCH!"=="" (
+    for /f %%a in ('git branch --show-current 2^>nul') do set FEATURE_BRANCH=%%a
+)
+if "!FEATURE_BRANCH!"=="" set "FEATURE_BRANCH=unknown"
+
+REM Get current date
+for /f "tokens=1-3 delims=/ " %%a in ('date /t') do set CURRENT_DATE=%%c/%%a/%%b
+
+echo.
+echo ========================================
+echo Feature Completion Milestone
+echo ========================================
+echo.
+
+echo Analyzing feature completion...
+echo.
+
+REM Get feature branch stats (simplified for Windows)
+set COMMITS=0
+set FILES=0
+set LINES_ADDED=0
+set LINES_REMOVED=0
+
+git --version >nul 2>&1
+if errorlevel 0 (
+    REM Get commit count
+    for /f %%a in ('git rev-list --count HEAD 2^>nul') do set COMMITS=%%a
+)
+
+echo Feature: !FEATURE_NAME!
+echo Branch: !FEATURE_BRANCH!
+echo Date: !CURRENT_DATE!
+echo Commits: !COMMITS!
+echo.
+
+REM Create milestone directory if it doesn't exist
+if not exist "!SCRIPT_DIR!.feature-milestones" mkdir "!SCRIPT_DIR!.feature-milestones"
+
+REM Store feature milestone
+(
+    echo.
+    echo ---
+    echo.
+    echo ### ✨ **Feature Milestone**: !FEATURE_NAME!
+    echo **Date**: !CURRENT_DATE!
+    echo **Branch**: !FEATURE_BRANCH!
+    echo.
+    echo **Feature Statistics:**
+    echo - **Commits**: !COMMITS!
+    echo - **Files Modified**: !FILES!
+    echo - **Lines Added**: !LINES_ADDED!
+    echo - **Lines Removed**: !LINES_REMOVED!
+    echo.
+    echo **Status**: Feature implementation complete, ready for code review and testing.
+    echo.
+) >> "!DEVLOG_FILE!"
+
+echo ✓ Feature milestone recorded
+echo.
+echo Note: Run 'devlog-update.bat' at the end of your work session to consolidate.
+echo.
+
+endlocal

package/.kiro/devlog/feature-completion-hook.sh

@@ -0,0 +1,84 @@
+#!/bin/bash
+# Feature Completion Hook
+# Automatically captures feature milestones when code is committed
+# Should be integrated with your git workflow or CI/CD system
+# Usage: ./feature-completion-hook.sh "Feature Name" "feature-branch-name"
+
+set -e
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+DEVLOG_FILE="$SCRIPT_DIR/DEVLOG.md"
+
+# Color codes
+BLUE='\033[0;34m'
+GREEN='\033[0;32m'
+YELLOW='\033[1;33m'
+NC='\033[0m'
+
+FEATURE_NAME="${1:-Feature}"
+FEATURE_BRANCH="${2:-$(git branch --show-current 2>/dev/null)}"
+CURRENT_DATE=$(date +"%B %d, %Y")
+
+echo -e "${BLUE}========================================${NC}"
+echo -e "${BLUE}Feature Completion Milestone${NC}"
+echo -e "${BLUE}========================================${NC}\n"
+
+# Get feature branch stats
+echo -e "${YELLOW}Analyzing feature completion...${NC}\n"
+
+# Get commits in this feature
+MAIN_BRANCH="${MAIN_BRANCH:-main}"
+if git rev-parse --verify "$MAIN_BRANCH" >/dev/null 2>&1; then
+    COMMITS=$(git log "$MAIN_BRANCH..$FEATURE_BRANCH" --oneline 2>/dev/null | wc -l)
+    FILES=$(git diff "$MAIN_BRANCH..$FEATURE_BRANCH" --name-only 2>/dev/null | wc -l)
+    STATS=$(git diff "$MAIN_BRANCH..$FEATURE_BRANCH" --numstat 2>/dev/null | \
+        awk '{add+=$1; del+=$2} END {print add "," del}' || echo "0,0")
+else
+    COMMITS=$(git rev-list --count HEAD 2>/dev/null || echo "0")
+    FILES="N/A"
+    STATS="0,0"
+fi
+
+LINES_ADDED=$(echo $STATS | cut -d',' -f1)
+LINES_REMOVED=$(echo $STATS | cut -d',' -f2)
+LINES_ADDED=${LINES_ADDED:-0}
+LINES_REMOVED=${LINES_REMOVED:-0}
+
+# Create milestone entry
+cat > /tmp/feature_milestone.txt << EOF
+
+---
+
+### ✨ **Feature Milestone**: $FEATURE_NAME
+**Date**: $CURRENT_DATE  
+**Branch**: $FEATURE_BRANCH
+
+**Feature Statistics:**
+- **Commits**: $COMMITS
+- **Files Modified**: $FILES
+- **Lines Added**: $LINES_ADDED
+- **Lines Removed**: $LINES_REMOVED
+- **Net Change**: $((LINES_ADDED - LINES_REMOVED))
+
+**Status**: Feature implementation complete, ready for code review and testing.
+
+*Automatically captured on feature completion*
+
+EOF
+
+echo -e "${GREEN}Feature milestone:${NC}"
+echo "  Feature: $FEATURE_NAME"
+echo "  Branch: $FEATURE_BRANCH"
+echo "  Commits: $COMMITS"
+echo "  Files: $FILES"
+echo "  Changes: +$LINES_ADDED, -$LINES_REMOVED"
+
+echo -e "\n${YELLOW}Note: This milestone will be included in the end-of-day devlog update.${NC}"
+echo -e "${YELLOW}Run './devlog-update.sh' at the end of your work session to consolidate.${NC}\n"
+
+# Store feature info for devlog update to pick up
+mkdir -p "$SCRIPT_DIR/.feature-milestones"
+echo "$FEATURE_NAME|$FEATURE_BRANCH|$COMMITS|$FILES|$LINES_ADDED|$LINES_REMOVED" >> \
+    "$SCRIPT_DIR/.feature-milestones/$(date +%Y-%m-%d).txt"
+
+echo -e "${GREEN}✓ Feature milestone recorded${NC}\n"

package/.kiro/documentation/cli.md

@@ -0,0 +1,31 @@
+# Prompt to code to deployment in your terminal
+Unleash [custom agents](https://kiro.dev/docs/cli/custom-agents/) in a highly interactive terminal experience. Build features in complex codebases. Automate workflows in seconds. Analyze errors and trace bugs with precision. 
+Install on macOS and Linux
+`curl -fsSL https://cli.kiro.dev/install | bash`
+Watch Demo
+Loading image...![terminal showing Kiro logo and prompt](https://kiro.dev/images/home/cli.png?h=7fefd22e)
+Terminal — 80×24
+### Quality code every time
+Kiro agents deliver precise code changes across large codebases with the power of [Claude frontier models](https://kiro.dev/docs/cli/chat/model-selection/) and [advanced context management](https://kiro.dev/docs/cli/chat/context/).
+### Powerful at any scale
+Kiro CLI is a lightning-fast coding experience that adapts to how you work, from simple bash commands to complex enterprise workflows.
+### Fast, secure development
+With powerful [agent steering](https://kiro.dev/docs/cli/steering/) and [native MCP support](https://kiro.dev/docs/cli/mcp/), Kiro helps you ship with precision, from prompt to production.
+Loading image...
+![](https://kiro.dev/images/cli/production.png?h=b7e9ae86)
+### Precise context, precise code
+Using your [knowledge base](https://kiro.dev/docs/cli/experimental/knowledge-management/), [steering files](https://kiro.dev/docs/cli/steering/), and [MCP tools](https://kiro.dev/docs/cli/mcp/), Kiro CLI delivers production-grade code, documentation, and tests that match your requirements.
+Loading image...
+![](https://kiro.dev/images/cli/agents.png?h=a0e3ea37)
+### Custom agents for every task
+[Build task-specific agents](https://kiro.dev/docs/cli/custom-agents/creating/) optimized for your best practices through pre-defined [tool permissions](https://kiro.dev/docs/cli/chat/permissions/), [context](https://kiro.dev/docs/cli/chat/context/), and [prompts](https://kiro.dev/docs/cli/chat/manage-prompts/).
+Loading image...
+![](https://kiro.dev/images/cli/hooks.png?h=00a29f59)
+### Automated actions
+Format code, run tests, manage logs, and more—all through automated shell commands.
+Loading image...
+![](https://kiro.dev/images/cli/code.png?h=afb6e933)
+### Maintain flow across Kiro tools
+Whether you're using the [IDE](https://kiro.dev/docs/) or CLI, Kiro understands the intent behind your prompts and helps you implement complex features on larger codebases, in fewer shots.
+{Resources}
+## Get started with Kiro CLI

package/.kiro/documentation/docs_cli.md

@@ -0,0 +1,41 @@
+# Get started
+The Kiro CLI brings the power of AI-assisted development to your terminal. Build, test, and deploy applications using natural language commands and automated workflows.
+Get started with the Kiro CLI in minutes. Install on macOS and Linux:
+`curl -fsSL https://cli.kiro.dev/install | bash`
+Start using Kiro CLI:
+bash
+```
+
+cd my-project
+kiro-cli
+
+
+```
+
+## Core features[](https://kiro.dev/docs/cli/#core-features)
+[ Interactive Chat Engage with Kiro through natural conversation in your terminal. ](https://kiro.dev/docs/cli/chat/)
+[ Custom Agents Create and deploy specialized agents for your workflows. ](https://kiro.dev/docs/cli/custom-agents/)
+[ MCP Integration Connect external tools and data sources through Model Context Protocol. ](https://kiro.dev/docs/cli/mcp/)
+[ Smart Hooks Automate workflows with intelligent pre/post command hooks. ](https://kiro.dev/docs/cli/hooks/)
+[ Agent Steering Steer Kiro agent with your best practices and preferences. ](https://kiro.dev/docs/cli/steering/)
+[ Auto Complete Intelligent command completion with context awareness. ](https://kiro.dev/docs/cli/autocomplete/)
+## Use cases[](https://kiro.dev/docs/cli/#use-cases)
+The Kiro CLI is perfect for:
+  * **Interactive Development** : Chat with Kiro directly in your terminal for instant help
+  * **Custom Automation** : Create specialized agents for your specific workflows
+  * **Team Standardization** : Use team level best practises and preferences
+  * **External Integrations** : Connect tools and services through MCP servers
+  * **Intelligent Assistance** : Get context-aware suggestions and auto-completion
+  * **Workflow Optimization** : Automate repetitive tasks with smart hooks
+
+
+## What's next?[](https://kiro.dev/docs/cli/#whats-next)
+### Ready to get started?
+Install the CLI and create your first project in under 5 minutes.
+[Install Kiro CLI →](https://kiro.dev/docs/cli/installation)
+Page updated: November 17, 2025
+[Installation](https://kiro.dev/docs/cli/installation/)
+On this page
+  * [Core features](https://kiro.dev/docs/cli/#core-features)
+  * [Use cases](https://kiro.dev/docs/cli/#use-cases)
+  * [What's next?](https://kiro.dev/docs/cli/#whats-next)

package/.kiro/documentation/docs_cli_authentication.md

@@ -0,0 +1,43 @@
+# Authentication methods
+Kiro supports the following authentication providers:
+  * GitHub: Seamless integration with your GitHub account
+  * Google: Sign in with your Google credentials
+  * AWS Builder ID: Quick setup for individual developers
+  * AWS IAM Identity Center: Enterprise-grade authentication
+
+
+**Info**
+Users that have a paid Kiro subscription and access it through a social login provider (like GitHub or Google) or through AWS Builder ID are considered _individual subscribers_. We may use certain content from Kiro Free Tier and Kiro individual subscribers for service improvement. For more information on service improvement and how to opt out, see [Service improvement](https://kiro.dev/docs/privacy-and-security/data-protection/#service-improvement).
+## Sign in to Kiro CLI[](https://kiro.dev/docs/cli/authentication/#sign-in-to-kiro-cli)
+**To sign in with Kiro CLI**
+  1. At the command line, enter `kiro-cli` or `kiro-cli login`. You will be prompted to press enter to complete the sign-in process in your browser.
+  2. In your browser, choose the organization or system through which you will authenticate: 
+     * Google
+     * GitHub
+     * Builder ID
+     * Your organization
+  3. After you authenticate, you'll receive a message in your browser, directing you back to your terminal.
+  4. When you return to your terminal, you should be signed in with the Kiro CLI.
+
+
+## Sign out of Kiro CLI[](https://kiro.dev/docs/cli/authentication/#sign-out-of-kiro-cli)
+**To sign out of Kiro CLI**
+  1. At the command line, enter `kiro-cli logout`.
+
+
+## Troubleshooting authentication issues[](https://kiro.dev/docs/cli/authentication/#troubleshooting-authentication-issues)
+If you encounter problems during the authentication process, such as browser redirect failures or sign-in errors, check our [troubleshooting guide](https://kiro.dev/docs/troubleshooting/#authentication-issues) for platform-specific solutions and common fixes.
+## Next steps[](https://kiro.dev/docs/cli/authentication/#next-steps)
+  * [Review FAQ](https://kiro.dev/faq)
+  * [Explore Agent features](https://kiro.dev/docs/chat)
+  * [Get started with Kiro](https://kiro.dev/docs)
+
+
+Page updated: November 18, 2025
+[Installation](https://kiro.dev/docs/cli/installation/)
+[Chat](https://kiro.dev/docs/cli/chat/)
+On this page
+  * [Sign in to Kiro CLI](https://kiro.dev/docs/cli/authentication/#sign-in-to-kiro-cli)
+  * [Sign out of Kiro CLI](https://kiro.dev/docs/cli/authentication/#sign-out-of-kiro-cli)
+  * [Troubleshooting authentication issues](https://kiro.dev/docs/cli/authentication/#troubleshooting-authentication-issues)
+  * [Next steps](https://kiro.dev/docs/cli/authentication/#next-steps)