Refactor workflows to support active feature context

- Updated paths in UX design, implementation readiness, architecture, and epics/stories workflows to use `{active_feature}` for organizing artifacts.
- Introduced a new workflow to set the active feature context, ensuring all subsequent artifacts are organized accordingly.
- Adjusted documentation and output file paths across multiple workflows to reflect the new structure.
- Enhanced user experience by confirming active feature settings and creating necessary subfolders.

Author: DavidsonGomes

docs/index.md

@@ -1,6 +1,6 @@
 ---
 title: Welcome to the EVO Method
-description: AI-driven development framework with specialized agents, guided workflows, and intelligent planning
+description: Context engineering for AI-powered development
 ---
 
 The EVO Method (**B**uild **M**ore **A**rchitect **D**reams) is an AI-driven development framework module within the EVO Method Ecosystem that helps you build software through the whole process from ideation and planning all the way through agentic implementation. It provides specialized AI agents, guided workflows, and intelligent planning that adapts to your project's complexity, whether you're fixing a bug or building an enterprise platform.

package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "@evoapi/evo-method",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "Evolve, Validate, Orchestrate — AI-driven Agile Development Method",
   "keywords": [
     "agile",

src/bmm/module-help.csv

@@ -1,4 +1,5 @@
 module,phase,name,code,sequence,workflow-file,command,required,agent,options,description,output-location,outputs,
+bmm,anytime,Set Feature,SF,,_evo/bmm/workflows/set-feature/workflow.md,evo-bmm-set-feature,false,sm,,"Set or switch the active feature context for artifact subfolder organization",,,
 bmm,anytime,Document Project,DP,,_evo/bmm/workflows/document-project/workflow.md,evo-bmm-document-project,false,analyst,Create Mode,"Analyze an existing project to produce useful documentation",project-knowledge,*,
 bmm,anytime,Generate Project Context,GPC,,_evo/bmm/workflows/generate-project-context/workflow.md,evo-bmm-generate-project-context,false,analyst,Create Mode,"Scan existing codebase to generate a lean LLM-optimized project-context.md containing critical implementation rules patterns and conventions for AI agents. Essential for brownfield projects and quick-flow.",output_folder,"project context",
 bmm,anytime,Quick Spec,QS,,_evo/bmm/workflows/evo-quick-flow/quick-spec/workflow.md,evo-bmm-quick-spec,false,quick-flow-solo-dev,Create Mode,"Do not suggest for potentially very complex things unless requested or if the user complains that they do not want to follow the extensive planning of the evo method. Quick one-off tasks small changes simple apps brownfield additions to well established patterns utilities without extensive planning",planning_artifacts,"tech spec",

src/bmm/module.yaml

@@ -43,6 +43,11 @@ project_knowledge: # Artifacts from research, document-project output, other lon
   default: "docs"
   result: "{project-root}/{value}"
 
+active_feature: # Current feature/implementation context — used as subfolder inside planning/implementation artifacts
+  prompt: "What is the active feature slug? (e.g. admin-panel, auth-refactor) — used as subfolder inside planning and implementation artifacts"
+  default: ""
+  result: "{value}"
+
 # Directories to create during installation (declarative, no code execution)
 directories:
   - "{planning_artifacts}"

src/bmm/workflows/1-analysis/create-product-brief/steps/step-01-init.md

@@ -4,7 +4,7 @@ description: 'Initialize the product brief workflow by detecting continuation st
 
 # File References
 nextStepFile: '{project-root}/_evo/bmm/workflows/1-analysis/create-product-brief/steps/step-02-vision.md'
-outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
+outputFile: '{planning_artifacts}/{active_feature}/product-brief-{{project_name}}.md'
 
 # Template References
 productBriefTemplate: '../product-brief.template.md'
@@ -57,6 +57,19 @@ Initialize the product brief workflow by detecting continuation state and settin
 
 ## Sequence of Instructions (Do not deviate, skip, or optimize)
 
+### 0. Validate Active Feature
+
+Before any other action, check if `{active_feature}` is set (non-empty) in the loaded config.
+
+**If `{active_feature}` is empty:**
+- Inform the user: "No active feature is set. Please provide a feature slug (e.g. `admin-panel`, `auth-refactor`) to organize artifacts into a subfolder."
+- Wait for user input
+- Update `{project-root}/_evo/bmm/config.yaml`: set `active_feature` to the provided slug
+- Create subfolders: `{planning_artifacts}/{{active_feature}}/` and `{implementation_artifacts}/{{active_feature}}/`
+- Confirm: "Active feature set to **{{active_feature}}**. Artifacts will be saved to `{planning_artifacts}/{{active_feature}}/`."
+
+**If `{active_feature}` is already set:** proceed directly to the next step.
+
 ### 1. Check for Existing Workflow State
 
 First, check if the output document already exists:

src/bmm/workflows/1-analysis/create-product-brief/steps/step-01b-continue.md

@@ -3,7 +3,7 @@ name: 'step-01b-continue'
 description: 'Resume the product brief workflow from where it was left off, ensuring smooth continuation'
 
 # File References
-outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
+outputFile: '{planning_artifacts}/{active_feature}/product-brief-{{project_name}}.md'
 ---
 
 # Step 1B: Product Brief Continuation

src/bmm/workflows/1-analysis/create-product-brief/steps/step-02-vision.md

@@ -4,7 +4,7 @@ description: 'Discover and define the core product vision, problem statement, an
 
 # File References
 nextStepFile: '{project-root}/_evo/bmm/workflows/1-analysis/create-product-brief/steps/step-03-users.md'
-outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
+outputFile: '{planning_artifacts}/{active_feature}/product-brief-{{project_name}}.md'
 
 # Task References
 advancedElicitationTask: '{project-root}/_evo/core/workflows/advanced-elicitation/workflow.md'

src/bmm/workflows/1-analysis/create-product-brief/steps/step-03-users.md

@@ -4,7 +4,7 @@ description: 'Define target users with rich personas and map their key interacti
 
 # File References
 nextStepFile: '{project-root}/_evo/bmm/workflows/1-analysis/create-product-brief/steps/step-04-metrics.md'
-outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
+outputFile: '{planning_artifacts}/{active_feature}/product-brief-{{project_name}}.md'
 
 # Task References
 advancedElicitationTask: '{project-root}/_evo/core/workflows/advanced-elicitation/workflow.md'

src/bmm/workflows/1-analysis/create-product-brief/steps/step-04-metrics.md

@@ -4,7 +4,7 @@ description: 'Define comprehensive success metrics that include user success, bu
 
 # File References
 nextStepFile: '{project-root}/_evo/bmm/workflows/1-analysis/create-product-brief/steps/step-05-scope.md'
-outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
+outputFile: '{planning_artifacts}/{active_feature}/product-brief-{{project_name}}.md'
 
 # Task References
 advancedElicitationTask: '{project-root}/_evo/core/workflows/advanced-elicitation/workflow.md'

src/bmm/workflows/1-analysis/create-product-brief/steps/step-05-scope.md

@@ -4,7 +4,7 @@ description: 'Define MVP scope with clear boundaries and outline future vision w
 
 # File References
 nextStepFile: '{project-root}/_evo/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md'
-outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
+outputFile: '{planning_artifacts}/{active_feature}/product-brief-{{project_name}}.md'
 
 # Task References
 advancedElicitationTask: '{project-root}/_evo/core/workflows/advanced-elicitation/workflow.md'