aiwf 0.3.8 → 0.3.12

package/claude-code/aiwf/en/.claude/commands/aiwf/aiwf_create_general_task.md

@@ -1,147 +0,0 @@
-# Create General Task - Top-Down Execution
-
-Creates a new general task in `.aiwf/04_GENERAL_TASKS/` following project documentation standards.
-
-## Create a TODO with EXACTLY these 10 Items
-
-1. Parse task arguments and determine task ID
-2. Load project context and documentation requirements
-3. Verify task doesn't duplicate existing work
-4. Research codebase for implementation context
-5. Create task file using standard template
-6. Fill in task details with proper context
-7. Add technical guidance and codebase references
-8. Update project manifest with new task
-9. Validate task alignment with architecture
-10. Perform final quality check and report
-
-## DETAILS on every TODO item
-
-### 1. Parse task arguments and determine task ID
-
-The argument format is: `<Task Title or Description>`
-
-- If arguments are empty, prompt user for task details
-- Generate sequential task ID by examining existing tasks in `.aiwf/04_GENERAL_TASKS/`
-- Find highest task number (T###) and increment by 1
-- Format: `T###_<Task_Title_Snake_Case>.md`
-- **IMPORTANT:** Task IDs must be sequential with no gaps
-
-### 2. Load project context and documentation requirements
-
-Use PARALLEL SUBAGENTS to READ and UNDERSTAND the project's context:
-
-- READ `.aiwf/00_PROJECT_MANIFEST.md` - Get current project state
-- READ `.aiwf/01_PROJECT_DOCS/ARCHITECTURE.md` - Understand system constraints
-- READ `.aiwf/01_PROJECT_DOCS/LONG_TERM_VISION.md` - Understand future direction
-- READ latest files in `.aiwf/10_STATE_OF_PROJECT/` - Review current state
-- SCAN `.aiwf/05_ARCHITECTURE_DECISIONS/` for relevant ADRs
-- **IMPORTANT:** General tasks must align with documented architecture
-
-### 3. Verify task doesn't duplicate existing work
-
-**SEARCH** comprehensively for potential duplicates:
-
-- Check all files in `.aiwf/04_GENERAL_TASKS/`
-- Search sprint tasks in `.aiwf/03_SPRINTS/*/T*.md`
-- Look for similar functionality in completed milestones
-- **CRITICAL:** If duplicate found, stop and report to user with file reference
-
-### 4. Research codebase for implementation context
-
-Based on the task description, use PARALLEL SUBAGENTS to:
-
-- SEARCH for existing patterns similar to what the task requires
-- IDENTIFY key interfaces, classes, or modules that will be affected
-- FIND examples of similar implementations in the codebase
-- LOCATE relevant test patterns and existing test files
-- DISCOVER error handling and logging patterns used
-- MAP OUT integration points with existing code
-- **DOCUMENT** all findings for inclusion in task
-
-### 5. Create task file using standard template
-
-**USE** the task template in `.aiwf/99_TEMPLATES/task_template.md` as base structure:
-
-- Copy template structure exactly
-- Place file in `.aiwf/04_GENERAL_TASKS/T###_<Title>.md`
-- Include timestamp: Execute `date '+%Y-%m-%d %H:%M:%S'` for creation time
-- **IMPORTANT:** Follow template structure precisely - no deviations
-
-### 6. Fill in task details with proper context
-
-Populate the task file with:
-
-- **Title**: Clear, actionable task name
-- **Context**: Link to architecture docs and project state
-- **Requirements**: Specific, measurable outcomes
-- **Acceptance Criteria**: Clear definition of done
-- **Dependencies**: Reference relevant sprints/milestones
-- **Implementation Notes**: Technical approach aligned with architecture
-- **CRITICAL:** All content must reference existing documentation
-
-### 7. Add technical guidance and codebase references
-
-**Technical Guidance section:**
-
-- Key interfaces and integration points discovered in step 4
-- Specific imports and module references from codebase
-- Existing patterns to follow (with file references)
-- Database models or API contracts to work with
-- Error handling approach used in similar code
-- Testing patterns found in the codebase
-
-**Implementation Notes section:**
-
-- Step-by-step implementation approach based on research
-- Key architectural decisions to respect (reference ADRs)
-- Specific files and functions to modify or extend
-- Testing approach based on existing test patterns
-- Performance considerations if relevant
-
-**IMPORTANT:** Do NOT include code examples. Provide structural guidance and file references only.
-
-### 8. Update project manifest with new task
-
-**UPDATE** `.aiwf/00_PROJECT_MANIFEST.md`:
-
-- Add task to "## General Tasks" section
-- Format: `- [ ] T###: [Task Title] - Status: Not Started`
-- Maintain alphabetical/numerical ordering
-- Link to task file: `[T###](04_GENERAL_TASKS/T###_Title.md)`
-- **IMPORTANT:** Preserve all existing content
-
-### 9. Validate task alignment with architecture
-
-**VERIFY** task compliance:
-
-- Check task doesn't contradict architecture principles
-- Ensure implementation approach uses established patterns
-- Validate dependencies exist and are correct
-- Confirm task scope is appropriate (not too broad/narrow)
-- Technical guidance aligns with existing codebase patterns
-- **CRITICAL:** Documentation is source of truth - any deviation needs justification
-
-### 10. Perform final quality check and report
-
-**QUALITY CHECK**:
-
-- Task file follows template completely
-- All sections properly filled including new technical guidance
-- References to documentation and codebase are valid
-- Task ID is sequential and unique
-- Manifest updated correctly
-- Technical guidance references actual files and patterns
-- No scope creep or architecture violations
-
-**OUTPUT FORMAT**:
-
-```markdown
-✅ **Created**: T###\_<Title>.md
-📋 **Type**: General Task
-🎯 **Purpose**: [One-line summary]
-📚 **References**: [Key documentation links]
-🔧 **Key Integration Points**: [Main files/modules to modify]
-🧪 **Test Approach**: [Testing pattern to follow]
-⏭️ **Next Step**: Review task details and run `/do_task T###` to begin
-```

package/claude-code/aiwf/en/.claude/commands/aiwf/aiwf_create_milestone_plan.md

@@ -1,194 +0,0 @@
-# Create Milestone Plan - Top-Down Execution
-
-Creates a new milestone with proper structure, documentation, and project integration through an interactive, adaptive process.
-
-## Create a TODO with EXACTLY these 8 items
-
-1. Parse arguments and analyze project context
-2. Interactive milestone scoping and definition
-3. Determine milestone structure and naming
-4. Create milestone directory and meta file
-5. Guide supporting documentation creation
-6. Update project manifest with milestone
-7. Validate milestone coherence and alignment
-8. Report milestone creation and next steps
-
----
-
-## 1 · Parse arguments and analyze project context
-
-**CRITICAL:** You are given additional Arguments: <$ARGUMENTS>
-
-**USE PARALLEL SUBAGENTS** to do these tasks:
-
-- Parse arguments for suggested milestone name/focus (defaults to interactive creation)
-- Read `.aiwf/00_PROJECT_MANIFEST.md` to understand current project state
-- Scan `.aiwf/02_REQUIREMENTS/` to identify existing milestones and numbering
-- Read `.aiwf/01_PROJECT_DOCS/ARCHITECTURE.md` to understand project scope
-- Check latest project review in `.aiwf/10_STATE_OF_PROJECT/` for current status
-- **IMPORTANT:** Understand project phase and what logical next milestone should be
-
-## 2 · Interactive milestone scoping and definition
-
-**Conversational milestone definition:**
-
-If arguments provided:
-
-- "I see you want to create a milestone for: [arguments]"
-- "Let me understand the scope better..."
-
-If no arguments:
-
-- "Let's define your next milestone based on the current project state"
-- "I see you're currently on [current milestone] - what should we focus on next?"
-
-**Interactive questions (adapt based on context):**
-
-- "What's the main goal of this milestone?"
-- "What key deliverables should be completed?"
-- "Are there any specific technical challenges or requirements?"
-- "How does this milestone advance the project toward its long-term vision?"
-- "What would 'done' look like for this milestone?"
-
-**Keep conversational and adaptive** - don't interrogate, just gather what's needed
-
-## 3 · Determine milestone structure and naming
-
-**Generate milestone details:**
-
-- Determine next milestone number (M##) by scanning existing milestones
-- Create descriptive milestone name from user input
-- Format: `M##_Milestone_Name_Snake_Case`
-- **CRITICAL:** Ensure no duplicate milestone numbers
-- Validate naming follows AIWF conventions (underscores, no spaces)
-
-**Confirm with user:**
-
-- "I'll create milestone: M##\_[Name] - does this sound right?"
-- Allow user to adjust name or numbering if needed
-
-## 4 · Create milestone directory and meta file
-
-**Create milestone structure:**
-
-- Create directory: `.aiwf/02_REQUIREMENTS/M##_Milestone_Name/`
-- Copy template from `.aiwf/99_TEMPLATES/milestone_meta_template.md`
-- Create milestone meta file: `M##_milestone_meta.md`
-
-**Populate milestone meta file:**
-
-- Fill in YAML frontmatter:
-  - `milestone_id: M##`
-  - `title: [Milestone Name]`
-  - `status: pending`
-  - `last_updated: [current timestamp YYYY-MM-DD HH:MM]`
-- Convert user input into structured sections:
-  - **Goals**: Clear objectives from user discussion
-  - **Key Documents**: Placeholder for PRD and SPECS files
-  - **Definition of Done**: Specific, measurable criteria from user input
-  - **Notes/Context**: Additional context from user discussion
-
-## 5 · Guide supporting documentation creation
-
-**Interactive document planning:**
-
-Based on milestone scope, suggest needed documents:
-
-- "For this milestone, you'll likely need:"
-- "□ PRD\_[Milestone_Name].md - Product requirements"
-- "□ SPECS\_[Technical_Area].md - Technical specifications"
-- "□ Any domain-specific documentation"
-
-**Ask user:**
-
-- "Would you like me to create starter templates for these documents now?"
-- "Or would you prefer to create them manually as needed?"
-
-**If user wants templates created:**
-
-- Create basic PRD template with milestone-specific sections
-- Create SPECS template if technical milestone
-- Include proper cross-references between documents
-- **IMPORTANT:** Don't over-engineer - create useful starting points
-
-**If user prefers manual:**
-
-- Note in milestone meta what documents are expected
-- Provide guidance on when/how to create them
-
-## 6 · Update project manifest with milestone
-
-**UPDATE** `.aiwf/00_PROJECT_MANIFEST.md`:
-
-- Add milestone to milestones section:
-  - Format: `- [ ] M##: [Milestone Name] - Status: Planning`
-  - Link: `[M##](02_REQUIREMENTS/M##_Milestone_Name/M##_milestone_meta.md)`
-- Update project metadata:
-  - Set `current_milestone` if this is the active milestone
-  - Update `highest_milestone` number
-  - Update `last_updated` timestamp
-- **IMPORTANT:** Preserve all existing content and formatting
-
-## 7 · Validate milestone coherence and alignment
-
-**VERIFY** milestone quality:
-
-- Check milestone aligns with project architecture and vision
-- Ensure Definition of Done is specific and measurable
-- Validate milestone scope is appropriate (not too broad/narrow)
-- Confirm milestone advances project toward stated goals
-- Check milestone numbering and naming follows conventions
-- Verify all created files follow template structure
-- **CRITICAL:** Milestone should be independently valuable and achievable
-
-**THINK ABOUT**:
-
-- Does this milestone make sense given the current project state?
-- Are the goals realistic and well-scoped?
-- Is the Definition of Done clear enough to know when it's complete?
-- Does this milestone set up future milestones logically?
-
-## 8 · Report milestone creation and next steps
-
-**OUTPUT FORMAT**:
-
-```markdown
-✅ **Milestone Created**: M##\_[Milestone_Name]
-
-📋 **Milestone Details**:
-
-- ID: M##
-- Title: [Milestone Name]
-- Status: Planning
-- Focus: [One-line summary of main goal]
-
-📚 **Created Documents**:
-
-- Milestone meta: `02_REQUIREMENTS/M##_[Name]/M##_milestone_meta.md`
-- [Any additional documents created]
-
-🎯 **Definition of Done**:
-
-- [Key DoD criteria from milestone]
-
-📈 **Project Impact**:
-
-- Updates project from M[previous] to M##
-- Advances toward: [project vision alignment]
-
-⏭️ **Recommended Next Steps**:
-
-- Review milestone details: `02_REQUIREMENTS/M##_[Name]/M##_milestone_meta.md`
-- Create supporting documentation as planned
-- Break down into sprints: `/project:aiwf:create_sprints_from_milestone M##`
-- Update with specific requirements as they become clear
-
-🎯 **Ready for Development**: Use `/project:aiwf:create_sprints_from_milestone M##` when ready to start implementation planning
-```
-
-**IMPORTANT NOTES**:
-
-- Keep milestone scope focused and achievable
-- Definition of Done should be measurable
-- Supporting documents can be created as needed
-- Milestone planning is iterative - refine as you learn more

package/claude-code/aiwf/en/.claude/commands/aiwf/aiwf_create_prd.md

@@ -1,272 +0,0 @@
-# Generate Product Documentation Workflow
-
-This rule guides AI to collect input through several key questions, then **sequentially** generate PRD → IA → UCD → UI/UX documents. All outputs use **Markdown** format.
-
----
-
-## 1. Question Phase
-
-AI collects the following information from the user through **questions**:
-
-1. `<product-overview>`
-2. `<references>` (List of URLs)
-3. `<must-features>` (List of must-have features)
-4. `<target-user-persona>`
-5. `<target-platforms>`
-6. `<storage-type>`
-7. `<tech-stack>`
-
-> ⚠️ All questions are in English, and if needed, request additional reference service or competitive product information.
-
----
-
-## 2. PRD Writing Phase
-
-After collecting all inputs from the user, create a PRD document based on the following **sample prompt** structure:
-
-```prompt
-Write a PRD document based on the following information:
-<product-overview>
-${productOverview}
-</product-overview>
-<references>
-${references}
-</references>
-<must-features>
-${mustFeatures}
-</must-features>
-<target-user-persona>
-${persona}
-</target-user-persona>
-<target-platforms>
-${platforms}
-</target-platforms>
-<storage-type>
-${storageType}
-</storage-type>
-<tech-stack>
-${techStack}
-</tech-stack>
-PRD must include the following contents:
-<table-of-contents>
-- Detailed product description
-- Reference Services with detailed rationale
-- Core features and specifications
-- Suggested additional features
-- User persona and scenarios
-- Technical stack recommendations
-</table-of-contents>
-<response-format>
-Use markdown format
-</response-format>
-<guidelines>
-- Use tables or lists where appropriate to organize information systematically.
-- Provide accurate answers with reliable references
-- Clearly separate each section
-- Collect additional reference services and provide detailed rationale
-- Do not include detailed data structure and storage design
-</guidelines>
-```
-
-Additional instructions to include in the document:
-
-- Use tables or lists where appropriate to organize information systematically.
-- Include at least 3 reference services, with detailed rationale for each.
-
-After completing the PRD, append a **English** question asking if the user wants to proceed to the IA phase, with a message "✅ PRD completed".
-
----
-
-## 3. IA(Information Architecture) Writing Phase
-
-If the user chooses to continue, create an IA document based on the following information:
-
-The IA document should include:
-
-1. **Site Map** – Represented as a tree structure
-2. **Content Inventory** – List of key content for each page
-3. **User Flow** – Provide at least 2 core scenarios in text-based flowchart format
-4. **Navigation Structure and URL Patterns**
-
-Document format: Markdown, English
-
-### IA Sample Prompt
-
-```prompt
-Write an Information Architecture document based on PRD, and following information:
-<navigation-type>
-${navigationType}
-</navigation-type>
-<auth-type>
-${authType}
-</auth-type>
-IA document must include the following contents:
-<table-of-contents>
-- Site Map
-- User Flow
-- Navigation Structure
-- Page Hierarchy
-- Content Organization
-- Interaction Patterns
-- URL Structure
-- Component Hierarchy
-</table-of-contents>
-<response-format>
-Use markdown format
-</response-format>
-<guidelines>
-- Use tables or lists where appropriate to organize information systematically
-- Provide accurate answers with reliable references
-- Clearly separate each section
-- Consider user experience and accessibility
-- Include responsive design considerations
-- Consider SEO best practices
-</guidelines>
-```
-
-After completing the IA, append a **English** question asking if the user wants to proceed to the UCD phase, with a message "✅ IA completed".
-
----
-
-## 4. UCD(User-Centered Design) Writing Phase
-
-The UCD document should include:
-
-1. **Main Persona** – 2-3 personas, summarized in a table (goals, motivations, pain points)
-2. **Scenarios** – At least 2 core scenarios per persona
-3. **Requirements Matrix** – Mapping of features to personas
-
-Document format: Markdown, English
-
-### UCD Sample Prompt
-
-```prompt
-Write a detailed use case document based on PRD, IA, and following information:
-Use case document must include the following contents:
-<table-of-contents>
-- Actor Definitions
-- Use Case Scenarios
-- Main Steps
-- Exception Handling
-- Comprehensive Actor Definitions
-- Detailed Use Case Scenarios
-- Main Steps and Flow of Events
-- Alternative Flows and Edge Cases
-- Preconditions and Postconditions
-- Business Rules and Constraints
-- Exception Handling Procedures
-- User Interface Considerations
-- Data Requirements and Data Flow
-- Security and Privacy Considerations
-</table-of-contents>
-<response-format>
-Use markdown format
-</response-format>
-<guidelines>
-- Use tables or lists where appropriate to organize information systematically
-- Provide accurate answers with reliable references
-- Clearly separate each section
-- Include detailed step-by-step descriptions
-- Consider error cases and alternative flows
-- Include technical considerations
-</guidelines>
-```
-
-After completing the UCD, append a **English** question asking if the user wants to proceed to the UI/UX phase, with a message "✅ UCD completed".
-
----
-
-## 5. UI/UX Guide Writing Phase
-
-내용:
-
-1. **Wireframe Description** – Layout and components of each core screen (text description)
-2. **Navigation Principles** – Description of consistent UI patterns
-3. **Style Guide Draft** – Color palette, typography, component rules
-4. **Accessibility Considerations** – WCAG 2.1 compliance key points
-
-Document format: Markdown, English
-
-### UI/UX Sample Prompt
-
-```prompt
-<role>
-senior UI/UX designer.
-</role>
-<task>
-Write a comprehensive UI/UX design guide based on the following information:
-</task>
-<design-preferences>
-Theme details: Please analyze the reference service and suggest appropriate:
-- Design style
-- Color scheme
-- Primary colors
-</design-preferences>
-<references>
-${references}
-</references>
-<additional-instructions>
-Please analyze the reference service's design system and suggest appropriate:
-- Overall design style and patterns
-- Color scheme and palette
-- Primary colors
-- Mood and atmosphere
-</additional-instructions>
-Design guide must include the following contents:
-<table-of-contents>
-- Design System Overview
-- Color Palette for tailwindcss (primary, secondary, accent, neutral, etc.)
-- Page Implementations
-  detailed design guide for each pages
-  - core purpose of the page
-  - key components
-  - layout structure
-- Layout Components
-  - applicable routes
-  - core components
-  - responsive behavior
-- Interaction Patterns
-- Breakpoints
-</table-of-contents>
-<breakpoints>
-$breakpoints: (
-├── 'mobile': 320px,
-├── 'tablet': 768px,
-├── 'desktop': 1024px,
-└── 'wide': 1440px
-);
-</breakpoints>
-<response-format>
-Use markdown format
-</response-format>
-<guidelines>
-- Use tables or lists where appropriate to organize information systematically
-- Considering color scheme, select proper color for each color in tailwindcss palette
-- Provide specific color codes
-- Provide rationale for design decisions
-- Always include responsive design considerations
-- Include all text content in UI
-- If needed, use enough images in each components
-- provide each image's url. Use stock photos from picsum.photos where appropriate, only valid URLs you know exist
-- must handle root route
-- consider proper grid system for all components
-</guidelines>
-```
-
-After completing all documents, inform the user with a message "🎉 All documents created" and guide them to the next step (sprint/task decomposition).
-
----
-
-## 6. Sprint/Task Decomposition Preparation
-
-After all documents are completed, inform the user that AI can automatically create development sprints and tasks using the `yolo` or `create_sprints_from_milestone` commands.
-
----
-
-### Example Usage
-
-1. AI → Question Phase
-2. User → Provide Information
-3. AI → PRD Creation, IA Progress Question
-4. User → "Continue"
-5. AI → IA Creation, UCD Progress Question … Repeat