@atlashub/smartstack-cli 1.3.0 → 1.4.1

package/templates/commands/business-analyse.md

@@ -1,11 +1,46 @@
 ---
 description: Business Analysis - Complete business analysis workflow (BABOK/IEEE 830)
+argument-hint: "<description du besoin>"
 ---
 
 # Business Analysis - Expert Workflow
 
 Senior Business Analyst expert. Complete business analysis without writing code.
 
+---
+
+## MODE AUTOMATIQUE (RECOMMANDE)
+
+```
++==============================================================================+
+|  /business-analyse "<description du besoin>"                                 |
+|                                                                              |
+|  ORCHESTRE AUTOMATIQUEMENT TOUT LE WORKFLOW:                                 |
+|  ├── 1. Verification MCP SmartStack (alerte si absent)                       |
+|  ├── 2. Analyse du contexte (Application/Module/Granularite)                 |
+|  ├── 3. Definition des integrations (Workflows/Notifs/IA)                    |
+|  ├── 4. Creation prd.json + progress.txt (Ralph Loop ready)                  |
+|  ├── 5. Execution phases 1-7 avec Ralph Loop                                 |
+|  ├── 6. Validation utilisateur (gate obligatoire)                            |
+|  ├── 7. Implementation avec Ralph Loop                                       |
+|  └── 8. Documentation HTML auto-generee                                      |
+|                                                                              |
+|  RESULTAT: Feature complete en ~30 minutes avec validation                   |
++==============================================================================+
+```
+
+**Usage:**
+```bash
+# Mode automatique complet (RECOMMANDE)
+/business-analyse "Je veux gerer les contacts clients avec import/export"
+
+# Mode manuel (phases individuelles)
+/business-analyse:1-init
+/business-analyse:2-discover ...
+```
+
+---
+
 ## Philosophy
 
 ```
@@ -91,7 +126,9 @@ Examples:
 
 | Phase | Command | Model | Description | Output |
 |-------|----------|-------|-------------|--------|
-| 0 | *Validation* | - | Context business check (automatic) | Block if not business |
+| **AUTO** | **`/business-analyse`** | **opus** | **Orchestration complete automatique** | **Feature complete** |
+| 0 | `/business-analyse:0-orchestrate` | opus | Orchestration manuelle avec questions | context.json, prd.json |
+| 0.5 | *Validation* | - | Context business check (automatic) | Block if not business |
 | 1 | `/business-analyse:1-init` | haiku | Initialize project structure + code scan | `config.json`, structure |
 | 2 | `/business-analyse:2-discover` | **opus** | Requirements elicitation (ultrathink) | `1-discovery.md` |
 | 3 | `/business-analyse:3-analyse` | sonnet | Business analysis BRD + doc scan (ultrathink) | `2-business-requirements.md` |
@@ -552,8 +589,52 @@ The skill is triggered automatically when user asks about:
 
 ## Next
 
-Execute the following command to begin:
-
+**Mode automatique (RECOMMANDE):**
+```bash
+/business-analyse "Description de votre besoin"
 ```
+
+**Mode manuel:**
+```bash
 /business-analyse:1-init
 ```
+
+---
+
+## EXECUTION AUTOMATIQUE
+
+Si cette commande est appelee avec un argument (description du besoin):
+
+```
+ARGUMENTS = "$ARGUMENTS"
+
+SI ARGUMENTS non vide:
+  → Executer /business-analyse:0-orchestrate $ARGUMENTS
+  → Le workflow complet est lance automatiquement
+
+SINON:
+  → Afficher ce fichier d'aide
+  → Proposer les options
+```
+
+**Lancer le mode automatique maintenant:**
+
+```javascript
+if (ARGUMENTS && ARGUMENTS.trim().length > 0) {
+  // Mode automatique - lancer l'orchestration
+  execute("/business-analyse:0-orchestrate " + ARGUMENTS);
+} else {
+  // Mode manuel - afficher l'aide et proposer les options
+  AskUserQuestion({
+    questions: [{
+      question: "Comment souhaitez-vous proceder?",
+      header: "Mode",
+      options: [
+        { label: "Mode automatique (Recommande)", description: "Orchestration complete avec Ralph Loop" },
+        { label: "Mode manuel", description: "Executer les phases une par une" }
+      ],
+      multiSelect: false
+    }]
+  });
+}
+```

package/templates/commands/create/agent.md

@@ -0,0 +1,138 @@
+---
+description: Create a SmartStack agent extension project
+argument-hint: <name> [description]
+---
+
+# Create Agent Extension
+
+Scaffold a complete SmartStack **agent** extension project.
+
+## What is an Agent?
+
+An agent is a specialized execution unit:
+- Launched by commands for parallel execution
+- Focused on specific tasks (search, analysis, etc.)
+- Defined in markdown with YAML frontmatter
+- Optimized with model selection (haiku/sonnet/opus)
+
+## Arguments
+
+Parse from `$ARGUMENTS`:
+- **name** (required): Agent name in kebab-case
+- **description** (optional): What the agent does
+
+## Project Structure
+
+```
+smartstack-{name}/
+├── package.json
+├── tsconfig.json
+├── tsup.config.ts
+├── README.md
+├── .gitignore
+├── src/
+│   └── index.ts
+└── templates/
+    └── agents/
+        └── {name}.md          # Agent template
+```
+
+## Generated Agent Template
+
+Create `templates/agents/{name}.md`:
+
+```markdown
+---
+name: {name}
+description: {description}
+color: yellow
+model: haiku
+---
+
+# {PascalCaseName} Agent
+
+{description}
+
+## Purpose
+
+This agent specializes in:
+- [Primary capability 1]
+- [Primary capability 2]
+- [Primary capability 3]
+
+## Search Strategy
+
+### 1. Initial Discovery
+- Use `Glob` to find files matching patterns
+- Focus on: `**/*.{relevant-extensions}`
+
+### 2. Deep Analysis
+- Use `Grep` for specific code patterns
+- Look for: `pattern1`, `pattern2`
+
+### 3. Context Building
+- Use `Read` to examine key files
+- Extract: imports, exports, dependencies
+
+### 4. Synthesis
+- Compile findings
+- Identify patterns
+- Generate recommendations
+
+## Output Format
+
+**CRITICAL**: Output findings directly in response. NEVER create files.
+
+### Findings Report
+
+#### Relevant Files
+| File | Purpose | Key Patterns |
+|------|---------|--------------|
+| path/to/file | description | patterns found |
+
+#### Analysis
+[Detailed analysis of findings]
+
+#### Recommendations
+1. [First recommendation]
+2. [Second recommendation]
+3. [Third recommendation]
+
+## Tool Usage
+
+Preferred tools for this agent:
+- `Glob` - File discovery
+- `Grep` - Pattern search
+- `Read` - File content
+
+## Anti-Patterns
+
+- **NEVER** create markdown files
+- **NEVER** guess without evidence
+- **NEVER** skip verification
+- **ALWAYS** cite specific file paths
+
+## Priority
+
+Accuracy > Completeness > Speed
+```
+
+## Model Selection Guide
+
+| Use Case | Model | Reason |
+|----------|-------|--------|
+| Simple search | haiku | Fast, cheap |
+| Analysis | sonnet | Good balance |
+| Complex reasoning | opus | Best quality |
+
+## Workflow
+
+1. Parse name and description from `$ARGUMENTS`
+2. Validate name is kebab-case
+3. Create project directory
+4. Generate all files using Write tool
+5. Display success message
+
+---
+
+User: $ARGUMENTS

package/templates/commands/create/command.md

@@ -0,0 +1,166 @@
+---
+description: Create a SmartStack command extension project
+argument-hint: <name> [description]
+---
+
+# Create Command Extension
+
+Scaffold a complete SmartStack **command** extension project.
+
+## What is a Command?
+
+A command is a slash command that users invoke in Claude Code:
+- `/my-command <args>` - Executes the command with arguments
+- Defined in markdown with YAML frontmatter
+- Contains workflow, rules, and execution logic
+
+## Arguments
+
+Parse from `$ARGUMENTS`:
+- **name** (required): Command name in kebab-case
+- **description** (optional): What the command does
+
+## Project Structure
+
+```
+smartstack-{name}/
+├── package.json
+├── tsconfig.json
+├── tsup.config.ts
+├── README.md
+├── .gitignore
+├── src/
+│   └── index.ts
+└── templates/
+    └── commands/
+        └── {name}.md          # Main command template
+```
+
+## Generated Command Template
+
+Create `templates/commands/{name}.md`:
+
+```markdown
+---
+description: {description}
+argument-hint: <task-description>
+---
+
+# {PascalCaseName}
+
+{description}
+
+## Workflow
+
+### 1. UNDERSTAND
+- Parse user arguments: `$ARGUMENTS`
+- Identify the task scope
+- Gather necessary context
+
+### 2. ANALYZE
+- Explore relevant codebase areas
+- Identify patterns and constraints
+- Document findings
+
+### 3. PLAN
+- Design the approach
+- Consider edge cases
+- Validate against requirements
+
+### 4. EXECUTE
+- Implement step by step
+- Follow existing patterns
+- Write clean code
+
+### 5. VERIFY
+- Test the implementation
+- Ensure no regressions
+- Validate completeness
+
+## Execution Rules
+
+1. **ULTRA THINK** before each phase
+2. Use parallel agents when beneficial
+3. Document all decisions
+4. **MINIMAL CHANGES**: Only what's needed
+5. Test before declaring complete
+
+## Agent Usage
+
+For exploration, launch agents:
+- `explore-codebase` - Find relevant files
+- `websearch` - Research solutions
+
+## Priority
+
+Understanding > Correctness > Speed
+
+---
+
+User: $ARGUMENTS
+```
+
+## Generated Files
+
+### package.json
+
+```json
+{
+  "name": "@smartstack/{name}",
+  "version": "1.0.0",
+  "description": "{description}",
+  "private": false,
+  "type": "module",
+  "main": "./dist/index.js",
+  "files": ["dist", "templates"],
+  "scripts": {
+    "build": "tsup",
+    "dev": "tsup --watch"
+  },
+  "peerDependencies": {
+    "@atlashub/smartstack-cli": ">=1.0.0"
+  }
+}
+```
+
+### src/index.ts
+
+```typescript
+import * as path from 'path';
+import * as fs from 'fs';
+
+export function getTemplatesPath(): string {
+  return path.join(__dirname, '..', 'templates');
+}
+
+export async function install(targetDir: string): Promise<void> {
+  const src = path.join(getTemplatesPath(), 'commands');
+  const dest = path.join(targetDir, 'commands');
+  // Copy command templates
+}
+
+export const metadata = {
+  name: '{name}',
+  version: '1.0.0',
+  description: '{description}',
+  type: 'command'
+};
+```
+
+## Workflow
+
+1. Parse name and description from `$ARGUMENTS`
+2. Validate name is kebab-case
+3. Create project directory
+4. Generate all files using Write tool
+5. Display success message with next steps
+
+## Validation
+
+- Name must match: `^[a-z][a-z0-9-]*$`
+- Directory must not exist
+- Description should be meaningful
+
+---
+
+User: $ARGUMENTS

package/templates/commands/create/hook.md

@@ -0,0 +1,234 @@
+---
+description: Create a SmartStack hook extension project
+argument-hint: <name> [trigger] [description]
+---
+
+# Create Hook Extension
+
+Scaffold a complete SmartStack **hook** extension project.
+
+## What is a Hook?
+
+A hook is a validation/action trigger:
+- Runs automatically at specific points (pre-commit, pre-merge, etc.)
+- Can block operations if issues detected
+- Defined in markdown with detection patterns
+- Integrates with GitFlow workflow
+
+## Arguments
+
+Parse from `$ARGUMENTS`:
+- **name** (required): Hook name in kebab-case
+- **trigger** (optional): pre-commit | pre-merge | pre-push | post-commit
+- **description** (optional): What the hook validates
+
+## Project Structure
+
+```
+smartstack-{name}/
+├── package.json
+├── tsconfig.json
+├── tsup.config.ts
+├── README.md
+├── .gitignore
+├── src/
+│   └── index.ts
+└── templates/
+    └── hooks/
+        └── {name}.md          # Hook template
+```
+
+## Generated Hook Template
+
+```markdown
+---
+description: {description}
+trigger: {trigger}
+blocking: true
+---
+
+# {PascalCaseName} Hook
+
+{description}
+
+## Purpose
+
+This hook validates [what it validates] before allowing [the action].
+
+## Trigger Points
+
+| Trigger | When | Blocking |
+|---------|------|----------|
+| pre-commit | Before git commit | Yes |
+| pre-merge | Before branch merge | Yes |
+| pre-push | Before git push | Yes |
+| post-commit | After git commit | No |
+
+Current trigger: **{trigger}**
+
+## Detection Patterns
+
+### BLOCKING Patterns
+
+These patterns will **prevent** the operation:
+
+| Pattern | File Types | Risk Level | Reason |
+|---------|-----------|------------|--------|
+| `PATTERN_ONE` | *.ts, *.js | Critical | Description |
+| `PATTERN_TWO` | *.sql | High | Description |
+| `PATTERN_THREE` | * | Medium | Description |
+
+### WARNING Patterns
+
+These patterns will **warn** but allow:
+
+| Pattern | File Types | Reason |
+|---------|-----------|--------|
+| `WARN_PATTERN` | *.ts | Description |
+
+## Detection Script
+
+```bash
+#!/bin/bash
+# {PascalCaseName} Hook
+# {description}
+
+set -e
+
+echo "🔍 Running {name} check..."
+
+# Configuration
+BLOCKING_PATTERNS=(
+  "PATTERN_ONE"
+  "PATTERN_TWO"
+)
+
+WARNING_PATTERNS=(
+  "WARN_PATTERN"
+)
+
+FILE_TYPES="*.ts *.js *.tsx *.jsx"
+
+FOUND_BLOCKING=0
+FOUND_WARNING=0
+
+# Check blocking patterns
+for pattern in "${BLOCKING_PATTERNS[@]}"; do
+  if grep -rn "$pattern" --include="$FILE_TYPES" . 2>/dev/null; then
+    echo "❌ BLOCKING: Found '$pattern'"
+    FOUND_BLOCKING=$((FOUND_BLOCKING + 1))
+  fi
+done
+
+# Check warning patterns
+for pattern in "${WARNING_PATTERNS[@]}"; do
+  if grep -rn "$pattern" --include="$FILE_TYPES" . 2>/dev/null; then
+    echo "⚠️  WARNING: Found '$pattern'"
+    FOUND_WARNING=$((FOUND_WARNING + 1))
+  fi
+done
+
+# Results
+if [ $FOUND_BLOCKING -gt 0 ]; then
+  echo ""
+  echo "╔═══════════════════════════════════════════╗"
+  echo "║  ❌ HOOK BLOCKED: $FOUND_BLOCKING issues found  ║"
+  echo "╚═══════════════════════════════════════════╝"
+  echo ""
+  echo "Fix the issues above or bypass with:"
+  echo "  SKIP_{NAME_UPPER}_HOOK=1 git commit -m 'message'"
+  exit 1
+fi
+
+if [ $FOUND_WARNING -gt 0 ]; then
+  echo ""
+  echo "⚠️  $FOUND_WARNING warnings found (non-blocking)"
+fi
+
+echo "✅ Hook PASSED"
+exit 0
+```
+
+## Integration
+
+### With GitFlow
+
+In `/gitflow:3-commit`, this hook runs automatically:
+
+1. User initiates commit
+2. Hook executes detection script
+3. If blocking patterns found → commit rejected
+4. User must fix or explicitly bypass
+
+### Manual Execution
+
+```bash
+# Run hook manually
+./.claude/hooks/{name}.sh
+
+# Check specific files
+./.claude/hooks/{name}.sh src/specific-file.ts
+```
+
+## Bypass (Emergency Only)
+
+```bash
+# Use with extreme caution!
+SKIP_{NAME_UPPER}_HOOK=1 git commit -m "message"
+
+# Or in environment
+export SKIP_{NAME_UPPER}_HOOK=1
+```
+
+**WARNING**: Bypassing should be documented and justified.
+
+## Logging
+
+All detections logged to:
+`~/.claude/gitflow/logs/{name}.json`
+
+```json
+{
+  "timestamp": "2024-01-15T10:30:00Z",
+  "hook": "{name}",
+  "trigger": "{trigger}",
+  "result": "blocked|passed|warning",
+  "blocking_issues": [],
+  "warnings": [],
+  "branch": "feature/xxx",
+  "user": "username"
+}
+```
+
+## Customization
+
+Edit patterns in the hook file:
+- Add new blocking patterns
+- Adjust file type filters
+- Customize error messages
+
+## Priority
+
+Security > Correctness > Speed
+```
+
+## Trigger Options
+
+| Trigger | Use Case |
+|---------|----------|
+| `pre-commit` | Validate before local commit |
+| `pre-merge` | Validate before branch merge |
+| `pre-push` | Validate before pushing to remote |
+| `post-commit` | Log/notify after commit |
+
+## Workflow
+
+1. Parse arguments (name, trigger, description)
+2. Validate name format
+3. Create project directory
+4. Generate hook template with proper trigger
+5. Display success message
+
+---
+
+User: $ARGUMENTS