@atlashub/smartstack-cli 2.0.0 → 2.2.0

package/templates/skills/business-analyse/steps/step-04-validate.md

@@ -1,313 +0,0 @@
----
-name: step-04-validate
-description: Validation gate - APPROVED or REJECTED decision
-next_step: steps/step-05-handoff.md
----
-
-## YOUR TASK:
-
-Validate that all specifications are complete and consistent.
-Gate decision: APPROVED or REJECTED with reasons.
-
-## EXECUTION SEQUENCE:
-
-### 1. Read Current State
-
-Read `{output_dir}/00-context.md` for state variables.
-Read all previous outputs:
-- `1-discovery.md`
-- `2-business-requirements.md`
-- `3-functional-specification.md`
-
-Update progress: `04-validate` -> "In Progress"
-
-**Read digest from previous step:**
-Read `{output_dir}/digest-03.md` for compressed context from previous step.
-**DO NOT read full output files** unless in resume mode (`-r`).
-
----
-
-### 2. Completeness Checklist
-
-**Discovery validation:**
-- [ ] Business problem clearly defined
-- [ ] All stakeholders identified
-- [ ] Scope (In/Out) explicit
-- [ ] Acceptance criteria defined
-- [ ] No critical open questions
-
-**BRD validation:**
-- [ ] All business objectives measurable
-- [ ] All business rules have BR-ID
-- [ ] Rules are testable (conditions + examples)
-- [ ] Process flow documented
-- [ ] Data entities complete
-
-**FRD validation:**
-- [ ] All UC have permission mapping
-- [ ] All FR trace to BR
-- [ ] Permission matrix complete
-- [ ] UI wireframes provided
-- [ ] Gherkin scenarios cover happy path + errors
-- [ ] i18n keys defined for messages
-
----
-
-### 3. Consistency Checks
-
-**Cross-reference validation:**
-
-| Check | Source | Target | Status |
-|-------|--------|--------|--------|
-| BR -> FR | 2-brd.md | 3-frd.md | {OK/FAIL} |
-| AC -> UC | 1-discovery.md | 3-frd.md | {OK/FAIL} |
-| Stakeholder -> Actor | 1-discovery.md | 3-frd.md | {OK/FAIL} |
-| Entity -> Endpoint | 2-brd.md | 3-frd.md | {OK/FAIL} |
-
-**Identify gaps:**
-- BR without FR coverage
-- AC without UC coverage
-- Endpoints without permissions
-
----
-
-### 4. SmartStack Convention Validation
-
-**Permission path format:**
-```
-VALID:   business.{app}.{module}.{action}
-INVALID: business.{app}.{action}
-INVALID: {app}.{module}.{action}
-```
-
-**NavRoute compliance:**
-- Controller route must match: `business.{app}.{module}`
-- Permissions must use same base path
-
-**Entity naming:**
-- PascalCase for entity names
-- Matches module naming convention
-
----
-
-### 5. Documentation Freshness Check
-
-**If `docs-manifest.json` exists in project root:**
-
-| Check | Expected | Status |
-|-------|----------|--------|
-| Module has manifest entry | Entry exists | {OK/MISSING} |
-| Last doc update < 30 days from last code change | Within threshold | {OK/DRIFT} |
-| All 8 business-first sections present | 8/8 | {X/8} |
-| i18n FR complete (minimum) | All keys present | {OK/INCOMPLETE} |
-| frd-data.ts exists | File present | {OK/MISSING} |
-
-**If drift detected:**
-- Add to validation report: `"documentationDrift": true`
-- Add to issues: `"Documentation is {N} days behind code changes"`
-- Severity: WARNING (non-blocking for BA validation)
-
-**If `docs-manifest.json` absent:** Skip this section silently.
-
----
-
-### 6. Risk Assessment
-
-| Risk | Severity | Mitigation |
-|------|----------|------------|
-| {identified risk} | High/Medium/Low | {mitigation strategy} |
-
-**Common risks to check:**
-- [ ] Missing error handling for integrations
-- [ ] Performance concerns for large datasets
-- [ ] Security gaps in permission model
-- [ ] Complex workflow without clear rollback
-
----
-
-### 7. Make Decision
-
-**APPROVED if:**
-- All completeness checks pass (100%)
-- All consistency checks pass
-- No HIGH severity risks unmitigated
-- SmartStack conventions respected
-
-**REJECTED if:**
-- Any critical completeness check fails
-- Consistency gap found
-- HIGH severity risk without mitigation
-- Convention violations
-
----
-
-### 8b. Generate Context Digest
-
-**Write digest to:** `{output_dir}/digest-04.md`
-
-```markdown
-# Digest: Step 04 - Validate
-
-## Changes
-- {output_dir}/validation.json: Validation report created
-
-## Decisions
-- Gate decision: {APPROVED/REJECTED}
-- Completeness: {score}
-- Consistency: {all checks status}
-
-## Findings
-- Convention compliance: {status}
-- Documentation drift: {status}
-- Risks: {count} identified, {count} mitigated
-
-## State Updates
-| Variable | New Value |
-|----------|-----------|
-| validation_status | {APPROVED/REJECTED} |
-| completeness_score | {score} |
-| risk_count | {count} |
-
-## For Next Step
-- Validation: {APPROVED/REJECTED}
-- If REJECTED: {list of issues to fix}
-- If APPROVED: ready for handoff generation
-```
-
----
-
-### 9. Generate Validation Report
-
-```json
-{
-  "featureId": "{feature_id}",
-  "validatedAt": "{timestamp}",
-  "validatedBy": "Business Analyst (Claude)",
-  "decision": "APPROVED" | "REJECTED",
-  "completeness": {
-    "discovery": {
-      "score": "5/5",
-      "issues": []
-    },
-    "brd": {
-      "score": "5/5",
-      "issues": []
-    },
-    "frd": {
-      "score": "6/6",
-      "issues": []
-    }
-  },
-  "consistency": {
-    "brToFr": "OK",
-    "acToUc": "OK",
-    "stakeholderToActor": "OK",
-    "entityToEndpoint": "OK"
-  },
-  "conventions": {
-    "permissions": "OK",
-    "navRoute": "OK",
-    "naming": "OK"
-  },
-  "risks": [
-    {
-      "risk": "{description}",
-      "severity": "Medium",
-      "mitigation": "{strategy}",
-      "status": "Mitigated"
-    }
-  ],
-  "summary": "{Overall assessment}",
-  "nextStep": "step-05-handoff" | "Revision required"
-}
-```
-
----
-
-### 10. Save Output
-
-Write to: `{output_dir}/validation.json`
-
-Update `00-context.md`:
-- Progress: `04-validate` -> "Complete"
-- Add validation status
-
----
-
-### 11. Handle Decision
-
-**If APPROVED:**
-
-Display:
-
-| Field | Value |
-|-------|-------|
-| Step | VALIDATION |
-| Feature | {feature_id} |
-| Status | APPROVED |
-| Completeness | 100% |
-| Consistency | All checks passed |
-| Conventions | SmartStack compliant |
-| Risks | {count} mitigated |
-| Output | {output_dir}/validation.json |
-| Next | step-05-handoff (Development prompt) |
-
-Load next step: `steps/step-05-handoff.md`
-
-**If REJECTED:**
-
-Display:
-
-| Field | Value |
-|-------|-------|
-| Step | VALIDATION |
-| Feature | {feature_id} |
-| Status | REJECTED |
-| Issues | {issue 1}, {issue 2}, {issue 3} |
-| Action 1 | {action 1} |
-| Action 2 | {action 2} |
-| Next | Revise specifications |
-
-**Ask user:**
-```json
-{
-  "questions": [
-    {
-      "question": "How would you like to proceed?",
-      "header": "Action",
-      "options": [
-        {"label": "Auto-revise", "description": "Claude fixes the identified issues"},
-        {"label": "Manual revision", "description": "You fix and relaunch validation"},
-        {"label": "Force approval", "description": "Continue despite issues (not recommended)"}
-      ],
-      "multiSelect": false
-    }
-  ]
-}
-```
-
----
-
-## OUTPUT FORMAT:
-
-This step produces:
-- `{output_dir}/validation.json` (created)
-- `{output_dir}/00-context.md` (updated)
-
-Gate decision enables or blocks next step.
-
-## ERROR HANDLING:
-
-**If previous output files are missing:**
-1. List which files exist vs expected
-2. If partial: validate only available documents
-3. Add "Missing document" as CRITICAL issue in validation report
-
-**If validation gate REJECTED:**
-1. Present issues to user with severity
-2. Offer: auto-revise / manual revision / force approval
-3. If auto-revise: loop back to the step that needs fixing
-
-## NEXT STEP:
-
-After completion, proceed to `steps/step-05-handoff.md`