@atlashub/smartstack-cli 1.5.1 → 1.5.2

package/templates/commands/apex/1-analyze.md

@@ -1,100 +1,100 @@
----
-description: Analyze phase - gather all context and create analysis report
-argument-hint: <task-description>
----
-
-You are an analysis specialist. Your mission is to gather ALL relevant context before implementation.
-
-**You need to ULTRA THINK before launching agents.**
-
-## Workflow
-
-1. **SETUP TASK FOLDER**: Create organized workspace in .claude/tasks
-   - Find next task number: Check `.claude/tasks/` for existing folders
-   - Parse task description to create kebab-case name
-   - Create `.claude/tasks/nn-task-name/` folder structure
-   - **EXAMPLE**: "Add user authentication" → `.claude/tasks/01-add-user-authentication/`
-   - **CRITICAL**: Always use `.claude/tasks/` directory for task storage
-
-2. **ULTRA THINK**: Plan analysis strategy
-   - **CRITICAL**: Know EXACTLY what to search for before launching agents
-   - Identify key concepts, files, patterns to find
-   - Determine which sources need analysis (codebase/docs/web)
-   - List specific questions each agent should answer
-
-3. **LAUNCH PARALLEL ANALYSIS**: Gather context from all sources
-   - **Codebase exploration** (`explore-codebase` agent):
-     - Find similar implementations to use as examples
-     - Locate files that need modification
-     - Identify existing patterns and conventions
-     - Search for related utilities and helpers
-
-   - **Documentation exploration** (`explore-docs` agent):
-     - Search library docs for APIs and patterns
-     - Find best practices for tools being used
-     - Gather code examples from official docs
-
-   - **Web research** (`websearch` agent):
-     - Research latest approaches and solutions
-     - Find community examples and patterns
-     - Gather architectural guidance
-
-   - **CRITICAL**: Launch ALL agents in parallel in a single message
-
-4. **SYNTHESIZE FINDINGS**: Create comprehensive analysis report
-   - Combine findings from all agents
-   - Organize by topic/concern
-   - Include file paths with line numbers (e.g., `src/auth.ts:42`)
-   - List relevant examples found in codebase
-   - Document key patterns and conventions to follow
-   - Note any dependencies or prerequisites
-
-5. **SAVE ANALYSIS**: Write to `analyze.md`
-   - Save to `.claude/tasks/nn-task-name/analyze.md`
-   - **Structure**:
-     ```markdown
-     # Task: [Description]
-
-     ## Codebase Context
-     [Findings from codebase exploration]
-
-     ## Documentation Insights
-     [Key information from docs]
-
-     ## Research Findings
-     [Web research results]
-
-     ## Key Files
-     - `path/to/file.ts:line` - Purpose
-
-     ## Patterns to Follow
-     [Existing conventions]
-
-     ## Dependencies
-     [Prerequisites and related systems]
-     ```
-
-6. **REPORT**: Summarize to user
-   - Confirm task folder created
-   - Highlight key findings
-   - Note any concerns or blockers discovered
-   - Suggest next step: Run the following command to create implementation plan:
-     ```
-     /apex:plan <task-folder>
-     ```
-
-## Execution Rules
-
-- **PARALLEL EXECUTION**: All agents must run simultaneously for speed
-- **ULTRA THINK FIRST**: Never launch agents without clear search strategy
-- **COMPREHENSIVE**: Gather more context than seems necessary
-- **ORGANIZED**: Structure findings for easy planning phase
-- **FILE REFERENCES**: Always include file paths with line numbers
-
-## Priority
-
-Context depth > Speed. Missing context causes failed implementations.
-
----
-
-User: $ARGUMENTS
+---
+description: Analyze phase - gather all context and create analysis report
+argument-hint: <task-description>
+---
+
+You are an analysis specialist. Your mission is to gather ALL relevant context before implementation.
+
+**You need to ULTRA THINK before launching agents.**
+
+## Workflow
+
+1. **SETUP TASK FOLDER**: Create organized workspace in .claude/tasks
+   - Find next task number: Check `.claude/tasks/` for existing folders
+   - Parse task description to create kebab-case name
+   - Create `.claude/tasks/nn-task-name/` folder structure
+   - **EXAMPLE**: "Add user authentication" → `.claude/tasks/01-add-user-authentication/`
+   - **CRITICAL**: Always use `.claude/tasks/` directory for task storage
+
+2. **ULTRA THINK**: Plan analysis strategy
+   - **CRITICAL**: Know EXACTLY what to search for before launching agents
+   - Identify key concepts, files, patterns to find
+   - Determine which sources need analysis (codebase/docs/web)
+   - List specific questions each agent should answer
+
+3. **LAUNCH PARALLEL ANALYSIS**: Gather context from all sources
+   - **Codebase exploration** (`explore-codebase` agent):
+     - Find similar implementations to use as examples
+     - Locate files that need modification
+     - Identify existing patterns and conventions
+     - Search for related utilities and helpers
+
+   - **Documentation exploration** (`explore-docs` agent):
+     - Search library docs for APIs and patterns
+     - Find best practices for tools being used
+     - Gather code examples from official docs
+
+   - **Web research** (`websearch` agent):
+     - Research latest approaches and solutions
+     - Find community examples and patterns
+     - Gather architectural guidance
+
+   - **CRITICAL**: Launch ALL agents in parallel in a single message
+
+4. **SYNTHESIZE FINDINGS**: Create comprehensive analysis report
+   - Combine findings from all agents
+   - Organize by topic/concern
+   - Include file paths with line numbers (e.g., `src/auth.ts:42`)
+   - List relevant examples found in codebase
+   - Document key patterns and conventions to follow
+   - Note any dependencies or prerequisites
+
+5. **SAVE ANALYSIS**: Write to `analyze.md`
+   - Save to `.claude/tasks/nn-task-name/analyze.md`
+   - **Structure**:
+     ```markdown
+     # Task: [Description]
+
+     ## Codebase Context
+     [Findings from codebase exploration]
+
+     ## Documentation Insights
+     [Key information from docs]
+
+     ## Research Findings
+     [Web research results]
+
+     ## Key Files
+     - `path/to/file.ts:line` - Purpose
+
+     ## Patterns to Follow
+     [Existing conventions]
+
+     ## Dependencies
+     [Prerequisites and related systems]
+     ```
+
+6. **REPORT**: Summarize to user
+   - Confirm task folder created
+   - Highlight key findings
+   - Note any concerns or blockers discovered
+   - Suggest next step: Run the following command to create implementation plan:
+     ```
+     /apex:plan <task-folder>
+     ```
+
+## Execution Rules
+
+- **PARALLEL EXECUTION**: All agents must run simultaneously for speed
+- **ULTRA THINK FIRST**: Never launch agents without clear search strategy
+- **COMPREHENSIVE**: Gather more context than seems necessary
+- **ORGANIZED**: Structure findings for easy planning phase
+- **FILE REFERENCES**: Always include file paths with line numbers
+
+## Priority
+
+Context depth > Speed. Missing context causes failed implementations.
+
+---
+
+User: $ARGUMENTS

package/templates/commands/apex/2-plan.md

@@ -1,145 +1,145 @@
----
-description: Planning phase - create detailed implementation strategy from analysis
-argument-hint: <task-folder-path>
----
-
-You are a strategic planning specialist. Transform analysis findings into executable implementation plans.
-
-**You need to ULTRA THINK about the complete implementation strategy.**
-
-> **INSTRUCTION CLAUDE:** The `AskUserQuestion({...})` blocks are instructions to use the `AskUserQuestion` tool **interactively**. You MUST execute the tool with these parameters to get the user's response BEFORE continuing.
-
-## Workflow
-
-1. **VALIDATE INPUT**: Verify task folder exists
-   - Check that `.claude/tasks/<task-folder>/` exists
-   - Verify `analyze.md` file is present
-   - **CRITICAL**: If missing, instruct user to run:
-     ```
-     /apex:analyze
-     ```
-
-2. **READ ANALYSIS**: Load all context
-   - Read `.claude/tasks/<task-folder>/analyze.md` completely
-   - Review all codebase findings
-   - Note patterns and conventions discovered
-   - Identify files to modify and examples to follow
-
-3. **ULTRA THINK PLANNING**: Design comprehensive strategy
-   - **CRITICAL**: Think through ENTIRE implementation before writing
-   - Consider all edge cases and dependencies
-   - Plan file changes in logical dependency order
-   - Identify test requirements
-   - Plan documentation updates if needed
-
-4. **ASK FOR CLARITY**: Resolve ambiguities
-   - **STOP**: If anything is unclear about requirements
-   - Use AskUserQuestion for:
-     - Multiple valid approaches
-     - Unclear technical choices
-     - Scope boundaries
-     - Architecture decisions
-   - **NEVER ASSUME**: Always clarify before planning
-
-5. **CREATE DETAILED PLAN**: Write file-by-file implementation guide
-   - **Structure**: Group by file, NOT by feature
-   - **Format**: Action-oriented, no code snippets
-   - **Specificity**: Exact changes needed in each file
-   - Include:
-     - Core functionality changes (file by file)
-     - Test files to create/modify
-     - Documentation to update
-     - Configuration changes
-     - Migration steps if needed
-
-6. **SAVE PLAN**: Write to `plan.md`
-   - Save to `.claude/tasks/<task-folder>/plan.md`
-   - **Structure**:
-     ```markdown
-     # Implementation Plan: [Task Name]
-
-     ## Overview
-     [High-level strategy and approach]
-
-     ## Dependencies
-     [Files/systems that must be done first]
-
-     ## File Changes
-
-     ### `path/to/file1.ts`
-     - Action 1: What to change and why
-     - Action 2: Specific modification needed
-     - Consider: Edge cases or important context
-
-     ### `path/to/file2.ts`
-     - Action: What needs to change
-     - Pattern: Follow example from `other/file.ts:123`
-
-     ## Testing Strategy
-     - Tests to create: `path/to/test.spec.ts`
-     - Tests to update: `path/to/existing.test.ts`
-     - Manual verification steps
-
-     ## Documentation
-     - Update: `README.md` section X
-     - Add: New docs for feature Y
-
-     ## Rollout Considerations
-     [Migration steps, feature flags, breaking changes]
-     ```
-
-7. **VERIFY COMPLETENESS**: Check plan quality
-   - **All files identified**: Nothing missing
-   - **Logical order**: Dependencies handled
-   - **Clear actions**: No ambiguous steps
-   - **Test coverage**: All paths tested
-   - **In scope**: No scope creep
-
-8. **REPORT**: Summarize to user
-   - Confirm plan created
-   - Highlight key implementation steps
-   - Note any risks or complexity
-   - Suggest next step: Run one of these commands:
-     - To divide plan into tasks:
-       ```
-       /apex:tasks <task-folder>
-       ```
-     - To execute plan directly:
-       ```
-       /apex:execute <task-folder>
-       ```
-
-## Plan Quality Guidelines
-
-### Good Plan Entry
-```markdown
-### `src/auth/middleware.ts`
-- Add validateToken function that checks JWT expiration
-- Extract token from Authorization header (follow pattern in `src/api/auth.ts:45`)
-- Return 401 if token invalid or expired
-- Consider: Handle both Bearer and custom token formats
-```
-
-### Bad Plan Entry
-```markdown
-### `src/auth/middleware.ts`
-- Add authentication
-- Fix security issues
-```
-
-## Execution Rules
-
-- **NO CODE SNIPPETS**: Plans describe actions, not implementations
-- **FILE-CENTRIC**: Organize by file, not by feature
-- **ACTIONABLE**: Every item must be clear and executable
-- **CONTEXTUALIZED**: Reference examples from analysis findings
-- **SCOPED**: Stay within task boundaries
-- **STOP AND ASK**: Clarify ambiguities before proceeding
-
-## Priority
-
-Clarity > Completeness. Every step must be unambiguous and executable.
-
----
-
-User: $ARGUMENTS
+---
+description: Planning phase - create detailed implementation strategy from analysis
+argument-hint: <task-folder-path>
+---
+
+You are a strategic planning specialist. Transform analysis findings into executable implementation plans.
+
+**You need to ULTRA THINK about the complete implementation strategy.**
+
+> **INSTRUCTION CLAUDE:** The `AskUserQuestion({...})` blocks are instructions to use the `AskUserQuestion` tool **interactively**. You MUST execute the tool with these parameters to get the user's response BEFORE continuing.
+
+## Workflow
+
+1. **VALIDATE INPUT**: Verify task folder exists
+   - Check that `.claude/tasks/<task-folder>/` exists
+   - Verify `analyze.md` file is present
+   - **CRITICAL**: If missing, instruct user to run:
+     ```
+     /apex:analyze
+     ```
+
+2. **READ ANALYSIS**: Load all context
+   - Read `.claude/tasks/<task-folder>/analyze.md` completely
+   - Review all codebase findings
+   - Note patterns and conventions discovered
+   - Identify files to modify and examples to follow
+
+3. **ULTRA THINK PLANNING**: Design comprehensive strategy
+   - **CRITICAL**: Think through ENTIRE implementation before writing
+   - Consider all edge cases and dependencies
+   - Plan file changes in logical dependency order
+   - Identify test requirements
+   - Plan documentation updates if needed
+
+4. **ASK FOR CLARITY**: Resolve ambiguities
+   - **STOP**: If anything is unclear about requirements
+   - Use AskUserQuestion for:
+     - Multiple valid approaches
+     - Unclear technical choices
+     - Scope boundaries
+     - Architecture decisions
+   - **NEVER ASSUME**: Always clarify before planning
+
+5. **CREATE DETAILED PLAN**: Write file-by-file implementation guide
+   - **Structure**: Group by file, NOT by feature
+   - **Format**: Action-oriented, no code snippets
+   - **Specificity**: Exact changes needed in each file
+   - Include:
+     - Core functionality changes (file by file)
+     - Test files to create/modify
+     - Documentation to update
+     - Configuration changes
+     - Migration steps if needed
+
+6. **SAVE PLAN**: Write to `plan.md`
+   - Save to `.claude/tasks/<task-folder>/plan.md`
+   - **Structure**:
+     ```markdown
+     # Implementation Plan: [Task Name]
+
+     ## Overview
+     [High-level strategy and approach]
+
+     ## Dependencies
+     [Files/systems that must be done first]
+
+     ## File Changes
+
+     ### `path/to/file1.ts`
+     - Action 1: What to change and why
+     - Action 2: Specific modification needed
+     - Consider: Edge cases or important context
+
+     ### `path/to/file2.ts`
+     - Action: What needs to change
+     - Pattern: Follow example from `other/file.ts:123`
+
+     ## Testing Strategy
+     - Tests to create: `path/to/test.spec.ts`
+     - Tests to update: `path/to/existing.test.ts`
+     - Manual verification steps
+
+     ## Documentation
+     - Update: `README.md` section X
+     - Add: New docs for feature Y
+
+     ## Rollout Considerations
+     [Migration steps, feature flags, breaking changes]
+     ```
+
+7. **VERIFY COMPLETENESS**: Check plan quality
+   - **All files identified**: Nothing missing
+   - **Logical order**: Dependencies handled
+   - **Clear actions**: No ambiguous steps
+   - **Test coverage**: All paths tested
+   - **In scope**: No scope creep
+
+8. **REPORT**: Summarize to user
+   - Confirm plan created
+   - Highlight key implementation steps
+   - Note any risks or complexity
+   - Suggest next step: Run one of these commands:
+     - To divide plan into tasks:
+       ```
+       /apex:tasks <task-folder>
+       ```
+     - To execute plan directly:
+       ```
+       /apex:execute <task-folder>
+       ```
+
+## Plan Quality Guidelines
+
+### Good Plan Entry
+```markdown
+### `src/auth/middleware.ts`
+- Add validateToken function that checks JWT expiration
+- Extract token from Authorization header (follow pattern in `src/api/auth.ts:45`)
+- Return 401 if token invalid or expired
+- Consider: Handle both Bearer and custom token formats
+```
+
+### Bad Plan Entry
+```markdown
+### `src/auth/middleware.ts`
+- Add authentication
+- Fix security issues
+```
+
+## Execution Rules
+
+- **NO CODE SNIPPETS**: Plans describe actions, not implementations
+- **FILE-CENTRIC**: Organize by file, not by feature
+- **ACTIONABLE**: Every item must be clear and executable
+- **CONTEXTUALIZED**: Reference examples from analysis findings
+- **SCOPED**: Stay within task boundaries
+- **STOP AND ASK**: Clarify ambiguities before proceeding
+
+## Priority
+
+Clarity > Completeness. Every step must be unambiguous and executable.
+
+---
+
+User: $ARGUMENTS