aiwf 0.3.7 → 0.3.12

package/.aiwf/99_TEMPLATES/feature_template.md

@@ -1,263 +0,0 @@
----
-feature_id: FL###
-title: [Feature Title]
-status: active
-created_date: YYYY-MM-DD
-last_updated: YYYY-MM-DD HH:MM
-
-# Milestone & Sprint Association
-milestone: M##
-sprint_ids: []
-tasks: []
-
-# Team & Assignment
-assignee: [username]
-contributors: []
-reviewers: []
-
-# Classification
-priority: medium  # critical | high | medium | low
-complexity: moderate  # simple | moderate | complex
-category: feature  # feature | enhancement | bugfix | refactor
-tags: []
-
-# Time Tracking
-estimated_hours: 0
-actual_hours: 0
-estimated_completion: YYYY-MM-DD
-actual_completion: null
-
-# Git Integration
-git_branch: feature/FL###-feature-name
-git_commits: []
-pull_requests: []
-
-# Dependencies
-depends_on: []
-blocks: []
-
-# Progress Tracking
-progress_percentage: 0
-checklist_items_total: 0
-checklist_items_completed: 0
-
-# Risk & Issues
-risk_level: low  # low | medium | high
-known_issues: []
-mitigation_plans: []
-
-# Additional Metadata
-external_links: []
-notes: ""
----
-
-# Feature: [Feature Title]
-
-## Overview
-
-[Provide a brief description of the feature, its purpose, and the value it brings to the project. This should be 2-3 sentences that clearly explain what the feature does and why it's needed.]
-
-## Background & Context
-
-[Explain the business or technical context that led to this feature. Include any relevant background information, user feedback, or strategic decisions that influenced this feature's creation.]
-
-## Requirements
-
-### Functional Requirements
-- [ ] [Requirement 1: Clear, specific, and testable]
-- [ ] [Requirement 2: User-facing functionality]
-- [ ] [Requirement 3: Business logic or rules]
-
-### Non-Functional Requirements
-- [ ] Performance: [Specific metrics or goals]
-- [ ] Security: [Security requirements or constraints]
-- [ ] Usability: [User experience requirements]
-- [ ] Compatibility: [Browser, device, or system requirements]
-
-### Acceptance Criteria
-- [ ] [Specific condition that must be met for feature acceptance]
-- [ ] [Another measurable criteria]
-- [ ] [User acceptance test scenario]
-
-## Technical Design
-
-### Architecture Overview
-
-[Describe how this feature fits into the overall system architecture. Include any architectural patterns or principles being followed.]
-
-### Components Affected
-
-1. **Frontend**
-   - [List affected UI components]
-   - [New components to be created]
-
-2. **Backend**
-   - [API endpoints impacted]
-   - [Services or modules affected]
-
-3. **Database**
-   - [Schema changes required]
-   - [New tables or collections]
-
-### API Specifications
-
-#### New Endpoints
-
-```
-[Method] /api/v1/[endpoint]
-Description: [What this endpoint does]
-Request Body: {
-  // JSON schema
-}
-Response: {
-  // JSON schema
-}
-```
-
-#### Modified Endpoints
-
-[List any existing endpoints that need modification]
-
-### Data Model Changes
-
-```
-[Describe new or modified data structures]
-```
-
-### Security Considerations
-
-- Authentication: [How users will be authenticated]
-- Authorization: [Access control requirements]
-- Data Protection: [Encryption or privacy requirements]
-
-## Implementation Plan
-
-### Phase 1: Foundation
-- [ ] Set up basic infrastructure
-- [ ] Create database schema
-- [ ] Implement core business logic
-
-### Phase 2: Integration
-- [ ] Integrate with existing systems
-- [ ] Implement API endpoints
-- [ ] Create UI components
-
-### Phase 3: Polish
-- [ ] Add error handling
-- [ ] Implement logging and monitoring
-- [ ] Performance optimization
-
-## Testing Strategy
-
-### Unit Tests
-- [ ] Business logic tests
-- [ ] Data validation tests
-- [ ] Error handling tests
-
-### Integration Tests
-- [ ] API endpoint tests
-- [ ] Database integration tests
-- [ ] External service integration tests
-
-### End-to-End Tests
-- [ ] User workflow tests
-- [ ] Cross-browser compatibility tests
-- [ ] Performance tests
-
-### User Acceptance Testing
-- [ ] Test scenario 1: [Description]
-- [ ] Test scenario 2: [Description]
-- [ ] Test scenario 3: [Description]
-
-## Rollout Plan
-
-### Feature Flags
-- Flag name: `[feature_name_enabled]`
-- Default state: disabled
-- Rollout stages:
-  1. Internal testing (5%)
-  2. Beta users (25%)
-  3. General availability (100%)
-
-### Monitoring & Metrics
-- [ ] Error rate monitoring
-- [ ] Performance metrics
-- [ ] User engagement metrics
-- [ ] Business impact metrics
-
-### Rollback Plan
-- [ ] Feature flag disable procedure
-- [ ] Database rollback scripts
-- [ ] Communication plan
-
-## Dependencies
-
-### External Dependencies
-- [ ] Third-party services: [List any external APIs or services]
-- [ ] Libraries: [List new libraries or packages needed]
-- [ ] Infrastructure: [Any infrastructure requirements]
-
-### Internal Dependencies
-- [ ] Features that must be completed first: [List feature IDs]
-- [ ] Shared components needed: [List components]
-- [ ] Team dependencies: [Other teams involved]
-
-## Risks & Mitigation
-
-### Technical Risks
-| Risk | Impact | Probability | Mitigation |
-|------|--------|-------------|------------|
-| [Risk description] | High/Medium/Low | High/Medium/Low | [Mitigation strategy] |
-
-### Business Risks
-| Risk | Impact | Probability | Mitigation |
-|------|--------|-------------|------------|
-| [Risk description] | High/Medium/Low | High/Medium/Low | [Mitigation strategy] |
-
-## Documentation
-
-### Developer Documentation
-- [ ] API documentation
-- [ ] Code comments and inline docs
-- [ ] Architecture decision records
-
-### User Documentation
-- [ ] User guide updates
-- [ ] FAQ entries
-- [ ] Video tutorials (if applicable)
-
-## Success Metrics
-
-- [ ] [Metric 1]: Target value and measurement method
-- [ ] [Metric 2]: Target value and measurement method
-- [ ] [Metric 3]: Target value and measurement method
-
-## Timeline
-
-- Start Date: YYYY-MM-DD
-- Target Completion: YYYY-MM-DD
-- Key Milestones:
-  - [ ] Milestone 1: [Date] - [Description]
-  - [ ] Milestone 2: [Date] - [Description]
-  - [ ] Milestone 3: [Date] - [Description]
-
-## Notes & Decisions
-
-[Record any important decisions made during planning or implementation, along with the reasoning behind them.]
-
-## References
-
-- [Link to PRD or requirements document]
-- [Link to design mockups]
-- [Link to technical specifications]
-- [Link to related features]
-
----
-
-## Activity Log
-
-[This section is automatically updated as work progresses]
-
-### YYYY-MM-DD
-- Feature ledger created
-- Initial planning completed

package/.aiwf/99_TEMPLATES/milestone_meta_template.md

@@ -1,25 +0,0 @@
----
-milestone_id: M<ID>
-title: Milestone Title
-status: pending # pending | active | completed | blocked | on_hold
-last_updated: YYYY-MM-DD HH:MM
----
-
-## Milestone: {{ title }}
-
-### Goals
-- Clearly define the primary objectives of this milestone.
-- What should be achieved by the end of this milestone?
-
-### Key Documents
-
-List the main requirement documents associated with this milestone (e.g., PRD, Technical Specifications).
-
-- `PRD_<Milestone_Name>.md`
-- `SPECS_<Milestone_Name>.md`
-
-### Definition of Done (DoD)
-- Specific, measurable criteria that must be met for this milestone to be considered complete.
-
-### Notes / Context (Optional)
-- Any additional context, high-level strategy, or important notes related to this milestone for Claude.

package/.aiwf/99_TEMPLATES/project_manifest_template.md

@@ -1,39 +0,0 @@
----
-project_name: {{project_name}}
-current_milestone_id: {{current_milestone_id}}
-highest_sprint_in_milestone: {{highest_sprint_in_milestone}}
-current_sprint_id: {{current_sprint_id}}
-status: active
-last_updated: {{timestamp}}
----
-
-# Project Manifest: {{project_name}}
-
-This manifest serves as the central reference point for the project. It tracks the current focus and links to key documentation.
-
-## 1. Project Vision & Overview
-
-{{project_vision}}
-
-This project follows a milestone-based development approach.
-
-## 2. Current Focus
-
-- **Milestone:** {{current_milestone_id}} - {{current_milestone_name}}
-- **Sprint:** {{current_sprint_id}} - {{current_sprint_name}}
-
-## 3. Sprints in Current Milestone
-
-{{sprint_list}}
-
-## 4. Key Documentation
-
-- [Architecture Documentation](./01_PROJECT_DOCS/ARCHITECTURE.md)
-- [Current Milestone Requirements](./02_REQUIREMENTS/{{current_milestone_id}}_{{current_milestone_slug}}/)
-- [General Tasks](./04_GENERAL_TASKS/)
-
-## 5. Quick Links
-
-- **Current Sprint:** [{{current_sprint_id}} Sprint Folder](./03_SPRINTS/{{current_sprint_id}}_{{current_milestone_id}}_{{current_sprint_slug}}/)
-- **Active Tasks:** Check sprint folder for T##_{{current_sprint_id}}_*.md files
-- **Project Reviews:** [Latest Review](./10_STATE_OF_PROJECT/)

package/.aiwf/99_TEMPLATES/sprint_meta_template.md

@@ -1,23 +0,0 @@
----
-sprint_folder_name: S<SprintSequenceID>_M<MilestoneID>_<Short_Name>
-sprint_sequence_id: S<ID>
-milestone_id: M<ID>
-title: Sprint Title - Focus of this Sprint
-status: pending # pending | active | completed | aborted
-goal: Clearly state the primary objective of this sprint.
-last_updated: YYYY-MM-DDTHH:MM:SSZ
----
-
-# Sprint: {{ title }} ({{ sprint_sequence_id }})
-
-## Sprint Goal
-{{ goal }}
-
-## Scope & Key Deliverables (Optional)
-- What specific features, fixes, or outcomes are targeted in this sprint for Claude to work on?
-
-## Definition of Done (for the Sprint) (Optional)
-- What conditions must be met for the sprint itself to be considered successfully completed?
-
-## Notes / Retrospective Points (Optional)
-- Any specific notes for this sprint.

package/.aiwf/99_TEMPLATES/task_template.md

@@ -1,36 +0,0 @@
----
-task_id: T<TaskNN>_S<SprintSequenceID> # For Sprint Tasks (e.g., T01_S01) OR T<NNN> for General Tasks (e.g., T501)
-sprint_sequence_id: S<ID> # e.g., S01 (If part of a sprint, otherwise null or absent)
-status: open # open | in_progress | pending_review | done | failed | blocked
-complexity: Medium # Low | Medium | High
-last_updated: YYYY-MM-DDTHH:MM:SSZ
-github_issue: # Optional: GitHub issue number (e.g., #123)
----
-
-# Task: (Filename serves as the descriptive title)
-
-## Description
-Briefly explain what this task is about. Provide necessary context to understand the 'why' behind the task.
-
-## Goal / Objectives
-Clearly state what needs to be achieved by completing this task. What does success look like?
-- Objective 1
-- Objective 2
-
-## Acceptance Criteria
-Specific, measurable conditions that must be met for this task to be considered 'done'.
-- [ ] Criterion 1 is met.
-- [ ] Criterion 2 is verified.
-
-## Subtasks
-A checklist of smaller steps to complete this task.
-- [ ] Subtask 1
-- [ ] Subtask 2
-
-## Output Log
-*(This section is populated as work progresses on the task)*
-
-[YYYY-MM-DD HH:MM:SS] Started task
-[YYYY-MM-DD HH:MM:SS] Modified files: file1.js, file2.js
-[YYYY-MM-DD HH:MM:SS] Completed subtask: Implemented feature X
-[YYYY-MM-DD HH:MM:SS] Task completed

package/.aiwf/CLAUDE.md

@@ -1,76 +0,0 @@
-# CLAUDE.md - AIWF Framework Structure Guide
-
-Always communicate in Korean
-
-## Overview
-
-This is the root directory of the AIWF framework structure. It contains all project documentation, requirements, sprints, and organizational files.
-
-## Critical Files
-
-### Project Manifest
-
-**IMPORTANT**: The project manifest file MUST be named:
-
-```
-00_PROJECT_MANIFEST.md
-```
-
-**NOT**:
-
-- ❌ `MANIFEST.md`
-- ❌ `PROJECT_MANIFEST.md`
-- ❌ `project_manifest.md`
-
-The manifest is the central reference file that tracks:
-
-- Project name and status
-- Current milestone and sprint
-- Project metadata
-- Last updated timestamp
-
-## Directory Structure
-
-```
-.AIWF/
-├── 00_PROJECT_MANIFEST.md          # Central project reference (CORRECT NAME)
-├── 01_PROJECT_DOCS/                # General project documentation
-├── 02_REQUIREMENTS/                # Milestone-based requirements
-├── 03_SPRINTS/                     # Sprint execution folders
-├── 04_GENERAL_TASKS/               # Non-sprint tasks
-├── 05_ARCHITECTURAL_DECISIONS/     # ADR documentation
-├── 10_STATE_OF_PROJECT/            # Project review snapshots
-└── 99_TEMPLATES/                   # Document templates
-```
-
-## Naming Conventions Summary
-
-### Files
-
-- **Project Manifest**: `00_PROJECT_MANIFEST.md`
-- **Milestone Meta**: `M##_milestone_meta.md`
-- **Sprint Meta**: `S##_M##_sprint_meta.md`
-- **Task Files**: `TASK_##_*.md`
-- **ADR Files**: `ADR_###_*.md`
-
-### Folders
-
-- **Milestones**: `M##_Milestone_Name/`
-- **Sprints**: `S##_M##_Sprint_Name/`
-- **State Snapshots**: `YYYY-MM-DD_HH-MM_snapshot/`
-
-## Important Notes for Claude Code
-
-1. **Always create `00_PROJECT_MANIFEST.md`** when initializing a project
-2. **Use the templates** from `99_TEMPLATES/` for consistency
-3. **Follow the naming conventions exactly** - they enable proper sorting and navigation
-4. **Update the manifest** when creating milestones or sprints
-5. **Use underscores** for spaces in folder and file names
-
-## Common Initialization Mistakes
-
-- Creating `MANIFEST.md` instead of `00_PROJECT_MANIFEST.md`
-- Missing the leading zeros in numbered prefixes
-- Using hyphens instead of underscores
-- Creating files without using templates
-- Not updating the manifest after structural changes

package/.aiwf/ai-tools/README.md

@@ -1,105 +0,0 @@
-# AIWF AI Tool Integration Templates
-
-This directory contains integration templates for various AI development tools to work seamlessly with the AI Workflow Framework (AIWF).
-
-## Available Tools
-
-### 1. Claude Code (`claude-code`)
-- **Description**: Official Anthropic Claude Code integration
-- **Features**: Deep AIWF integration, feature ledger sync, AI personas
-- **Installation**: `aiwf ai-tool install claude-code`
-
-### 2. GitHub Copilot (`github-copilot`)
-- **Description**: GitHub Copilot configuration for AIWF projects
-- **Features**: Feature-aware suggestions, sprint task integration
-- **Installation**: `aiwf ai-tool install github-copilot`
-
-### 3. Cursor (`cursor`)
-- **Description**: Cursor IDE integration with AIWF
-- **Features**: Multi-file context, composer enhancement, task tracking
-- **Installation**: `aiwf ai-tool install cursor`
-
-### 4. Windsurf (`windsurf`)
-- **Description**: Windsurf IDE with Cascade AI integration
-- **Features**: Flow-based development, multi-agent support, visual progress
-- **Installation**: `aiwf ai-tool install windsurf`
-
-### 5. Augment (`augment`)
-- **Description**: Augment Code with deep codebase understanding
-- **Features**: Team collaboration, knowledge queries, smart refactoring
-- **Installation**: `aiwf ai-tool install augment`
-
-## Quick Start
-
-1. **List available tools**:
-   ```bash
-   aiwf ai-tool list
-   ```
-
-2. **Install a tool**:
-   ```bash
-   aiwf ai-tool install <tool-name>
-   ```
-
-3. **Update installed tools**:
-   ```bash
-   aiwf ai-tool update <tool-name>
-   ```
-
-4. **Verify installation**:
-   ```bash
-   aiwf ai-tool verify <tool-name>
-   ```
-
-## Integration Features
-
-All templates provide:
-- ✅ Feature Ledger integration
-- ✅ AI Persona support
-- ✅ Sprint task management
-- ✅ Context optimization
-- ✅ Offline cache support
-
-## Directory Structure
-
-```
-ai-tools/
-├── claude-code/
-│   ├── template/
-│   ├── config.json
-│   └── README.md
-├── github-copilot/
-│   ├── template/
-│   ├── config.json
-│   └── README.md
-├── cursor/
-│   ├── template/
-│   ├── config.json
-│   └── README.md
-├── windsurf/
-│   ├── template/
-│   ├── config.json
-│   └── README.md
-└── augment/
-    ├── template/
-    ├── config.json
-    └── README.md
-```
-
-## Customization
-
-Each tool template can be customized:
-1. Edit the template files in the tool directory
-2. Modify config.json for tool-specific settings
-3. Add project-specific rules to the template files
-
-## Support
-
-For issues or questions:
-- Check individual tool README files
-- Visit [AIWF Documentation](https://aiwf.dev)
-- Submit issues on GitHub
-
----
-
-*AIWF AI Tool Integration System v1.0.0*