@atlashub/smartstack-cli 2.1.0 → 2.2.0

package/templates/skills/business-analyse/steps/step-02-analyse.md

@@ -1,299 +0,0 @@
----
-name: step-02-analyse
-description: Analysis phase - BRD formalization with business rules
-next_step: steps/step-03-specify.md
----
-
-## YOUR TASK:
-
-Transform discovery findings into a formal Business Requirements Document (BRD).
-Identify and formalize all business rules with BR-XXX identifiers.
-
-> **ULTRATHINK MODE:**
-> - Extract IMPLICIT rules from discovery responses
-> - Challenge completeness of each rule
-> - Verify no rule contradicts another
-> - Ensure rules are testable
-
-## EXECUTION SEQUENCE:
-
-### 1. Read Current State
-
-Read `{output_dir}/00-context.md` to restore state variables.
-Read `{output_dir}/1-discovery.md` for discovery findings.
-
-Update progress: `02-analyse` -> "In Progress"
-
-**Read digest from previous step:**
-Read `{output_dir}/digest-01.md` for compressed context from previous step.
-**DO NOT read full output files** unless in resume mode (`-r`).
-
----
-
-### 2. Load BRD Template
-
-```
-Read: templates/tpl-brd.md    # ~90 lines only (vs 477 lines full template)
-```
-
-This template contains ONLY the BRD structure, not FRD or Handoff.
-
----
-
-### 3. Extract Business Objectives
-
-From discovery section 1 (Contexte Business), formalize:
-
-| ID | Objective | Metric | Target |
-|----|----------|----------|-------|
-| OBJ-001 | {objective} | {measurable KPI} | {target value} |
-| OBJ-002 | ... | ... | ... |
-
-**ULTRATHINK checkpoint:**
-- Each objective is measurable?
-- Target values are realistic?
-- Objectives align with stakeholder needs?
-
----
-
-### 4. Identify Business Rules
-
-Scan discovery document for implicit and explicit rules:
-
-**Sources to analyze:**
-- Scope section (constraints)
-- Stakeholder needs (role-specific rules)
-- Data requirements (validation rules)
-- Process flows (workflow rules)
-
-**Rule categories:**
-| Category | Example | BR-ID pattern |
-|----------|---------|---------------|
-| Validation | "Email must be unique" | BR-VAL-XXX |
-| Calculation | "Total = sum of lines" | BR-CALC-XXX |
-| Workflow | "Manager must approve > 1000$" | BR-WF-XXX |
-| Security | "Only admin can delete" | BR-SEC-XXX |
-| Data | "Created date is immutable" | BR-DATA-XXX |
-
----
-
-### 5. Formalize Each Business Rule
-
-For each identified rule, create detailed specification:
-
-```markdown
-#### BR-XXX: {Rule Name}
-
-**Statement:** {Clear, unambiguous statement}
-
-**Conditions:**
-- IF {condition A}
-- AND {condition B}
-- THEN {result}
-- ELSE {alternative result}
-
-**Examples:**
-| Input | Expected Output |
-|-------|-----------------|
-| {example input 1} | {expected output 1} |
-| {example input 2} | {expected output 2} |
-
-**Testability:** {How to verify this rule}
-```
-
----
-
-### 6. Model Business Process
-
-Create process diagram for main flow:
-
-```
-┌─────────────┐     ┌─────────────┐     ┌─────────────┐
-│   Step 1    │────►│   Step 2    │────►│   Step 3    │
-│  {action}   │     │  {action}   │     │  {action}   │
-└─────────────┘     └─────────────┘     └─────────────┘
-      │                   │                   │
-      ▼                   ▼                   ▼
-   {actor}            {actor}            {actor}
-```
-
-Identify:
-- Entry points
-- Decision points (apply BR-WF rules)
-- Exit points
-- Alternative flows
-
----
-
-### 7. Define Data Entities (Business View)
-
-**IMPORTANT: Business attributes only - NO technical types!**
-
-| Entity | Description | Cardinality |
-|--------|-------------|-------------|
-| {Entity} | {business description} | 1:N with {other} |
-
-| Entity | Attribute | Description | Required |
-|--------|-----------|-------------|----------|
-| {Entity} | {attribute} | {business meaning} | Yes/No |
-
-**ULTRATHINK checkpoint:**
-- All entities from discovery captured?
-- Relationships are complete?
-- No orphan entities?
-- **RBAC CHECK:** No role/permission/access-level modeled as entity attribute?
-  - `User.Role`, `User.AccessLevel`, `User.IsAdmin` = **FORBIDDEN**
-  - Roles are SmartStack RBAC permission sets, not data model concepts
-  - If stakeholders described roles, they belong in the Permission Matrix (step-03), not here
-
----
-
-### 8. Identify Integrations
-
-| System | Direction | Data | Frequency |
-|--------|-----------|------|-----------|
-| {system} | In/Out/Bi | {data} | Real-time/Batch |
-
-For each integration, note:
-- Data format expected
-- Error handling strategy
-- Fallback behavior
-
----
-
-### 9. Compile BRD Document
-
-Assemble using `templates/tpl-brd.md` structure:
-
-```markdown
-# BRD - {feature_id} {feature_description}
-
-> **Module:** business/{application_name}/{module_name}
-> **Version:** 1.0
-> **Based on:** 1-discovery.md v1.0
-
-## 1. Executive Summary
-{3-5 sentence synthesis}
-
-## 2. Business Objectives
-{OBJ table}
-
-## 3. Business Rules
-{BR summary table}
-
-### 3.1 Critical Rules Detail
-{BR-XXX detailed specs}
-
-## 4. Business Process
-{Process diagrams}
-
-## 5. Business Data
-{Entity tables - business view}
-
-## 6. Integrations
-{Integration table}
-
----
-
-## Version History
-
-| Version | Date | Author | Changes |
-|---------|------|--------|---------|
-| 1.0 | {date} | BA | Initial creation |
-```
-
----
-
-### 9b. Generate Context Digest
-
-**Write digest to:** `{output_dir}/digest-02.md`
-
-```markdown
-# Digest: Step 02 - Analyse
-
-## Changes
-- {output_dir}/2-business-requirements.md: BRD created
-
-## Decisions
-- {count} business objectives formalized
-- {count} business rules identified (categories: VAL, CALC, WF, SEC, DATA)
-
-## Findings
-- {count} entities with {count} total attributes
-- {count} integrations identified
-- Process flow: {summary of main flow}
-
-## State Updates
-| Variable | New Value |
-|----------|-----------|
-| br_count | {count} |
-| entity_count | {count} |
-| integration_count | {count} |
-
-## For Next Step
-- BR-IDs to trace: {list of BR-IDs}
-- Entities to specify: {list}
-- Permission paths needed for: {list of entities}
-```
-
----
-
-### 10. Save Output
-
-Write to: `{output_dir}/2-business-requirements.md`
-
-Update `00-context.md`:
-- Progress: `02-analyse` -> "Complete"
-- Add BR count to state
-
----
-
-### 11. Display Summary and Load Next Step
-
-**Display:**
-
-| Field | Value |
-|-------|-------|
-| Step | ANALYSE |
-| Feature | {feature_id} |
-| Status | Complete |
-| Objectives | {OBJ count} |
-| Business Rules | {BR count} |
-| Entities | {entity count} |
-| Integrations | {integration count} |
-| Output | {output_dir}/2-business-requirements.md |
-| Next | step-03-specify (FRD + Use Cases) |
-
-**If NOT auto_mode:**
-Ask: "Proceed with functional specification?"
-
-**Load next step:**
-```
-Read and execute: steps/step-03-specify.md
-```
-
----
-
-## OUTPUT FORMAT:
-
-This step produces:
-- `{output_dir}/2-business-requirements.md` (created)
-- `{output_dir}/00-context.md` (updated)
-
-Template loaded: **~90 lines** (vs 477 lines full file)
-
-## ERROR HANDLING:
-
-**If discovery document is incomplete:**
-1. List missing sections
-2. Ask user: "Return to discovery to complete, or proceed with available data?"
-3. If proceeding: mark BRD sections with "[INCOMPLETE - based on partial discovery]"
-
-**If business rules contradict each other:**
-1. Identify conflicting rules (BR-XXX vs BR-YYY)
-2. Ask user to resolve contradiction via AskUserQuestion
-3. Document resolution in BRD
-
-## NEXT STEP:
-
-After completion, proceed to `steps/step-03-specify.md`