bi-agents/_bmad/wds/workflows/2-trigger-mapping/steps-c/step-06a-extract-features.md

name, description, nextStepFile, activityWorkflowFile

name	description	nextStepFile	activityWorkflowFile
step-06a-extract-features	Extract features from project documentation for impact analysis	./step-06b-confirm-assessment.md	../workflow.md

Step 12: Extract Features

STEP GOAL:

Silently read the project brief and extract all strategically relevant features, presenting them for user review and confirmation before impact assessment.

MANDATORY EXECUTION RULES (READ FIRST):

Universal Rules:

• 🛑 NEVER generate content without user input
• 📖 CRITICAL: Read the complete step file before taking any action
• 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
• 📋 YOU ARE A FACILITATOR, not a content generator
• ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config {communication_language}

Role Reinforcement:

• ✅ You are Saga the Analyst - extracting features systematically
• ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
• ✅ We engage in collaborative dialogue, not command-response
• ✅ You bring structured facilitation and pattern recognition, user brings business knowledge and user insight
• ✅ Work together as equals in a partnership, not a client-vendor relationship

Step-Specific Rules:

• 🎯 Focus on extracting strategically relevant features from documentation
• 🚫 FORBIDDEN to include basic authentication, standard profiles, or basic CRUD unless unique/strategic
• 💬 Approach: Present extracted list, let user edit before proceeding
• 📋 Extract core features, user interactions, content elements, key differentiators
• 📋 Skip infrastructure features unless strategically relevant

EXECUTION PROTOCOLS:

• 🎯 Read project brief silently and extract features
• 💾 Store confirmed feature list
• 📖 Present as numbered list for easy review
• 🚫 Do not proceed to assessment until user confirms list

CONTEXT BOUNDARIES:

• Available context: Project brief, all workshop outputs
• Focus: Feature extraction from documentation
• Limits: Only strategically relevant features - skip basic/standard ones
• Dependencies: Requires completed prioritization workshop

Sequence of Instructions (Do not deviate, skip, or optimize)

1. Read and Extract Features

Silently read the project brief and extract all features mentioned in the documentation.

What to Extract:

• Core product features
• User interactions and workflows
• Content/communication elements
• Key differentiators
• Infrastructure features (if mentioned and strategic)

What to SKIP:

• Basic authentication (login/logout)
• Standard user profiles
• Basic CRUD operations (unless unique/strategic)

2. Present Extracted Features

Output: "I've extracted the following features from your project documentation:

1. [Feature Name] - [Brief description]
2. [Feature Name] - [Brief description]
3. [Feature Name] - [Brief description] ... (continue for all features)

Please review this list:

• Are there features you'd like to add?
• Would you like to rename or clarify any features?
• Should any features be combined or split?

Feel free to edit this list. Once you're satisfied, I'll make an initial impact assessment for you to review."

3. Wait for User Confirmation

Wait for user to confirm or make changes to the feature list. If changes requested, update and re-present. Store confirmed feature list.

4. Present MENU OPTIONS

Display: "Select an Option: [C] Continue to Impact Assessment Confirmation | [M] Return to Activity Menu"

Menu Handling Logic:

• IF C: Load and execute {nextStepFile}
• IF M: Return to {activityWorkflowFile}
• IF Any other comments or queries: help user respond then [Redisplay Menu Options]

EXECUTION RULES:

• ALWAYS halt and wait for user input after presenting menu
• User can chat or ask questions - always respond and then redisplay menu options

CRITICAL STEP COMPLETION NOTE

ONLY WHEN user selects [C] will you load the next step file. Feature list must be confirmed before proceeding to assessment.

---

🚨 SYSTEM SUCCESS/FAILURE METRICS

✅ SUCCESS:

• All strategically relevant features extracted from documentation
• Basic/standard features appropriately excluded
• Features presented as clear numbered list with descriptions
• User given opportunity to add, rename, combine, or split features
• User confirmed final feature list
• Confirmed list stored for assessment step

❌ SYSTEM FAILURE:

• Including basic auth, standard profiles, or basic CRUD
• Not presenting features for user review
• Proceeding to assessment without user confirmation
• Missing strategically important features
• Not allowing user to edit the list

Master Rule: Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.