@torus-engineering/tas-kit 1.13.0 → 2.1.0

package/.tas/rules/csharp/torus-core-framework.md

@@ -0,0 +1,128 @@
+---
+paths:
+  - "**/*.cs"
+  - "**/*.csproj"
+  - "**/*.sln"
+  - "**/Directory.Build.props"
+  - "**/Directory.Build.targets"
+  - "**/appsettings*.json"
+  - "**/Program.cs"
+---
+
+# Torus Core Framework — Bootstrap Rule
+
+> Used by `/tas-plan` and `/tas-dev` when scaffolding a **new .NET backend project** on top of Torus Backend Framework.
+> Skip this rule for non-Torus .NET projects, or when modifying an existing solution not started from `torus-bootstrap`.
+
+## When to apply
+
+Apply if **all** of the following hold:
+- Tech Stack in `CLAUDE.md` contains `.NET` / `C#` as backend
+- Feature / PRD asks for a brand-new backend project (target dir has no `*.sln`)
+- User has not opted out of Torus Backend Framework in `tas.yaml` or task description
+
+If a `*.sln` already exists in the target dir → do NOT re-bootstrap. Read the existing layout instead.
+
+## Tooling
+
+CLI: `torus-bootstrap` — generates Onion Architecture solution wired to Torus Backend Framework NuGet packages.
+
+Install globally (once):
+
+```bash
+dotnet tool install --global Torus.Bootstrap
+```
+
+Or build from source (when working inside the framework monorepo):
+
+```bash
+cd Torus.Bootstrap
+dotnet pack
+dotnet tool install --global --add-source ./bin/Debug Torus.Bootstrap
+```
+
+## Bootstrap workflow
+
+### 1. Pick mode
+
+| Mode | Command | Use when |
+|---|---|---|
+| Interactive | `torus-bootstrap create --name {Name}` | Choices unclear, first-time scaffold |
+| Non-interactive | `torus-bootstrap create --name {Name} --interactive false` | Defaults fine: Memory cache, OpenTelemetry, SQL Server |
+| Flag-driven | `torus-bootstrap create --name {Name} --cache redis --database postgresql ...` | Choices already decided in PRD / SAD |
+
+`{Name}` follows project naming convention (e.g. `Torus.Org`, `Acme.Billing`).
+
+### 2. Flag reference
+
+| Category | Flag | Values | Default |
+|---|---|---|---|
+| Cache | `--cache` | `none` / `memory` / `redis` / `both` | `memory` |
+| Cache | `--distributed-lock` | flag — requires `--cache redis\|both` | off |
+| Messaging | `--messaging` `--kafka` | `--kafka` requires `--messaging` | off |
+| Background Jobs | `--background-jobs` `--quartz` | `--quartz` requires `--background-jobs` | off |
+| Telemetry | `--telemetry` `--otel` | `--otel` requires `--telemetry` | off |
+| Captcha | `--captcha` | `none` / `google` / `turnstile` / `both` | `none` |
+| Authorization | `--opa` | flag — Open Policy Agent | off |
+| Blob Storage | `--blob-storage` | `none` / `filesystem` / `minio` / `s3` / `both` | `none` |
+| Email | `--email` | `none` / `mailkit` / `ses` / `both` | `none` |
+| Database | `--database` | `sqlserver` / `postgresql` / `mysql` / `mongodb` | `sqlserver` |
+| Multi-Tenancy | `--multi-tenancy` | flag | off |
+| Output dir | `--output` | path | current dir |
+
+Flags override interactive prompts when combined.
+
+### 3. Generated structure
+
+```
+{Name}/
+├── {Name}.Domain.Shared/             # Shared domain primitives
+├── {Name}.Domain/                    # Domain layer (entities, value objects)
+├── {Name}.Application.Contracts/     # Application contracts (DTOs, interfaces)
+├── {Name}.Application/               # Application layer (use cases, services)
+├── {Name}.Persistence.EfCore/        # EF Core DbContext + repositories
+├── {Name}.Infrastructure/            # Cross-cutting (logging, caching, ...)
+├── {Name}.WebApi/                    # ASP.NET Core entry point
+└── {Name}.sln
+```
+
+Onion dependency direction: `WebApi → Infrastructure / Persistence → Application → Application.Contracts → Domain → Domain.Shared`. Inner layers MUST NOT reference outer layers.
+
+### 4. Post-bootstrap checklist
+
+After `torus-bootstrap create` succeeds:
+
+1. `cd {Name}` && `dotnet restore`
+2. Update `appsettings.json` with real config. Secrets go via `dotnet user-secrets` / env vars — never commit.
+3. Add EF Core provider package to `{Name}.Persistence.EfCore.csproj`:
+   - `sqlserver` → `Microsoft.EntityFrameworkCore.SqlServer`
+   - `postgresql` → `Npgsql.EntityFrameworkCore.PostgreSQL`
+   - `mysql` → `Pomelo.EntityFrameworkCore.MySql`
+   - `mongodb` → `MongoDB.EntityFrameworkCore` (or use the driver directly, skip EF Core)
+4. Create initial migration:
+   ```bash
+   dotnet ef migrations add InitialCreate --project {Name}.Persistence.EfCore
+   ```
+5. Build + run:
+   ```bash
+   dotnet build
+   dotnet run --project {Name}.WebApi
+   ```
+
+## Guardrails
+
+- DO NOT scaffold on top of an existing solution. Verify target dir has no `.sln` first.
+- DO NOT add stray top-level projects (e.g. `Common`, `Shared`) outside Onion layers — extend `Domain.Shared` or `Infrastructure` instead.
+- DO NOT let `WebApi` reference `Application` directly — go through `Application.Contracts` to keep boundaries clean.
+- DO NOT pin to outdated Torus NuGet versions — `torus-bootstrap` resolves current versions; trust its choices unless PRD overrides.
+- Multi-tenancy reshapes DbContext + middleware significantly — only enable if PRD / SAD explicitly calls for it.
+- Captcha / OPA / Distributed Lock add infra dependencies — only enable when AC requires them.
+
+## Integration with TAS commands
+
+- **`/tas-plan`** — when Feature requires a new .NET backend project, include a `Bootstrap` step in the Execution Plan referencing this rule. Pin the exact `torus-bootstrap create ...` command (with all chosen flags) in the Technical file so `/tas-dev` can replay it deterministically.
+- **`/tas-dev`** — before writing application code, if no `*.sln` exists in target dir, run the bootstrap command from the Technical Plan, then continue with regular Tasks.
+
+## Reference
+
+Full bootstrap CLI docs: [`.tas/templates/torus-dotnet-bootstrap.md`](../../templates/torus-dotnet-bootstrap.md).

package/.tas/tas-example.yaml

@@ -5,7 +5,7 @@
 
 project:
   name: "My Project"
-  code: "PROJ"              # Prefix for file naming: PROJ-Epic-001, PROJ-Feature-001, etc.
+  code: "PROJ"              # Prefix for file naming: PROJ-Feature-001, PROJ-Bug-001, etc.
   type: greenfield          # greenfield | brownfield
   description: "Brief project description"
 
@@ -37,9 +37,8 @@ workflow:
       - design_spec
       - sad
       - adr
-      - epic
-      - feature
-      - story
+      - feature              # Business spec — replaces Epic + Story (single unit per business flow per stack)
+      - feature_technical    # Technical plan generated by /tas-plan
     gate: ready_for_development
 
   # Phase 1: Develop (Orchestrated Agentic)
@@ -49,6 +48,12 @@ workflow:
     environment: test
     use_tdd: true
     auto_review: true
+    # Autonomy mode for /tas-dev + /tas-plan.
+    # manual (default) — human gates: plan approval, SAD/ADR ask, deviation prompt, Done confirm.
+    # full — skip gates: auto-pick approach, write Technical file straight, auto-Done if review passes.
+    # CLI flag --autonomous=true|false on /tas-dev or /tas-plan overrides this per-call.
+    # Hard gates remain even in `full`: post-impl review still runs; Critical/High blocks auto-Done; ADR creation stays human-triggered.
+    autonomy_mode: manual
 
   # Phase 2: Verify (Agentic + PE Review)
   verify:
@@ -95,31 +100,3 @@ security:
   deep_scan_on_every_commit: false         # true = opt into tier 3 AI review each local commit
   block_on: [critical, high]               # severities that block commit (tier 1 & 2 only)
   allow_bypass: true                       # print hint about SKIP_SECURITY_SCAN / --no-verify
-
-# Template overrides (optional)
-templates:
-  sad: ".tas/templates/SAD.md"
-  adr: ".tas/templates/ADR.md"
-  prd: ".tas/templates/PRD.md"
-  epic: ".tas/templates/Epic.md"
-  feature: ".tas/templates/Feature.md"
-  story: ".tas/templates/Story.md"
-  bug: ".tas/templates/Bug.md"
-
-# Model mapping
-models:
-  default: sonnet
-  commands:
-    tas-prd: sonnet
-    tas-design: sonnet
-    tas-sad: opus
-    tas-adr: opus
-    tas-epic: sonnet
-    tas-feature: sonnet
-    tas-story: sonnet
-    tas-dev: sonnet
-    tas-review: opus
-    tas-brainstorm: opus
-    tas-bug: sonnet
-    tas-status: haiku
-    tas-security: opus

package/.tas/templates/AGENTS.md

@@ -35,3 +35,16 @@
 ## Key Workflows
 <!-- Common commands for this project -->
 Type /[command-name] to [describe what it does].
+
+## TAS Flow (kit v3 — Feature-only)
+
+> Epic and User Story are NOT used. Each piece of work = one Feature per stack (`app` | `web` | `service` | `integration`), small enough to release in 1 day of dev.
+
+Typical loop:
+1. `/tas-prd` — capture business requirements (PE)
+2. `/tas-feature` — create `docs/features/{CODE}-Feature-NNN-{slug}/{CODE}-Feature-NNN-{slug}.md` with AC in Given/When/Then (PE)
+3. `/tas-plan` — generate `{CODE}-Feature-NNN-{slug}-Technical.md` with Context Diagram, Logic Flow, Data Flow, ERD, File Changes, Config, SAD impact, ADR need (SE)
+4. `/tas-dev` — implement per Technical Plan + Definition of Done (SE)
+5. `/tas-functest` + `/tas-functest-{mobile|web}` — generate FT spec + scripts (QA/SE)
+6. `/tas-e2e` + `/tas-e2e-{mobile|web}` — chain Features into end-to-end scenarios (QA/PE)
+7. `/tas-review` — multi-agent review before release

package/.tas/templates/API-Test-Spec.md

@@ -8,7 +8,7 @@ status:
 created_date:
 updated_date:
 executor:
-story_id:
+feature_id:
 framework: xUnit
 ---
 
@@ -22,7 +22,7 @@ framework: xUnit
 **Status**: [status] (Draft | Review | Approved | Deprecated)
 **Spec Source**: [spec_source]
 **Code Path**: [code_path]
-**Story**: [story_id] (if applicable)
+**Feature**: [feature_id] (if applicable)
 
 ---
 
@@ -352,9 +352,10 @@ framework: xUnit
 
 ---
 
-## Story-Specific Test Cases (Optional)
+## Feature-Specific Test Cases (Optional)
 
-> If spec generated from Story, add AC mapping here.
+> If spec generated from a Feature, add AC mapping here.
+> Anchor TC IDs on AC: `{PROJECT}_F{FEATURE}_AC{N}_API_NNN_{H|N}` if you want full traceability.
 
 | AC ID | AC Description | Test Case IDs |
 |-------|----------------|---------------|

package/.tas/templates/BRD.md

@@ -0,0 +1,133 @@
+# Business Requirements Document (BRD)
+
+> **Document Status:** [Draft | In Review | Approved | Archived]
+> **Last Updated:** [Date]
+> **Business Owner:** [Name]
+> **Contributors:** [Names/Roles]
+
+---
+
+## Executive Summary
+
+**Project / Initiative Name:** [Name]
+
+**Summary:**
+[2-3 sentences: what this initiative is, what business problem it solves, expected outcome.]
+
+**Decision Required By:** [Date]
+
+---
+
+## Business Objectives
+
+1. [Primary business objective — measurable]
+2. [Secondary business objective]
+
+**KPIs / Success Criteria:**
+- [KPI 1 with target, e.g. "Reduce support tickets by 30% within 6 months"]
+- [KPI 2 with target]
+
+---
+
+## Problem Statement / Business Need
+
+**Current State:**
+[Describe the problem, pain point, or opportunity. What is broken or missing today?]
+
+**Impact:**
+[Quantify impact where possible: cost, time, revenue lost, compliance risk, etc.]
+
+**Why Now:**
+[Market timing, regulatory deadline, competitive pressure, strategic priority]
+
+---
+
+## Project Scope
+
+### In Scope
+- [Business capability / domain 1]
+- [Business capability / domain 2]
+
+### Out of Scope
+- [Explicitly excluded item 1]
+- [Explicitly excluded item 2]
+
+---
+
+## Business Requirements
+
+> High-level requirements only. No technical implementation detail.
+
+| ID | Requirement | Priority |
+|----|-------------|----------|
+| BR-001 | [Business requirement description] | Must |
+| BR-002 | [Business requirement description] | Should |
+| BR-003 | [Business requirement description] | Could |
+
+**Priority scale:** Must / Should / Could / Won't
+
+---
+
+## Stakeholders
+
+| Name / Role | Type | Interest / Concern |
+|-------------|------|--------------------|
+| [Name] — [Title] | Decision Maker | [What they care about] |
+| [Name] — [Title] | Contributor | [What they contribute] |
+| [Name] — [Title] | Informed | [What they need to know] |
+
+---
+
+## Constraints & Assumptions
+
+### Constraints
+- **Budget:** [Constraint]
+- **Timeline:** [Hard deadline if any]
+- **Legal / Regulatory:** [Compliance constraints]
+- **Technical:** [Platform, integration limits]
+
+### Assumptions
+- [Assumption 1 — what we assume to be true]
+- [Assumption 2]
+
+---
+
+## Timeline / Milestones
+
+| Milestone | Target Date | Owner |
+|-----------|-------------|-------|
+| BRD Approved | [Date] | Business Owner |
+| PRD Completed | [Date] | PE |
+| Development Start | [Date] | SE |
+| Launch | [Date] | DSE |
+
+---
+
+## Cost-Benefit / Business Case
+
+**Estimated Cost:**
+- Development: [estimate]
+- Operational: [estimate]
+
+**Expected Benefits:**
+- [Benefit 1 — quantified if possible]
+- [Benefit 2]
+
+**ROI / Payback Period:** [estimate]
+
+---
+
+## Changelog
+
+| Date | Version | Changes | Author |
+|------|---------|---------|--------|
+| [Date] | 1.0 | Initial draft | [Name] |
+
+---
+
+## AI Usage Log
+
+| # | Date | Command | Input (est.) | Output (est.) |
+|---|------|---------|-------------|---------------|
+| 1 | [Date] | /tas-brd | ~{N}k | ~{N}k |
+| **Total** | | | **~{N}k** | **~{N}k** |

package/.tas/templates/Bug.md

@@ -7,6 +7,7 @@ ado_assigned_to:
 ado_created:
 last_ado_sync:
 parent_ado_id:
+sad_impact: false
 ---
 # Bug-{NNN}: {Title}
 
@@ -49,6 +50,20 @@ parent_ado_id:
 | RT-1 | Reproduce bug case | {input} | {expected} | - |
 | RT-2 | Related regression | {input} | {expected} | - |
 
+## SAD Impact Matrix
+*SE fills during analyze step. Per `.tas/rules/common/sad-impact.md`. Set frontmatter `sad_impact: true` if any row `Detected: Yes`.*
+
+| # | Category | Detected | SAD Section | Change Summary | ADR Candidate |
+|---|----------|----------|-------------|----------------|---------------|
+| 1 | Tech Stack | No | — | — | No |
+| 2 | System Boundary | No | — | — | No |
+| 3 | Container / Topology | No | — | — | No |
+| 4 | Data Architecture | No | — | — | No |
+| 5 | API Contract | No | — | — | No |
+| 6 | Security | No | — | — | No |
+| 7 | NFR / Ops | No | — | — | No |
+| 8 | Deployment | No | — | — | No |
+
 ## Fix Notes
 *SE fills after fixing*
 - **Fix Description:** {Fix description}

package/.tas/templates/E2E-Execution-Report.md

@@ -3,9 +3,9 @@ created_date:
 executor:
 status: # Pass | Fail | Partial
 test_layer: # functional | e2e
-scenario_id:
-feature_id:
-epic_id:
+scenario_id:               # filled when test_layer = e2e
+feature_id:                # filled when test_layer = functional (single Feature)
+feature_ids:               # filled when test_layer = e2e (comma-separated Features in scenario)
 platform: # mobile-ios | mobile-android | web-chromium | web-firefox | web-webkit
 environment: # dev | staging | prod
 ---
@@ -40,9 +40,9 @@ environment: # dev | staging | prod
 
 | Test ID | AC Ref | Description | Result | Duration | Failure Reason |
 |---------|--------|-------------|--------|----------|----------------|
-| {PROJECT}_E{EPIC}_F{FEATURE}_S{STORY}_FT_001_H | AC-1 | {description} | PASS | {Xs} | - |
-| {PROJECT}_E{EPIC}_F{FEATURE}_S{STORY}_FT_002_N | AC-1 | {description} | PASS | {Xs} | - |
-| {PROJECT}_E{EPIC}_F{FEATURE}_S{STORY}_FT_003_E | AC-1 | {description} | FAIL | {Xs} | {brief reason: element not found / assertion mismatch / timeout / ...} |
+| {PROJECT}_F{FEATURE}_AC1_FT_001_H | AC-1 | {description} | PASS | {Xs} | - |
+| {PROJECT}_F{FEATURE}_AC1_FT_002_N | AC-1 | {description} | PASS | {Xs} | - |
+| {PROJECT}_F{FEATURE}_AC1_FT_003_E | AC-1 | {description} | FAIL | {Xs} | {brief reason: element not found / assertion mismatch / timeout / ...} |
 
 ---
 
@@ -133,8 +133,8 @@ environment: # dev | staging | prod
 
 | AC ID | FT Tests | E2E Tests | Covered | Status |
 |-------|----------|-----------|---------|--------|
-| AC-1 | FT_001_H, FT_002_N | E2E_001 (Step 1) | Yes | All Pass |
-| AC-2 | FT_003_H | E2E_001 (Step 3) | Yes | 1 Fail |
+| AC-1 | F012_AC1_FT_001_H, F012_AC1_FT_002_N | E2E_001 (Step 1) | Yes | All Pass |
+| AC-2 | F012_AC2_FT_001_H | E2E_001 (Step 3) | Yes | 1 Fail |
 | AC-3 | - | - | No | Not tested |
 
 ### Uncovered Areas

package/.tas/templates/E2E-Mobile-Spec.md

@@ -2,18 +2,16 @@
 created_date:
 executor:
 status: Draft
-story_id:
-feature_id:
-epic_id:
+feature_ids: # comma-separated Feature IDs chained in this scenario
+scenario_id:
 ---
 
 # E2E Mobile Test Specification
 
-**Epic**: [EPIC_LINK]  
-**Feature**: [FEATURE_LINK]  
-**Story**: [STORY_LINK]  
-**Author**: @[executor]  
-**Created**: [created_date]  
+**Scenario**: [{Scenario_ID}]({SCENARIO_LINK})
+**Features**: {feature_ids}
+**Author**: @[executor]
+**Created**: [created_date]
 **Status**: [status]
 
 ---

package/.tas/templates/E2E-Report.md

@@ -3,8 +3,8 @@ created_date:
 executed_date:
 executor:
 status: Draft
-story_id:
-feature_id:
+feature_ids: # comma-separated Feature IDs covered by this report
+scenario_id: # if this report covers an E2E scenario (cross-Feature)
 environment: Local
 ---
 

package/.tas/templates/E2E-Scenario.md

@@ -3,15 +3,15 @@ created_date:
 updated_date:
 executor:
 status: Draft
-epic_id: # Single epic ID, or "XEPIC" for cross-epic
-scenario_type: # single-epic | cross-epic
+feature_ids: # comma-separated list of Features chained in this scenario, or "XSTACK" for cross-stack
+scenario_type: # single-stack | cross-stack
 platform: # mobile | web | both
 ---
 
 # E2E Scenario: {Scenario Name}
 
-**Epic(s)**: [{Epic_ID}]({link}) {{#if cross-epic}} + [{Epic_ID_2}]({link2}) {{/if}}
-**Scenario Type**: {{scenario_type}} (single-epic | cross-epic)
+**Features**: [{Feature_ID_1}]({link1}) {{#if cross-stack}} + [{Feature_ID_2}]({link2}) {{/if}}
+**Scenario Type**: {{scenario_type}} (single-stack | cross-stack)
 **Platform**: {{platform}}
 **Author**: @[executor]
 **Created**: [created_date]
@@ -21,17 +21,17 @@ platform: # mobile | web | both
 
 ## Scenario Naming Convention
 
-### Single-Epic E2E
+### Single-Stack E2E
 ```
-{PROJECT}_E{EPIC}_E2E_{NUMBER}_{MODIFIER}
+{PROJECT}_E2E_{NUMBER}_{MODIFIER}
 ```
-Example: `AL_E002_E2E_001_H` - Full auth flow happy path
+Example: `AL_E2E_001_H` — full auth flow happy path (all Features in `web` stack)
 
-### Cross-Epic E2E
+### Cross-Stack E2E
 ```
-{PROJECT}_XEPIC_E2E_{NUMBER}_{MODIFIER}
+{PROJECT}_XSTACK_E2E_{NUMBER}_{MODIFIER}
 ```
-Example: `AL_XEPIC_E2E_001_H` - Registration through first scan journey
+Example: `AL_XSTACK_E2E_001_H` — registration (web) → KYC service → first scan (app)
 
 ---
 
@@ -40,7 +40,7 @@ Example: `AL_XEPIC_E2E_001_H` - Registration through first scan journey
 > Narrative description of the end-to-end user journey.
 > This scenario tests {what} by simulating {user type} performing {complete flow}.
 
-**User Persona**: {Clinical / Organic / New User / Returning User}
+**User Persona**: {persona / role}
 **Starting Point**: {Screen/Page where flow begins}
 **End Point**: {Screen/Page where flow ends}
 **Estimated Duration**: {X minutes}
@@ -51,11 +51,11 @@ Example: `AL_XEPIC_E2E_001_H` - Registration through first scan journey
 
 | Step | Screen/Page | Action | Expected Result | Builds on FT IDs | Priority |
 |------|-------------|--------|-----------------|-------------------|----------|
-| 1 | {Start Screen} | {User action} | {Expected outcome} | {PROJECT}_E{EPIC}_F{FEATURE}_S{STORY}_FT_001_H | P0 |
-| 2 | {Next Screen} | {User action} | {Expected outcome} | {PROJECT}_E{EPIC}_F{FEATURE}_S{STORY}_FT_002_H | P0 |
-| 3 | {Next Screen} | {User action} | {Expected outcome} | {PROJECT}_E{EPIC}_F{FEATURE}_S{STORY}_FT_003_H | P0 |
+| 1 | {Start Screen} | {User action} | {Expected outcome} | {PROJECT}_F{FEATURE}_AC1_FT_001_H | P0 |
+| 2 | {Next Screen} | {User action} | {Expected outcome} | {PROJECT}_F{FEATURE}_AC1_FT_002_H | P0 |
+| 3 | {Next Screen} | {User action} | {Expected outcome} | {PROJECT}_F{FEATURE}_AC2_FT_001_H | P0 |
 | 4 | {Next Screen} | {User action} | {Expected outcome} | - (new step, no FT reference) | P1 |
-| 5 | {End Screen} | {Verify final state} | {Final expected state} | {PROJECT}_E{EPIC}_F{FEATURE}_S{STORY}_FT_005_H | P0 |
+| 5 | {End Screen} | {Verify final state} | {Final expected state} | {PROJECT}_F{FEATURE}_AC2_FT_003_H | P0 |
 
 ### Step Details
 
@@ -64,7 +64,7 @@ Example: `AL_XEPIC_E2E_001_H` - Registration through first scan journey
 - **Preconditions**: {What must be true before this step}
 - **Action**: {Detailed user action}
 - **Expected Result**: {What should happen}
-- **FT Reference**: Reuses logic from `{FT_ID}` in `features/{epic}/{feature}/helpers.ts`
+- **FT Reference**: Reuses logic from `{FT_ID}` in `features/{feature-slug}/helpers.ts`
 - **Timeout**: {Expected max time for this step}
 
 #### Step 2: {Action Title}
@@ -116,7 +116,7 @@ _(Continue for each step)_
 ## Prerequisites
 
 - [ ] User account exists in target environment
-- [ ] Required test data seeded (products, allergens, etc.)
+- [ ] Required test data seeded
 - [ ] Backend services running and accessible
 - [ ] External service stubs/mocks configured (if applicable)
 - [ ] Device/browser configured and ready
@@ -151,12 +151,12 @@ _(Continue for each step)_
 
 ### Mobile Script Output
 - **File**: `apps/mobile/e2e/flows/{scenario-slug}.e2e.ts`
-- **Reuses**: Helper functions from `apps/mobile/e2e/features/{epic}/{feature}/helpers.ts`
+- **Reuses**: Helper functions from `apps/mobile/e2e/features/{feature-slug}/helpers.ts`
 - **Run**: `yarn e2e:flow:{scenario-slug}`
 
 ### Web Script Output
 - **File**: `apps/web/e2e/flows/{scenario-slug}.spec.ts`
-- **Reuses**: Page objects + helpers from `apps/web/e2e/features/{epic}/{feature}/`
+- **Reuses**: Page objects + helpers from `apps/web/e2e/features/{feature-slug}/`
 - **Run**: `yarn e2e:flow:{scenario-slug}`
 
 ---
@@ -167,9 +167,9 @@ _(Continue for each step)_
 
 | Step | FT ID | Source File | Helper Function |
 |------|-------|-------------|-----------------|
-| 1 | {FT_ID_1} | `features/{epic}/{feature}/helpers.ts` | `{functionName}()` |
-| 2 | {FT_ID_2} | `features/{epic}/{feature}/helpers.ts` | `{functionName}()` |
-| 3 | - | (new logic) | N/A - write new code |
+| 1 | {FT_ID_1} | `features/{feature-slug}/helpers.ts` | `{functionName}()` |
+| 2 | {FT_ID_2} | `features/{feature-slug}/helpers.ts` | `{functionName}()` |
+| 3 | - | (new logic) | N/A — write new code |
 
 ---