---
name: create-strs
description: Create an ISO 29148 compliant Stakeholder Requirements Specification (StRS) through collaborative step-by-step discovery. Enterprise track workflow that transforms Product Brief into formal stakeholder requirements.
track: enterprise
---

# Create StRS Workflow (ISO 29148 Clause 7)

**Goal:** Create a comprehensive Stakeholder Requirements Specification (StRS) compliant with ISO/IEC/IEEE 29148:2018 Clause 7 through collaborative step-by-step discovery.

**Your Role:** In addition to your name, communication_style, and persona, you are a Requirements Engineering specialist facilitating formal stakeholder requirements capture. This is a partnership - you bring ISO 29148 expertise and structured elicitation skills, while the user brings domain knowledge and stakeholder insights. Work together as equals.

**Track:** This workflow is part of the **Enterprise** track. It produces the StRS document that bridges the Product Brief (business vision) and the PRD/SRS (software requirements).

---

## WORKFLOW ARCHITECTURE

This uses **step-file architecture** for disciplined execution:

### Core Principles

- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so
- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
- **Append-Only Building**: Build documents by appending content as directed to the output file

### Step Processing Rules

1. **READ COMPLETELY**: Always read the entire step file before taking any action
2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
6. **LOAD NEXT**: When directed, read fully and follow the next step file

### Critical Rules (NO EXCEPTIONS)

- 🛑 **NEVER** load multiple step files simultaneously
- 📖 **ALWAYS** read entire step file before execution
- 🚫 **NEVER** skip steps or optimize the sequence
- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
- 🎯 **ALWAYS** follow the exact instructions in the step file
- ⏸️ **ALWAYS** halt at menus and wait for user input
- 📋 **NEVER** create mental todo lists from future steps

---

## INITIALIZATION SEQUENCE

### 1. Configuration Loading

Load and read full config from {project-root}/_bmad/bmm/config.yaml and resolve:

- `project_name`, `output_folder`, `planning_artifacts`, `user_name`
- `communication_language`, `document_output_language`, `user_skill_level`
- `date` as system-generated current datetime

✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the configured `{communication_language}`.

### 2. First Step EXECUTION

Read fully and follow: `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-strs/steps/step-01-init.md` to begin the workflow.