@atlashub/smartstack-cli 2.7.3 → 2.8.0

package/templates/skills/apex/steps/step-03-execute.md

@@ -1,217 +0,0 @@
----
-name: step-03-execute
-description: Todo-driven implementation - execute the plan file by file
-prev_step: steps/step-02-plan.md
-next_step: steps/step-04-validate.md
----
-
-# Step 3: Execute (Implementation)
-
-## MANDATORY EXECUTION RULES:
-
-- NEVER deviate from the approved plan
-- NEVER add features not in the plan (scope creep)
-- NEVER modify files without reading them first
-- ALWAYS follow the plan file-by-file
-- ALWAYS mark todos complete immediately after each task
-- ALWAYS read files BEFORE editing them
-- YOU ARE AN IMPLEMENTER following a plan, not a designer
-- FORBIDDEN to add "improvements" not in the plan
-
-## YOUR TASK:
-
-Execute the approved implementation plan file-by-file, tracking progress with todos.
-
----
-
-<available_state>
-From previous steps:
-
-| Variable | Description |
-|----------|-------------|
-| `{task_description}` | What to implement |
-| `{task_id}` | Kebab-case identifier |
-| `{auto_mode}` | Skip confirmations |
-| `{save_mode}` | Save outputs to files |
-| `{output_dir}` | Path to output (if save_mode) |
-| Implementation plan | File-by-file changes from step-02 |
-| Patterns | How to implement from step-01 |
-</available_state>
-
----
-
-## EXECUTION SEQUENCE:
-
-### 1. Create Todos from Plan
-
-Convert each file change from the plan into todos:
-
-```
-Plan entry:
-#### `src/auth/handler.ts`
-- Add `validateToken` function
-- Handle error case: expired token
-
-Becomes:
-- [ ] src/auth/handler.ts: Add validateToken function
-- [ ] src/auth/handler.ts: Handle expired token error
-```
-
-Use TodoWrite to create the full list.
-
-### 2. Execute File by File
-
-For each todo:
-
-**2.1 Mark In Progress**
-- Only ONE todo in_progress at a time
-
-**2.2 Read Before Edit**
-```
-ALWAYS read the file before modifying:
-- Understand current structure
-- Find exact insertion points
-- Verify patterns match expectations
-```
-
-**2.3 Implement Changes**
-```
-Make changes specified in the plan:
-- Follow patterns from step-01 analysis
-- Use exact names from plan
-- Handle error cases as specified
-- NO comments unless truly necessary
-```
-
-**2.4 Mark Complete Immediately**
-- Mark todo complete RIGHT AFTER finishing
-- Don't batch completions
-
-**2.5 Log Progress (if save_mode)**
-
-Append to `{output_dir}/03-execute.md`:
-```markdown
-### file.ts
-- Added `functionName` (lines 45-78)
-- Added error handling
-```
-
-### 3. Handle Blockers
-
-**If `{auto_mode}` = true:**
-Make reasonable decision and continue.
-
-**If `{auto_mode}` = false:**
-
-```yaml
-questions:
-  - header: "Blocker"
-    question: "Encountered an issue. How should we proceed?"
-    options:
-      - label: "Use alternative approach (Recommended)"
-        description: "Description of alternative"
-      - label: "Skip this part"
-        description: "Continue without this change"
-      - label: "Stop for discussion"
-        description: "I want to discuss before continuing"
-    multiSelect: false
-```
-
-### 4. Verify Implementation
-
-After completing all todos:
-
-```bash
-pnpm run typecheck && pnpm run lint --fix
-```
-
-Fix any errors immediately.
-
-### 5. Implementation Summary
-
-```
-**Implementation Complete**
-
-**Files Modified:**
-- `src/auth/handler.ts` - Added validateToken, error handling
-- `src/api/auth/route.ts` - Integrated token validation
-
-**New Files:**
-- `src/types/auth.ts` - Auth type definitions
-
-**Todos:** {X}/{Y} complete
-```
-
-### 6. Save Output (if save_mode)
-
-**If `{save_mode}` = true:**
-
-Finalize `{output_dir}/03-execute.md` with:
-- Summary of all changes
-- Timestamp
-- Update 00-context.md Progress table: 03-execute -> Complete
-
-**Then proceed to validation.**
-
-### 6b. Generate Context Digest (if save_mode)
-
-**If `{save_mode}` = true:**
-
-Generate a compact digest (max 50 lines) for inter-step context transfer.
-Use the template from `_resources/context-digest-template.md`.
-
-```markdown
-## Context Digest — step-03-execute
-
-### Changes
-- {files modified with line ranges and summary}
-- {new files created}
-
-### Decisions
-- {implementation choices made during execution}
-
-### Findings
-- {issues encountered and how resolved}
-- {patterns that deviated from plan}
-
-### State
-- Todos completed: {X}/{Y}
-- Files modified: {count}
-- Files created: {count}
-
-### Blockers
-- {any remaining issues}
-
-### Next
-- Step-04 should validate: {specific checks needed}
-- Files to verify: {list of modified files}
-```
-
-Write digest to `{output_dir}/03-execute-digest.md`
-
-**Purpose:** Step-04 reads ONLY this digest (not full execution log) to minimize token usage.
-Exception: If `{resume_task}` is set, read the full outputs instead.
-
----
-
-## SUCCESS METRICS:
-
-- All plan items implemented
-- All todos marked complete
-- No scope creep - only plan items
-- Files read before modification
-- Typecheck and lint pass
-
-## FAILURE MODES:
-
-- Adding features not in the plan
-- Modifying files without reading first
-- Not updating todos as you work
-- Multiple todos in_progress simultaneously
-- Ignoring type or lint errors
-
----
-
-## NEXT STEP:
-
-After implementation complete, load `./step-04-validate.md`

package/templates/skills/apex/steps/step-04-validate.md

@@ -1,273 +0,0 @@
----
-name: step-04-validate
-description: Self-check - run tests, verify AC, audit implementation quality
-prev_step: steps/step-03-execute.md
-next_step: steps/step-05-examine.md
----
-
-# Step 4: Validate (Self-Check)
-
-## MANDATORY EXECUTION RULES:
-
-- NEVER claim checks pass when they don't
-- NEVER skip any validation step
-- ALWAYS run typecheck, lint, and tests
-- ALWAYS verify each acceptance criterion
-- ALWAYS fix failures before proceeding
-- YOU ARE A VALIDATOR, not an implementer
-- FORBIDDEN to proceed with failing checks
-
-## YOUR TASK:
-
-Validate the implementation by running checks, verifying acceptance criteria, and ensuring quality.
-
----
-
-<available_state>
-From previous steps:
-
-| Variable | Description |
-|----------|-------------|
-| `{task_description}` | What was implemented |
-| `{task_id}` | Kebab-case identifier |
-| `{acceptance_criteria}` | Success criteria |
-| `{auto_mode}` | Skip confirmations |
-| `{save_mode}` | Save outputs to files |
-| `{test_mode}` | Include test steps |
-| `{examine_mode}` | Auto-proceed to review |
-| `{doc_mode}` | Documentation sync enabled |
-| `{output_dir}` | Path to output (if save_mode) |
-| Implementation | Completed in step-03 |
-</available_state>
-
----
-
-## EXECUTION SEQUENCE:
-
-### 1. Discover Available Commands
-
-Check `package.json` for exact command names:
-```bash
-cat package.json | grep -A 20 '"scripts"'
-```
-
-Look for: `typecheck`, `lint`, `test`, `build`, `format`
-
-### 2. Run Validation Suite
-
-**2.1 Typecheck**
-```bash
-pnpm run typecheck  # or npm run typecheck
-```
-
-**MUST PASS.** If fails:
-1. Read error messages
-2. Fix type issues
-3. Re-run until passing
-
-**2.2 Lint**
-```bash
-pnpm run lint
-```
-
-**MUST PASS.** If fails:
-1. Try auto-fix: `pnpm run lint --fix`
-2. Manually fix remaining
-3. Re-run until passing
-
-**2.3 Tests**
-```bash
-pnpm run test
-```
-
-**MUST PASS.** If fails:
-1. Identify failing test
-2. Determine if code bug or test bug
-3. Fix the root cause
-4. Re-run until passing
-
-### 3. SmartStack Convention Validation (if MCP available)
-
-**Use MCP to validate SmartStack conventions:**
-
-```
-mcp__smartstack__validate_conventions:
-  checks: ["all"]
-  # Valide: tables, migrations, services, namespaces, entities, tenants, controllers
-```
-
-**If EF Core changes detected, also run:**
-
-```
-mcp__smartstack__check_migrations:
-  # Vérifie conflits, ordre chronologique, ModelSnapshot
-```
-
-**MCP validation checks:**
-- [ ] Table naming (domain prefixes: auth_, nav_, cfg_, etc.)
-- [ ] Migration naming ({context}_v{version}_{sequence}_{Description})
-- [ ] Service interfaces (I*Service pattern)
-- [ ] Namespace structure (Domain → Application → Infrastructure → API)
-- [ ] Entity conventions (base classes, soft delete, audit)
-- [ ] Tenant isolation (ITenantEntity where required)
-- [ ] Controller routes (NavRoute attributes)
-
-### 3b. Documentation Impact Check (informative)
-
-**If `{doc_mode}` = true:**
-
-Check if `docs-manifest.json` exists in the project root. If it does:
-
-1. Read `docs-manifest.json`
-2. Compare modified files (from step-03 todos) against `codeFiles` in manifest
-3. For each impacted module, note:
-   - Module name and featureId
-   - Last documentation update date
-   - Which code-to-doc mapping applies (entity → businessRules, controller → apiEndpoints, etc.)
-
-**Report (informative only, does not block validation):**
-
-```
-Documentation Impact:
-- Module: {app}/{module} (FEAT-NNN) — last doc update: {date}
-  - Entity changes → businessRules, features may need update
-  - Controller changes → apiEndpoints need update
-```
-
-**If `docs-manifest.json` absent:** Skip silently.
-
-> **Note:** Actual documentation sync happens in step-04b-doc-sync.md (next step if doc_mode enabled).
-
-### 4. Self-Audit Checklist
-
-Verify each item:
-
-**Tasks Complete:**
-- [ ] All todos from step-03 marked complete
-- [ ] No tasks skipped without reason
-- [ ] Any blocked tasks have explanation
-
-**Tests Passing:**
-- [ ] All existing tests pass
-- [ ] New tests written for new functionality
-- [ ] No skipped tests without reason
-
-**Acceptance Criteria:**
-- [ ] Each AC demonstrably met
-- [ ] Can explain how implementation satisfies AC
-- [ ] Edge cases considered
-
-**Patterns Followed:**
-- [ ] Code follows existing patterns
-- [ ] Error handling consistent
-- [ ] Naming conventions match
-
-### 5. Format Code
-
-If format command available:
-```bash
-pnpm run format
-```
-
-### 6. Final Verification
-
-Re-run all checks:
-```bash
-pnpm run typecheck && pnpm run lint
-```
-
-Both MUST pass.
-
-### 7. Present Validation Results
-
-```
-**Validation Complete**
-
-**Typecheck:** Pass
-**Lint:** Pass
-**Tests:** {X}/{X} passing
-**Format:** Applied
-
-**Acceptance Criteria:**
-- [x] AC1: Verified by [how]
-- [x] AC2: Verified by [how]
-
-**Files Modified:** {list}
-
-**Summary:** All checks passing, ready for next step.
-```
-
-### 8. Save Output (if save_mode)
-
-**If `{save_mode}` = true:**
-
-Write to `{output_dir}/04-validate.md`:
-- Validation results
-- AC verification
-- Timestamp
-- Update 00-context.md Progress table: 04-validate -> Complete
-
-### 9. Determine Next Step
-
-**Decision tree:**
-
-```
-IF {doc_mode} = true AND docs-manifest.json exists:
-    -> Load step-04b-doc-sync.md (documentation sync)
-
-ELSE IF {test_mode} = true:
-    -> Load step-07-tests.md (test analysis and creation)
-
-ELSE IF {examine_mode} = true:
-    -> Load step-05-examine.md (adversarial review)
-
-ELSE IF {auto_mode} = false:
-    -> Ask user what to do next
-
-ELSE:
-    -> Complete workflow (show final summary)
-```
-
-**If `{auto_mode}` = false:**
-
-```yaml
-questions:
-  - header: "Next"
-    question: "Validation complete. What would you like to do?"
-    options:
-      - label: "Run adversarial review"
-        description: "Deep review for security, logic, and quality"
-      - label: "Complete workflow"
-        description: "Skip review and finalize"
-      - label: "Add tests"
-        description: "Create additional tests first"
-    multiSelect: false
-```
-
----
-
-## SUCCESS METRICS:
-
-- Typecheck passes
-- Lint passes
-- All tests pass
-- All AC verified
-- Code formatted
-- User informed of status
-
-## FAILURE MODES:
-
-- Claiming checks pass when they don't
-- Not running all validation commands
-- Skipping tests for modified code
-- Missing AC verification
-- Proceeding with failures
-
----
-
-## NEXT STEP:
-
-Based on flags (check in order):
-- **If test_mode:** Load `./step-07-tests.md`
-- **If examine_mode OR user requests:** Load `./step-05-examine.md`
-- **Otherwise:** Workflow complete - show summary

package/templates/skills/apex/steps/step-04b-doc-sync.md

@@ -1,162 +0,0 @@
----
-name: step-04b-doc-sync
-description: Documentation sync - detect affected modules and update documentation
-prev_step: steps/step-04-validate.md
-next_step: steps/step-05-examine.md
----
-
-# Step 4b: Documentation Sync
-
-## MANDATORY EXECUTION RULES:
-
-- NEVER skip this step when {doc_mode} = true
-- NEVER create documentation from scratch (that is BA skill's job)
-- ALWAYS update existing documentation only
-- ALWAYS update docs-manifest.json after changes
-- IF docs-manifest.json is absent → skip with note "No documentation manifest found"
-
-## YOUR TASK:
-
-Detect which documented modules are affected by the code changes and update their documentation data files.
-
----
-
-<available_state>
-From previous steps:
-
-| Variable | Description |
-|----------|-------------|
-| `{task_description}` | What was implemented |
-| `{task_id}` | Full task identifier |
-| `{doc_mode}` | Documentation sync enabled (should be true) |
-| `{economy_mode}` | No subagents if true |
-| `{save_mode}` | Save outputs to disk |
-| `{output_dir}` | Output directory path |
-</available_state>
-
----
-
-## EXECUTION SEQUENCE:
-
-### 1. Check Documentation Manifest
-
-Read `docs-manifest.json` from project root.
-
-**If absent:**
-```
-Display: "No docs-manifest.json found. Skipping documentation sync."
-Display: "TIP: Run /business-analyse to create documentation for your modules."
-→ Load next step
-```
-
-**If present:** Continue.
-
-### 2. Identify Affected Modules
-
-Get files modified during step-03 (from TodoList or git diff):
-
-```bash
-git diff --name-only HEAD~1
-```
-
-Match modified files against `codeFiles` in each manifest module entry.
-
-**Build affected modules list:**
-
-| Module | Changed Files | Impact |
-|--------|---------------|--------|
-| business/{app}/{module} | [list] | [sections] |
-
-### 3. Map Code Changes to Documentation Sections
-
-For each affected module, classify changes:
-
-| Code Change Pattern | Documentation Section |
-|--------------------|-----------------------|
-| `**/Entities/**` modified | businessRules, features |
-| `**/Controllers/**` modified | apiEndpoints, technicalRef |
-| `**/Permissions*` modified | permissions |
-| `**/Validators/**` modified | businessRules |
-| `**/i18n/**` modified | useCases (labels), faq |
-| `**/Migrations/**` created | technicalRef |
-| `**/DTOs/**` modified | apiEndpoints |
-| `**/Commands/**` modified | useCases, features |
-| `**/Queries/**` modified | useCases, features |
-
-### 4. Read Current Documentation
-
-For each affected module:
-
-**If {economy_mode} = false:**
-- Launch `docs-context-reader` agent for the module
-- Agent returns structured summary of current doc state
-
-**If {economy_mode} = true:**
-- Read `doc-data.ts` directly
-- Read i18n FR file directly
-
-### 5. Update Documentation Data
-
-For each affected module and impacted section:
-
-1. Read current `doc-data.ts`
-2. Compare with actual code state
-3. Update affected fields:
-   - **apiEndpoints**: Scan controller for `[Http*]` attributes
-   - **permissions**: Scan PermissionConfiguration.cs for module
-   - **businessRules**: Scan validators and entity methods
-   - **useCases**: Update if commands/queries changed
-   - **features**: Update if new functionality added
-4. Write updated `doc-data.ts`
-5. Update i18n FR file if label keys changed
-
-### 6. Update Documentation Manifest
-
-For each updated module:
-
-```json
-{
-  "lastDocUpdate": "{current_timestamp}",
-  "gitCommitDoc": "{current_commit_sha}",
-  "status": "synced"
-}
-```
-
-Update `docs-manifest.json` root `lastUpdated`.
-
-### 7. Save Output (if save_mode)
-
-Write `{output_dir}/04b-doc-sync.md` with:
-- Modules checked
-- Modules updated
-- Sections modified
-- Files changed
-
----
-
-## SUCCESS METRICS:
-
-- All affected modules identified
-- Documentation data files updated for impacted sections
-- docs-manifest.json timestamps updated
-- No new documentation created (only updates)
-
-## FAILURE MODES:
-
-- docs-manifest.json absent → skip gracefully (not a failure)
-- doc-data.ts has unexpected format → report warning, skip module
-- No modules affected → display "No documented modules affected by changes"
-
----
-
-## NEXT STEP:
-
-```
-IF {test_mode} = true AND step-07 not yet done:
-    → Load steps/step-07-tests.md
-ELSE IF {examine_mode} = true:
-    → Load steps/step-05-examine.md
-ELSE:
-    → Display completion summary
-    → IF {pr_mode} = true: Load steps/step-09-finish.md
-```