aiwf 0.1.0 → 0.3.1

package/claude-code/simone/CHANGELOG.md

@@ -1,71 +0,0 @@
-# Changelog
-
-## 2025-05-30
-
-### Added
-
-- `npx hello-simone` quick start command for easy Simone installation
-- Interactive, adaptive initialize command that:
-  - Auto-detects project type and framework
-  - Guides users through conversational setup
-  - Creates documentation through Q&A process
-  - Adapts to existing vs new projects
-
-### Changed
-
-- initialize command completely rewritten for better user experience
-- Removed complex branching logic in favor of adaptive process
-- Focus on conversational interaction rather than rigid steps
-
-### Improved
-
-- Better handling of existing documentation during setup
-- Smart project detection (Node.js, Python, PHP, etc.)
-- Milestone creation now interactive and context-aware
-
-## 2025-05-29
-
-### Added
-
-- ADR template for architecture decision records
-- Task ID filtering in commit command (T01_S02, TX003 patterns)
-- YOLO mode in commit command to skip user approval
-- Code review results now write to task Output Log sections
-- create_general_task command for structured task creation
-- create_sprint_tasks command for detailed sprint planning
-- create_sprints_from_milestone command for milestone-based sprint planning
-- prime command for quick project context loading
-- yolo command for autonomous task execution without user interaction
-
-### Changed
-
-- Date format simplified to YYYY-MM-DD HH:MM in templates
-- Milestone template heading structure updated
-- do_task command now uses parallel subagents and updates project manifest
-- project_review command removes timeline pressure and focuses on current state
-
-### Removed
-
-- create_sprint, create_task, plan_milestone commands (replaced by new workflow)
-
-## Developer Notes
-
-This update represents a significant evolution based on real-world usage and user feedback. The command architecture has been substantially enhanced with better use of parallel agents, loops, and conditionals, which work surprisingly well in practice.
-
-**Command Complexity**: The enhanced commands may behave differently between Claude Opus and Sonnet models. While the complexity might be challenging for Sonnet, testing suggests it should handle the workflows effectively.
-
-**Task Quality Improvements**: The new `create_sprint_tasks` and `create_general_task` commands now provide much better context and codebase references, resulting in notably higher quality task generation with specific implementation guidance.
-
-**YOLO Mode Warning**: The standalone `yolo` command requires extreme caution. It should only be used:
-
-- Within isolated development environments
-- With Claude Code's permission-skipping mode enabled (`claude --dangerously-skip-permissions`)
-- Never on production systems or systems with important data
-
-The YOLO mode can potentially modify or delete files outside your project directory. Use at your own risk and only in completely isolated environments.
-
-**Feedback Welcome**: Submit issues or pull requests on GitHub. This framework continues to evolve based on real-world usage patterns.
-
-## 2025-05-23
-
-Initial release of Simone framework

package/claude-code/simone/LICENSE

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2025 moonklabs
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.

package/claude-code/simone/README.md

@@ -1,219 +0,0 @@
-# Simone for Claude Code
-
-## What is this?
-
-Simone is a directory-based project management system I built to work better with Claude Code. It's basically a set of folders, markdown files, and custom commands that help break down software projects into manageable chunks that AI can handle effectively.
-
-**⚠️ Complexity Warning**: Simone is a sophisticated system that requires time to understand properly. It's not a simple plug-and-play solution, but rather a framework that works best when you take the time to learn how it operates and adapt it to your workflow.
-
-**📋 Latest Updates**: See [CHANGELOG.md](CHANGELOG.md) for recent changes and improvements.
-
-## How to Get Started
-
-### 1. Install Simone
-
-```bash
-npx hello-simone
-```
-
-This sets up the folder structure and installs/updates the command files in your project. Can also be used to update an existing installation - command files get backed up automatically.
-
-### 2. Initialize Your Project
-
-Open your project in Claude Code and run:
-
-```
-/project:simone:initialize
-```
-
-This guides you through the basic setup process. Works with new or existing codebases, and can help you create project documentation (PRDs, architecture docs) or work with documents you already have.
-
-### 3. Set Up Your First Milestone
-
-Create a milestone folder in `.simone/02_REQUIREMENTS/` named `M01_Your_Milestone_Name` (e.g., `M01_Basic_Application`). Include at least:
-
-- `M01_PRD.md` - Product requirements document
-- Other specs as needed: `M01_Database_Schema.md`, `M01_API_Specs.md`, etc.
-
-*Note: There's no command for this yet. Use the existing chat from step 2 to guide Claude through milestone creation, ensuring proper naming with the `M##_` prefix and underscores.*
-
-### 4. Break Down into Sprints
-
-```
-/project:simone:create_sprints_from_milestone
-```
-
-This analyzes your milestone and breaks it down into logical sprints. It looks at the entire scope and creates meaningful sprint boundaries without detailed tasks yet.
-
-### 5. Create Your First Tasks
-
-```
-/project:simone:create_sprint_tasks
-```
-
-This analyzes your sprints, reviews documentation, researches necessary information, and identifies knowledge gaps to gain comprehensive understanding of your project. Creates detailed, actionable tasks for the current sprint.
-
-*Important: Only create tasks for your next sprint, not all sprints upfront. After completing Sprint 1, then create tasks for Sprint 2. This ensures the system can reference your existing codebase and incorporate completed work into future task creation.*
-
-### 6. Start Working
-
-```
-/project:simone:do_task
-```
-
-This will automatically pick a task from your general tasks or sprints. For faster execution, specify a task ID:
-
-```
-/project:simone:do_task T01_S01
-```
-
-Claude will then work through the specified task with full project context.
-
-That's the basic workflow to get started! You can also:
-
-- Create general tasks with `/project:simone:create_general_task`
-- Use YOLO mode to run a full sprint autonomously
-- Explore other commands in `.claude/commands/simone/`
-
-**Important**: Simone is a complex system, not a simple set-and-forget tool. It works best when you understand how it operates. Take time to read through the commands and consider adapting them to your workflow.
-
-## How it Works
-
-Simone organizes your project into:
-
-- **Milestones**: Major features or project phases
-- **Sprints**: Groups of related tasks within a milestone
-- **Tasks**: Individual work items scoped for one Claude session
-
-Each task gets full project context so Claude knows exactly what to build and how it fits into your architecture.
-
-## Why I built this
-
-AI coding tools have become incredibly powerful, but they all face the same fundamental challenge: context management. The context window is limited in size, and we have little control over what stays in context and what doesn't.
-
-The problem with long-running sessions is context decay - as you work, critical project knowledge silently falls off the end of the context window. You don't know what's been forgotten until something goes wrong.
-
-My solution: Start fresh for each task, but provide rich surrounding context. By keeping tasks focused and well-scoped, I can dedicate more of the context window to relevant project knowledge, requirements, and architectural decisions. This way:
-
-- Each task starts with exactly the project context it needs
-- No critical knowledge gets lost in long sessions
-- Claude can work confidently with full awareness of requirements
-- The surrounding context guides development, not just the task description
-
-The result is a task-based workflow where Claude always has the right context for the job at hand.
-
-## Key Components
-
-### 00_PROJECT_MANIFEST.md
-
-The central document containing the project's vision, goals, and high-level overview. It serves as the starting point for Claude to understand the project. **Important**: The manifest file must be named exactly `00_PROJECT_MANIFEST.md`, not `MANIFEST.md`.
-
-### 01_PROJECT_DOCS/
-
-Contains general project documentation including technical specifications, user guides, and API documentation that Claude can reference.
-
-### 02_REQUIREMENTS/
-
-Organized by milestones, this directory stores product requirements documents (PRDs) and their amendments, providing a clear view of what needs to be built. This helps Claude understand the project requirements. Milestone folders must follow the naming convention `M##_Milestone_Name/` (e.g., `M01_Backend_Setup/`).
-
-### 03_SPRINTS/
-
-Contains sprint plans and task definitions organized by milestone and sprint sequence. Each sprint folder contains individual task files with detailed information for Claude to work on.
-
-### 04_GENERAL_TASKS/
-
-Stores task definitions for work not tied to a specific sprint. Completed tasks use a `TX` prefix (e.g., `TX001_Completed_Task.md`), making it easy for Claude to identify what's been done.
-
-### 05_ARCHITECTURAL_DECISIONS/
-
-Captures significant architectural decisions as Architecture Decision Records (ADRs), documenting the context, options considered, and rationale. This provides critical context for Claude when making technical decisions. Uses a structured ADR template for consistency.
-
-### 10_STATE_OF_PROJECT/
-
-Contains timestamped project review snapshots created by the `project_review` command. These provide a historical record of project health, technical decisions, and progress over time.
-
-### 99_TEMPLATES/
-
-Contains standardized templates for different document types to ensure consistency for both humans and Claude:
-
-- Task templates with structured objectives and acceptance criteria
-- Sprint and milestone metadata templates
-- ADR template for documenting architectural decisions
-- All templates use simplified date formats (YYYY-MM-DD HH:MM)
-
-### .claude/commands/simone/
-
-Custom Claude Code commands that power the Simone workflow:
-
-- `initialize` - Set up project structure and documentation
-- `create_sprints_from_milestone` - Break milestones into logical sprints
-- `create_sprint_tasks` - Generate detailed tasks from sprint plans
-- `do_task` - Execute individual tasks with full context
-- `yolo` - Autonomous sprint execution (use with caution)
-- And many more for testing, reviewing, and project management
-
-## Directory Structure
-
-```plaintext
-.simone/
-├── 00_PROJECT_MANIFEST.md
-├── 01_PROJECT_DOCS/
-├── 02_REQUIREMENTS/
-│   ├── M01_Backend_Setup/
-│   ├── M02_Frontend_Setup/
-│   └── ...
-├── 03_SPRINTS/
-│   ├── S01_M01_Initial_API/
-│   ├── S02_M01_Database_Schema/
-│   └── ...
-├── 04_GENERAL_TASKS/
-│   ├── TX001_Refactor_Logging_Module.md  # Completed task
-│   ├── T002_API_Rate_Limiting.md          # Open task
-│   └── ...
-├── 05_ARCHITECTURE_DECISIONS/
-│   ├── ADR001_Database_Selection.md
-│   └── ...
-├── 10_STATE_OF_PROJECT/         # Project review snapshots
-└── 99_TEMPLATES/
-    ├── task_template.md
-    ├── sprint_meta_template.md
-    └── milestone_meta_template.md
-```
-
-## Configuration Tips
-
-### Enabling Parallel Task Execution
-
-While Simone commands like `create_sprint_tasks` support the `useParallelSubagents` instruction, Claude Code needs to be configured to actually execute tasks in parallel. By default, it only runs one task at a time.
-
-To enable parallel execution:
-
-```bash
-# Set the number of parallel tasks (example: 3)
-claude config set --global "parallelTasksCount" 3
-
-# Check your current configuration
-claude config list -g
-```
-
-**Important considerations:**
-
-- Choose the number based on your system's capabilities and rate limits
-- Parallel execution increases API usage significantly
-- Some tasks may have conflicts when run in parallel
-- Start with a small number (2-3) and adjust based on your experience
-
-## Contributing & Feedback
-
-I'd love to hear from you! This is very much shaped by how I work, and I'm sure there are tons of improvements to be made.
-
-- **GitHub Issues**: Best place for bugs and feature requests
-- **Anthropic Discord**: Find me @helmi if you want to chat about it
-- **Pull Requests**: Very welcome! Let's make this better together
-
-I'm particularly interested in:
-
-- How you're using it differently
-- What's missing for your workflow
-- Ideas for better Claude Code integration
-- Different organizational approaches

package/claude-code/simone/SYNC_GUIDE.md

@@ -1,172 +0,0 @@
-# Simone Framework Sync Guide
-
-## Overview
-
-This guide explains how to sync Simone framework updates from development projects (like Synapsa) back to the canonical `claude-simone` repository.
-
-**Important**: This is a ONE-WAY sync process. Framework improvements flow from active development projects → claude-simone, not the other way around.
-
-## Current Development Context
-
-- **Primary Development**: Happens in Synapsa project
-- **Framework Evolution**: New commands, templates, and improvements are tested in real use
-- **Sync Direction**: Synapsa → claude-simone (when improvements are stable)
-- **Manual Review**: Each sync should be carefully reviewed, not automated
-
-## What to Consider When Syncing
-
-Before syncing, ask yourself:
-1. Is this change Synapsa-specific or would it benefit all Simone users?
-2. Has this been tested enough in real use?
-3. Will this break existing workflows?
-4. Is the change documented clearly?
-
-## What Gets Synced
-
-### Framework Core (Always Sync)
-```
-/.claude/commands/simone/     # All command definitions
-/.simone/99_TEMPLATES/        # All templates
-/.simone/CLAUDE.MD           # Framework instructions
-/.simone/README.md           # Framework documentation
-```
-
-### Framework Structure (Sync Structure Only)
-```
-/.simone/10_STATE_OF_PROJECT/  # Directory only, not contents
-```
-
-### Project-Specific (Never Sync)
-```
-/.simone/00_PROJECT_MANIFEST.md
-/.simone/01_PROJECT_DOCS/*
-/.simone/02_REQUIREMENTS/*
-/.simone/03_SPRINTS/*
-/.simone/04_GENERAL_TASKS/*
-/.simone/05_ARCHITECTURAL_DECISIONS/*
-/.simone/10_STATE_OF_PROJECT/* (contents)
-```
-
-## Manual Sync Process (Synapsa → claude-simone)
-
-1. **Identify What Changed**
-   ```bash
-   # From claude-simone directory
-   # Compare commands
-   diff -r ./.claude/commands/simone/ ~/code/synapsa/.claude/commands/simone/
-   
-   # Compare templates
-   diff -r ./.simone/99_TEMPLATES/ ~/code/synapsa/.simone/99_TEMPLATES/
-   
-   # Check for new structural elements
-   ls -la ~/code/synapsa/.simone/
-   ```
-
-2. **Review Each Change Carefully**
-   - Read through command changes - are they improvements or project-specific?
-   - Check template modifications - are they more generic or more specific?
-   - Look for new directories or conventions
-
-3. **Selective Manual Copy**
-   - Copy only framework improvements
-   - Leave out Synapsa-specific adaptations
-   - Preserve generic examples in claude-simone
-
-4. **Test in claude-simone Context**
-   - Ensure examples still make sense
-   - Verify commands work with generic project structure
-   - Check that documentation is project-agnostic
-
-5. **Document Changes for Users**
-   - Update README.md with new features or changes
-   - Add usage examples for new commands
-   - Note any breaking changes or migration needs
-   - Consider creating a CHANGELOG.md for version history
-
-6. **Prepare for GitHub Push**
-   - Review all documentation for clarity
-   - Ensure examples are helpful and generic
-   - Check that getting started instructions still work
-   - Commit with clear message about what's new
-
-## Sync Decision Tree
-
-```
-Is it a command file? → YES → Sync it
-                     ↓ NO
-Is it a template? → YES → Sync it
-                 ↓ NO
-Is it CLAUDE.MD or README.md in .simone/? → YES → Sync it
-                                          ↓ NO
-Is it a new directory structure? → YES → Create directory only
-                                ↓ NO
-Don't sync (project-specific content)
-```
-
-## Handling Conflicts
-
-### Command Updates
-- New commands: Add directly
-- Modified commands: Review changes, ensure compatibility
-- Removed commands: Keep if still used in project
-
-### Template Changes
-- Always take latest version from claude-simone
-- Templates should be generic enough for all projects
-
-### Structure Changes
-- New directories: Add to all projects
-- Directory renames: Carefully migrate with content preservation
-
-## Best Practices
-
-1. **Regular Syncs**: Sync framework updates monthly or when new features are announced
-2. **Test After Sync**: Run a few commands to ensure everything works
-3. **Document Custom Changes**: If you modify framework files, document why
-4. **Contribute Back**: If you improve templates or commands, PR to claude-simone
-
-## Example: Syncing to Synapsa
-
-```bash
-# From synapsa directory
-cd ~/code/synapsa
-
-# Dry run first
-rsync -av --dry-run \
-  --include='/.claude/commands/simone/***' \
-  --include='/.simone/99_TEMPLATES/***' \
-  --include='/.simone/CLAUDE.MD' \
-  --include='/.simone/README.md' \
-  --exclude='/*' \
-  ~/code/claude-simone/ ./
-
-# If looks good, run without --dry-run
-rsync -av \
-  --include='/.claude/commands/simone/***' \
-  --include='/.simone/99_TEMPLATES/***' \
-  --include='/.simone/CLAUDE.MD' \
-  --include='/.simone/README.md' \
-  --exclude='/*' \
-  ~/code/claude-simone/ ./
-
-# Create any new directories
-mkdir -p .simone/10_STATE_OF_PROJECT
-```
-
-## Troubleshooting
-
-### Missing Directories
-Create them manually: `mkdir -p .simone/10_STATE_OF_PROJECT`
-
-### Command Not Working
-Check if it depends on new directory structures or conventions
-
-### Merge Conflicts
-Always prefer claude-simone version for framework files
-
-## Future Improvements
-
-- [ ] Automated sync script with safety checks
-- [ ] Version tracking for framework components
-- [ ] Compatibility matrix for different Simone versions
-- [ ] Migration guides for breaking changes

package/claude-code/simone/sync-simone.sh

@@ -1,138 +0,0 @@
-#!/bin/bash
-# Simone Framework Sync Script
-# 
-# NOTE: This script is kept for reference but should be used with extreme caution.
-# The primary sync flow is: Active Development (Synapsa) → claude-simone
-# Not the other way around. Manual review is strongly recommended over automated sync.
-#
-# Original purpose: Syncs framework components from claude-simone to a project
-# Current reality: Development happens in Synapsa, syncs back to claude-simone
-
-set -e
-
-# Colors for output
-RED='\033[0;31m'
-GREEN='\033[0;32m'
-YELLOW='\033[1;33m'
-NC='\033[0m' # No Color
-
-# Default source path (can be overridden)
-SOURCE_PATH="${SIMONE_SOURCE:-$HOME/code/claude-simone}"
-TARGET_PATH="."
-
-# Usage
-usage() {
-    echo "Usage: $0 [options]"
-    echo "Options:"
-    echo "  -s, --source PATH    Source claude-simone path (default: $SOURCE_PATH)"
-    echo "  -t, --target PATH    Target project path (default: current directory)"
-    echo "  -d, --dry-run        Show what would be synced without doing it"
-    echo "  -h, --help           Show this help message"
-    exit 1
-}
-
-# Parse arguments
-DRY_RUN=""
-while [[ $# -gt 0 ]]; do
-    case $1 in
-        -s|--source)
-            SOURCE_PATH="$2"
-            shift 2
-            ;;
-        -t|--target)
-            TARGET_PATH="$2"
-            shift 2
-            ;;
-        -d|--dry-run)
-            DRY_RUN="--dry-run"
-            shift
-            ;;
-        -h|--help)
-            usage
-            ;;
-        *)
-            echo "Unknown option: $1"
-            usage
-            ;;
-    esac
-done
-
-# Verify source exists
-if [ ! -d "$SOURCE_PATH/.simone" ]; then
-    echo -e "${RED}Error: Source path doesn't appear to be a claude-simone repository${NC}"
-    echo "Path: $SOURCE_PATH"
-    exit 1
-fi
-
-# Verify target exists
-if [ ! -d "$TARGET_PATH/.simone" ]; then
-    echo -e "${RED}Error: Target path doesn't appear to have Simone installed${NC}"
-    echo "Path: $TARGET_PATH"
-    exit 1
-fi
-
-# Show what we're doing
-echo -e "${GREEN}Simone Framework Sync${NC}"
-echo "Source: $SOURCE_PATH"
-echo "Target: $TARGET_PATH"
-if [ -n "$DRY_RUN" ]; then
-    echo -e "${YELLOW}DRY RUN MODE - No changes will be made${NC}"
-fi
-echo ""
-
-# Function to sync a component
-sync_component() {
-    local component=$1
-    local description=$2
-    
-    echo -e "${GREEN}Syncing $description...${NC}"
-    
-    # Build rsync command
-    if [[ "$component" == *"***" ]]; then
-        # It's a directory with contents
-        rsync -av $DRY_RUN \
-            --include="$component" \
-            --exclude='/*' \
-            "$SOURCE_PATH/" "$TARGET_PATH/"
-    else
-        # It's a single file
-        rsync -av $DRY_RUN \
-            "$SOURCE_PATH/$component" "$TARGET_PATH/$component"
-    fi
-}
-
-# Sync commands
-sync_component "/.claude/commands/simone/***" "Claude commands"
-
-# Sync templates  
-sync_component "/.simone/99_TEMPLATES/***" "Project templates"
-
-# Sync framework docs
-echo -e "${GREEN}Syncing framework documentation...${NC}"
-rsync -av $DRY_RUN \
-    "$SOURCE_PATH/.simone/CLAUDE.MD" \
-    "$SOURCE_PATH/.simone/README.md" \
-    "$TARGET_PATH/.simone/"
-
-# Create new directories if needed
-echo -e "${GREEN}Ensuring directory structure...${NC}"
-if [ -z "$DRY_RUN" ]; then
-    mkdir -p "$TARGET_PATH/.simone/10_STATE_OF_PROJECT"
-    echo "Created: .simone/10_STATE_OF_PROJECT/"
-else
-    echo "Would create: .simone/10_STATE_OF_PROJECT/"
-fi
-
-# Summary
-echo ""
-echo -e "${GREEN}Sync complete!${NC}"
-if [ -n "$DRY_RUN" ]; then
-    echo -e "${YELLOW}This was a dry run. Run without -d to apply changes.${NC}"
-else
-    echo "Framework components have been updated."
-    echo ""
-    echo "Next steps:"
-    echo "1. Test a few commands to ensure everything works"
-    echo "2. Review SYNC_GUIDE.md for any manual steps"
-    echo "3. Commit the framework updates"
-fi