@meltstudio/meltctl 2.0.2 → 2.1.0

package/README.md

@@ -120,12 +120,13 @@ This tool is part of the Melt Development Process. For issues or contributions:
 The CLI uses a bundled template system organized in:
 
 ```
-packages/cli/templates/
-├── cursor-commands/     # All 8 Cursor AI command templates
-├── melt-memory/        # Project context templates with dynamic timestamps
-└── melt-scripts/       # Utility scripts for sh and PowerShell
-    ├── sh/            # Bash/zsh utility scripts
-    └── ps/            # PowerShell utility scripts
+packages/cli/
+├── memory/            # Project context and standards
+├── scripts/           # Utility scripts for sh and PowerShell
+│   ├── sh/            # Bash/zsh utility scripts
+│   └── ps/            # PowerShell utility scripts
+└── templates/
+    └── cursor-commands/ # All 8 Cursor AI command templates
 ```
 
 Templates support dynamic content replacement (like timestamps) and are copied to your project during initialization.

package/dist/commands/project/init.js

@@ -80,17 +80,11 @@ export async function initCommand(options = {}) {
         console.log(`  • ${chalk.cyan('.melt/templates/')}`);
         console.log();
         console.log('Next steps:');
-        console.log('  1. Start using Cursor commands (8 commands available):');
-        console.log(`     • ${chalk.cyan('/melt-plan')} - Create detailed implementation plans`);
-        console.log(`     • ${chalk.cyan('/melt-test-plan')} - Generate test strategy and test files`);
-        console.log(`     • ${chalk.cyan('/melt-docs')} - Update project documentation`);
-        console.log(`     • ${chalk.cyan('/melt-implement')} - Execute implementation with best practices`);
-        console.log(`     • ${chalk.cyan('/melt-pr')} - Create pull request with proper description`);
-        console.log(`     • ${chalk.cyan('/melt-review')} - Review code for quality and compliance`);
-        console.log(`     • ${chalk.cyan('/melt-complete')} - Complete story and handle deployment`);
-        console.log(`     • ${chalk.cyan('/melt-debug')} - Systematic debugging with AI assistance`);
-        console.log('  2. Customize templates in .melt/templates/');
-        console.log(`  3. Use utility scripts in .melt/scripts/${selectedShell}/`);
+        console.log('  1. Open Cursor IDE');
+        console.log(`  2. Run ${chalk.cyan('/melt-plan')} to start planning a feature`);
+        console.log('  3. Follow the workflow: Plan → Test → Implement → Review');
+        console.log();
+        console.log(`See docs: ${chalk.cyan('https://melt-development-prompts.vercel.app')}`);
         outro(chalk.green('Happy coding with Melt! 🚀'));
     }
     catch (error) {
@@ -125,22 +119,21 @@ async function copyTemplates(baseDir, shell) {
     if (existsSync(cursorCommandsTemplateDir)) {
         fs.copySync(cursorCommandsTemplateDir, cursorCommandsDestDir);
     }
-    // Create initial context file from template
-    const contextTemplatePath = join(templatesDir, 'melt-memory', 'context.md');
+    // Create initial context file from memory
+    const contextSourcePath = join(__dirname, '../../../memory', 'context.md');
     const contextDestPath = join(baseDir, '.melt', 'memory', 'context.md');
-    if (existsSync(contextTemplatePath)) {
-        let contextContent = readFileSync(contextTemplatePath, 'utf8');
+    if (existsSync(contextSourcePath)) {
+        let contextContent = readFileSync(contextSourcePath, 'utf8');
         // Replace timestamp placeholders
         const timestamp = new Date().toISOString();
         contextContent = contextContent.replace(/{{timestamp}}/g, timestamp);
         fs.writeFileSync(contextDestPath, contextContent, 'utf8');
     }
-    // Copy shell script from template
-    const scriptExt = shell === 'ps' ? 'ps1' : 'sh';
-    const scriptTemplatePath = join(templatesDir, 'melt-scripts', shell, `common.${scriptExt}`);
-    const scriptDestPath = join(baseDir, '.melt', 'scripts', shell, `common.${scriptExt}`);
-    if (existsSync(scriptTemplatePath)) {
-        fs.copySync(scriptTemplatePath, scriptDestPath);
+    // Copy shell scripts from CLI package
+    const scriptsSourceDir = join(__dirname, '../../../scripts', shell);
+    const scriptsDestDir = join(baseDir, '.melt', 'scripts', shell);
+    if (existsSync(scriptsSourceDir)) {
+        fs.copySync(scriptsSourceDir, scriptsDestDir);
     }
 }
 function createVersionFile(meltDir) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@meltstudio/meltctl",
-  "version": "2.0.2",
+  "version": "2.1.0",
   "description": "CLI tool for Melt development process automation - initialize and update project configurations",
   "main": "dist/index.js",
   "type": "module",

package/templates/cursor-commands/melt-plan.md

@@ -1,15 +1,25 @@
 ---
-description: Create implementation plan following Melt's domain-driven architecture standards
+description: Create implementation plan with User Story and RFC validation following Melt's domain-driven architecture standards
+scripts:
+  sh: .melt/scripts/sh/get-plan-context.sh --json
+  ps: .melt/scripts/ps/get-plan-context.ps1 -Json
 ---
 
 Create a comprehensive implementation plan for the requested feature. Follow these steps:
 
-1. **Analyze Requirements**:
-   - Read `.melt/memory/context.md` for project context and constraints
+1. **Collect Requirements**:
+   - Run `{SCRIPT}` from the project root and parse JSON for USER_STORY, RFC, ISSUE_ID, PLAN_FILE, and PROJECT_ROOT
+   - If script fails, prompt manually for User Story and RFC
+   - Validate that both User Story and RFC are complete and actionable
+
+2. **Analyze Requirements**:
+   - Analyze the provided User Story for clear acceptance criteria and user value
+   - Review the RFC for technical decisions, architecture, and constraints
+   - Read `.melt/memory/context.md` for additional project context
    - Identify the target domain(s) this feature belongs to
    - Determine integration points with existing domains
 
-2. **Architecture Planning**:
+3. **Architecture Planning**:
    - Design domain structure following our patterns:
      ```
      src/domains/[domain]/
@@ -23,27 +33,28 @@ Create a comprehensive implementation plan for the requested feature. Follow the
    - Plan component hierarchy and state management
    - Design data flow and API integration points
 
-3. **Technical Decisions**:
+4. **Technical Decisions**:
    - Choose appropriate React patterns (server vs client components)
    - Plan Zod schemas for data validation
    - Design TypeScript interfaces and types
    - Plan testing strategy (unit, integration, e2e)
 
-4. **Implementation Strategy**:
+5. **Implementation Strategy**:
    - Break down into atomic, testable units
    - Identify dependencies and execution order
    - Plan for error handling and edge cases
    - Consider accessibility and performance requirements
 
-5. **Create Detailed Plan**:
+6. **Create Detailed Plan**:
    - List specific files to create/modify
    - Define component interfaces and props
    - Specify API endpoints and data contracts
    - Plan test cases and coverage targets
 
-6. **Save Planning Output**:
-   - Save comprehensive plan to `.melt/outputs/plans/[timestamp]-plan.md`
-   - Update `.melt/memory/context.md` with planning decisions
-   - Create task breakdown for implementation
+7. **Save Planning Output**:
+   - Save comprehensive plan to the PLAN_FILE path provided by the script
+   - Include User Story and RFC as context sections in the plan
+   - Update `.melt/memory/context.md` with planning decisions and issue reference
+   - Create task breakdown for implementation with clear dependencies
 
 Focus on maintainable, testable code that follows our domain-driven architecture principles.

package/templates/melt-memory/context.md

@@ -1,23 +0,0 @@
-# Project Context
-
-## Project Overview
-This project uses Melt's development standards with domain-driven architecture.
-
-## Architecture Principles
-- **Domain-Driven Design**: Code organized by business domains
-- **React 2025 Standards**: Functional components, hooks, TypeScript strict
-- **Type Safety**: Zod schemas for runtime validation
-- **Testing**: 80% coverage minimum with comprehensive test strategies
-
-## Development Workflow
-1. **Plan**: Create implementation plans in `.melt/outputs/plans/`
-2. **Implement**: Follow domain architecture patterns
-3. **Review**: Ensure quality and compliance
-4. **Debug**: Systematic problem-solving approach
-
-## Current Status
-- Initialized: {{timestamp}}
-- Last Updated: {{timestamp}}
-
-## Notes
-Update this file as the project evolves to maintain context for AI assistants and team members.

package/templates/melt-scripts/ps/common.ps1

@@ -1,48 +0,0 @@
-#!/usr/bin/env pwsh
-# Common utilities for Melt development workflow
-
-function Get-ProjectRoot {
-    try {
-        git rev-parse --show-toplevel
-    }
-    catch {
-        Get-Location
-    }
-}
-
-function Get-Timestamp {
-    Get-Date -Format "yyyyMMdd-HHmmss"
-}
-
-function Test-MeltWorkspace {
-    if (-not (Test-Path ".melt" -PathType Container)) {
-        Write-Error "ERROR: .melt workspace not found. Run 'meltctl project init' first."
-        exit 1
-    }
-}
-
-function New-OutputFile {
-    param(
-        [string]$Category,
-        [string]$Name
-    )
-
-    $timestamp = Get-Timestamp
-    $filename = "$timestamp-$Name.md"
-    $filepath = ".melt/outputs/$Category/$filename"
-
-    New-Item -Path ".melt/outputs/$Category" -ItemType Directory -Force | Out-Null
-    return $filepath
-}
-
-function Update-Context {
-    param([string]$Message)
-
-    $timestamp = Get-Date -Format "yyyy-MM-ddTHH:mm:ssK"
-
-    Add-Content -Path ".melt/memory/context.md" -Value "## Update: $timestamp"
-    Add-Content -Path ".melt/memory/context.md" -Value $Message
-    Add-Content -Path ".melt/memory/context.md" -Value ""
-}
-
-Write-Output "Melt development utilities loaded."

package/templates/melt-scripts/sh/common.sh

@@ -1,44 +0,0 @@
-#!/usr/bin/env bash
-# Common utilities for Melt development workflow
-
-# Get project root directory
-get_project_root() {
-    git rev-parse --show-toplevel 2>/dev/null || pwd
-}
-
-# Get current timestamp for file naming
-get_timestamp() {
-    date '+%Y%m%d-%H%M%S'
-}
-
-# Check if .melt directory exists
-check_melt_workspace() {
-    if [[ ! -d ".melt" ]]; then
-        echo "ERROR: .melt workspace not found. Run 'meltctl project init' first."
-        exit 1
-    fi
-}
-
-# Create output file with timestamp
-create_output_file() {
-    local category="$1"
-    local name="$2"
-    local timestamp=$(get_timestamp)
-    local filename="${timestamp}-${name}.md"
-    local filepath=".melt/outputs/${category}/${filename}"
-
-    mkdir -p ".melt/outputs/${category}"
-    echo "$filepath"
-}
-
-# Update context file with new information
-update_context() {
-    local message="$1"
-    local timestamp=$(date -Iseconds)
-
-    echo "## Update: $timestamp" >> .melt/memory/context.md
-    echo "$message" >> .melt/memory/context.md
-    echo "" >> .melt/memory/context.md
-}
-
-echo "Melt development utilities loaded."