aiwf 0.1.0 → 0.3.0

package/COMMANDS_GUIDE.md

@@ -1,462 +0,0 @@
-# Moonklabs 명령어 가이드
-
-이 가이드는 사용 가능한 Moonklabs 명령어와 이를 프로젝트에서 효과적으로 사용하는 방법을 설명합니다.
-
-## 명령어 개요
-
-Moonklabs 명령어는 `/project:moonklabs:<command_name> [arguments]` 형식을 따릅니다.
-
-## 설정 및 컨텍스트 명령어
-
-### 🚀 `/project:moonklabs:initialize`
-
-**목적**: 새 프로젝트 또는 기존 프로젝트에서 Moonklabs 초기화
-
-**사용법**:
-
-```
-/project:moonklabs:initialize
-```
-
-**동작**:
-
-1. Scans and analyzes your project
-2. Asks for confirmation about project type
-3. Checks for existing Moonklabs documents
-4. Guides you through document creation (imports existing docs or creates new ones)
-5. Creates your first milestone
-6. Generates project manifest
-
-**사용 시기**: 프로젝트에서 Moonklabs를 처음 설정할 때(현재 ForeLoop에는 이미 설정되어 있습니다!)
-
----
-
-### 🧠 `/project:moonklabs:prime`
-
-**목적**: 코딩 세션 시작 시 프로젝트 컨텍스트를 로드합니다
-
-**사용법**:
-
-```
-/project:moonklabs:prime
-```
-
-**동작**:
-
-- 프로젝트 매니페스트를 읽음
-- 현재 마일스톤 및 스프린트 정보를 로드
-- 활성 작업을 식별
-- 빠른 상태 개요를 제공
-
-**사용 시기**: 코딩 세션을 시작할 때 전체 상황을 빠르게 파악할 때
-
-## 계획 명령어
-
-### 📅 `/project:moonklabs:create_sprints_from_milestone`
-
-**목적**: 마일스톤을 관리 가능한 스프린트로 분해
-
-**사용법**:
-
-```
-/project:moonklabs:create_sprints_from_milestone 001_MVP_FOUNDATION
-```
-
-**동작**:
-
-1. 마일스톤 요구사항을 분석
-2. 관련 요구사항을 약 1주 길이의 스프린트로 그룹화
-3. 스프린트 폴더 및 META 파일 생성
-4. 스프린트 정보를 매니페스트에 업데이트
-
-**사용 시기**: 새로운 마일스톤을 생성한 후
-
----
-
-### 📋 `/project:moonklabs:create_sprint_tasks`
-
-**목적**: 스프린트를 위한 상세 작업 분해 생성
-
-**사용법**:
-
-```
-/project:moonklabs:create_sprint_tasks S01
-# or for specific sprint:
-/project:moonklabs:create_sprint_tasks S02_001_MVP_FOUNDATION
-```
-
-**동작**:
-
-1. 스프린트 요구사항을 분석
-2. 이를 구체적이고 실행 가능한 작업으로 분해
-3. 목표가 명확한 작업 파일을 생성
-4. 작업 간 종속성을 처리
-
-**사용 시기**: 각 스프린트 시작 시
-
----
-
-### ✏️ `/project:moonklabs:create_general_task`
-
-**목적**: 스프린트와 연결되지 않은 독립형 작업 생성
-
-**사용법**:
-
-```
-/project:moonklabs:create_general_task
-# Then describe your task when prompted
-```
-
-**예시 작업**:
-
-- "Fix memory leak in physics engine"
-- "Update documentation for API changes"
-- "Refactor database connection pooling"
-
-**사용 시기**: 유지보수, 버그 수정 또는 스프린트 범위를 벗어난 작업에 사용
-
-## Development Commands
-
-### 💻 `/project:moonklabs:do_task`
-
-**목적**: 특정 작업을 실행
-
-**사용법**:
-
-```
-/project:moonklabs:do_task
-# 사용 가능한 작업을 나열하고 선택을 요청
-
-# 또는 작업을 직접 지정:
-/project:moonklabs:do_task T001_S01_setup_tauri
-```
-
-**동작**:
-
-1. Reads task requirements
-2. Implements the solution
-3. Runs tests if applicable
-4. Updates task status
-5. Creates necessary files/changes
-
-**사용 시기**: Ready to work on a specific task
-
----
-
-### 📝 `/project:moonklabs:commit`
-
-**목적**: Create well-structured git commits
-
-**사용법**:
-
-```
-/project:moonklabs:commit
-# 변경 사항을 검토하고 커밋을 생성
-
-# 또는 특정 작업에 대해:
-/project:moonklabs:commit T001_S01_setup_tauri
-
-# 리뷰와 함께:
-/project:moonklabs:commit --review
-```
-
-**동작**:
-
-1. Analyzes changes made
-2. Groups related changes
-3. Creates meaningful commit messages
-4. Links commits to tasks/requirements
-5. Optionally runs code review first
-
-**사용 시기**: After completing work you want to save
-
----
-
-### 🧪 `/project:moonklabs:test`
-
-**목적**: Run tests and fix common issues
-
-**사용법**:
-
-```
-/project:moonklabs:test
-# 모든 테스트 실행
-
-/project:moonklabs:test unit
-# 특정 테스트 스위트 실행
-```
-
-**동작**:
-
-1. Identifies test commands from package.json
-2. Runs appropriate tests
-3. Fixes common issues (missing deps, configs)
-4. Reports results clearly
-
-**사용 시기**: Before committing or when tests fail
-
-## 코드 리뷰 명령어
-
-### 🔍 `/project:moonklabs:code_review`
-
-**목적**: Review code against specifications
-
-**사용법**:
-
-```
-/project:moonklabs:code_review
-# 커밋되지 않은 변경 사항 검토
-
-/project:moonklabs:code_review src/app/components/GameCanvas.tsx
-# Reviews specific file
-```
-
-**동작**:
-
-1. Checks code against requirements
-2. Verifies patterns and conventions
-3. Identifies bugs and issues
-4. Suggests improvements
-5. Ensures spec compliance
-
-**사용 시기**: Before committing important changes
-
----
-
-### 📊 `/project:moonklabs:project_review`
-
-**목적**: Comprehensive project health check
-
-**사용법**:
-
-```
-/project:moonklabs:project_review
-```
-
-**동작**:
-
-1. Reviews overall architecture
-2. Checks technical debt
-3. Analyzes progress vs. timeline
-4. Identifies risks and blockers
-5. Suggests improvements
-
-**사용 시기**: Weekly or at sprint boundaries
-
----
-
-### 🧪 `/project:moonklabs:testing_review`
-
-**목적**: Analyze test coverage and quality
-
-**사용법**:
-
-```
-/project:moonklabs:testing_review
-```
-
-**동작**:
-
-1. Reviews test coverage
-2. Identifies missing test cases
-3. Checks test quality
-4. Suggests improvements
-
-**사용 시기**: After implementing features
-
----
-
-### 💬 `/project:moonklabs:discuss_review`
-
-**목적**: Technical discussion about review findings
-
-**사용법**:
-
-```
-/project:moonklabs:discuss_review
-# After running another review command
-```
-
-**동작**:
-
-- Provides detailed explanations
-- Discusses trade-offs
-- Suggests solutions
-- Answers questions
-
-**사용 시기**: To understand review feedback better
-
-## 자동화 명령어
-
-### 🚀 `/project:moonklabs:yolo`
-
-**목적**: Autonomous task execution
-
-**사용법**:
-
-```
-/project:moonklabs:yolo
-# 모든 열린 작업을 순차 실행
-
-/project:moonklabs:yolo S02
-# 특정 스프린트를 순차 실행
-```
-
-**동작**:
-
-1. Identifies open tasks
-2. Executes them in order
-3. Handles dependencies
-4. Commits completed work
-5. Updates progress
-
-**Safety features**:
-
-- Won't modify schemas without confirmation
-- Skips dangerous operations
-- Maintains code quality
-- Creates logical commits
-
-**사용 시기**: When you want autonomous progress
-
-## 추가/고급 명령어
-
-### 📌 `/project:moonklabs:pr_create`
-
-**목적**: Pull Request를 생성하고 템플릿을 적용하여 변경 사항을 정리합니다.
-
-**사용법**:
-
-```
-/project:moonklabs:pr_create "Add authentication to API"
-```
-
----
-
-### 🗂️ `/project:moonklabs:issue_create`
-
-**목적**: GitHub Issue를 생성하여 버그 리포트·기능 요청을 기록합니다.
-
-**사용법**:
-
-```
-/project:moonklabs:issue_create "Bug: login fails on Safari"
-```
-
----
-
-### 🛠️ `/project:moonklabs:plan_milestone`
-
-**목적**: 대화형 프로세스로 신규 마일스톤을 계획하고 `.moonklabs/02_REQUIREMENTS/` 구조를 자동 생성합니다.
-
----
-
-### 📈 `/project:moonklabs:mermaid`
-
-**목적**: 코드베이스를 분석하여 Mermaid 다이어그램(UML/시퀀스 등)을 생성합니다.
-
----
-
-### ♾️ `/project:moonklabs:infinite`
-
-**목적**: 명세에 따라 무한(또는 지정 횟수) 반복 결과물을 생성하는 고급 반복 생성 루프를 실행합니다.
-
----
-
-### 🤖 `/project:moonklabs:tm-run-all-subtask`
-
-**목적**: Task Master의 모든 서브태스크를 한 번에 실행하여 진행 상황을 자동화합니다.
-
----
-
-### 🧠 `/project:moonklabs:ultrathink_general`
-
-**목적**: 폭넓은 문제를 심층 분석하기 위한 울트라 씽킹(General) 세션을 시작합니다.
-
----
-
-### 🧠 `/project:moonklabs:ultrathink_code_basic`
-
-**목적**: 코드 기반 문제를 기본 수준에서 심층 분석하는 울트라 씽킹 세션을 시작합니다.
-
----
-
-### 🧠 `/project:moonklabs:ultrathink_code_advanced`
-
-**목적**: 복잡한 코드·아키텍처 문제를 고급 수준에서 심층 분석하는 울트라 씽킹 세션을 시작합니다.
-
----
-
-### ⚙️ `/project:moonklabs:prime_context`
-
-**목적**: 프로젝트 컨텍스트(파일 목록·주요 문서)를 빠르게 불러와 프라임합니다.
-
-## 모범 사례
-
-### 일일 워크플로
-
-```bash
-# Start of day
-/project:moonklabs:prime
-
-# Work on tasks
-/project:moonklabs:do_task
-/project:moonklabs:test
-/project:moonklabs:commit
-
-# End of day
-/project:moonklabs:project_review
-```
-
-### 스프린트 워크플로
-
-```bash
-# Sprint planning
-/project:moonklabs:create_sprint_tasks S02
-
-# Sprint execution
-/project:moonklabs:do_task T001_S02_first_task
-/project:moonklabs:do_task T002_S02_second_task
-/project:moonklabs:commit --review
-
-# Sprint review
-/project:moonklabs:project_review
-```
-
-### 빠른 수정
-
-```bash
-# Bug fix workflow
-/project:moonklabs:create_general_task
-# Describe: "Fix memory leak in /src/foo.bar"
-/project:moonklabs:do_task T003
-/project:moonklabs:test
-/project:moonklabs:commit T003
-```
-
-## 팁 & 트릭
-
-1. **Use YOLO for routine tasks**: Great for implementing straightforward features
-2. **Always prime first**: Ensures commands have proper context
-3. **Review before major commits**: Catch issues early
-4. **Create general tasks for bugs**: Keeps them trackable
-5. **Use task-specific commits**: Better traceability
-
-## 명령어 안전 장치
-
-Moonklabs commands include safety features:
-
-- Won't delete critical files
-- Asks before schema changes
-- Validates changes against specs
-- Maintains code quality standards
-- Creates incremental commits
-
-## 도움 받기
-
-If you need help with a command:
-
-1. Run the command without arguments for usage info
-2. Check this guide
-3. Look at task examples in `.moonklabs/`
-4. Review the command source in `.claude/commands/`

package/claude-code/simone/.simone/04_GENERAL_TASKS/CLAUDE.MD

@@ -1,51 +0,0 @@
-# General Tasks Instructions
-
-## General Task Structure
-
-General tasks are standalone work items not tied to sprints:
-
-- Files follow pattern: `T<NNN>_<Description>.md`
-- Completed tasks: `TX<NNN>_<Description>.md`
-
-Always use the template at `.simone/99_TEMPLATES/task_template.md` when creating new general tasks.
-
-## Task Formatting
-
-General tasks use standardized YAML frontmatter and sections:
-
-```yaml
----
-task_id: T001
-status: open # open | in_progress | pending_review | done | failed | blocked
-complexity: Medium # Low | Medium | High
-last_updated: YYYY-MM-DD HH:MM
----
-```
-
-The full task structure with all sections is defined in the task template. Always maintain this structure.
-
-## Working with General Tasks
-
-When handling general tasks:
-
-1. Update the status field as you progress
-2. Record timestamps in this format (YYYY-MM-DD HH:MM)
-3. Log all significant actions in the Output Log section:
-
-   ```plaintext
-   [YYYY-MM-DD HH:MM] Started task
-   [YYYY-MM-DD HH:MM] Modified files: file1.js, file2.js
-   ```
-
-4. Mark subtasks as they're completed: `- [x] Completed subtask`
-5. Use the Acceptance Criteria as your primary completion checklist
-6. Ensure all sections from the task template are preserved
-
-## Task Completion Process
-
-When a task is complete:
-
-1. Update status to "done"
-2. Update all Acceptance Criteria with [x]
-3. Add final Output Log entry
-4. Rename file from T... to TX... (e.g., `TX001_Task_Name.md`)

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.