diff --git a/package-lock.json b/package-lock.json index 512261e6..d2e4f718 100644 --- a/package-lock.json +++ b/package-lock.json @@ -95,7 +95,6 @@ "integrity": "sha512-yDBHV9kQNcr2/sUr9jghVyz9C3Y5G2zUM2H2lo+9mKv4sFgbA8s8Z9t8D1jiTkGoO/NoIfKMyKWr4s6CN23ZwQ==", "dev": true, "license": "MIT", - "peer": true, "dependencies": { "@ampproject/remapping": "^2.2.0", "@babel/code-frame": "^7.27.1", @@ -1818,7 +1817,6 @@ "integrity": "sha512-aPTXCrfwnDLj4VvXrm+UUCQjNEvJgNA8s5F1cvwQU+3KNltTOkBm1j30uNLyqqPNe7gE3KFzImYoZEfLhp4Yow==", "devOptional": true, "license": "MIT", - "peer": true, "dependencies": { "undici-types": "~7.10.0" } @@ -2135,7 +2133,6 @@ "integrity": "sha512-NZyJarBfL7nWwIq+FDL6Zp/yHEhePMNnnJ0y3qfieCrmNvYct8uvtiV41UvlSe6apAfk0fY1FbWx+NwfmpvtTg==", "dev": true, "license": "MIT", - "peer": true, "bin": { "acorn": "bin/acorn" }, @@ -2497,7 +2494,6 @@ } ], "license": "MIT", - "peer": true, "dependencies": { "caniuse-lite": "^1.0.30001735", "electron-to-chromium": "^1.5.204", @@ -3352,7 +3348,6 @@ "integrity": "sha512-RNCHRX5EwdrESy3Jc9o8ie8Bog+PeYvvSR8sDGoZxNFTvZ4dlxUB3WzQ3bQMztFrSRODGrLLj8g6OFuGY/aiQg==", "dev": true, "license": "MIT", - "peer": true, "dependencies": { "@eslint-community/eslint-utils": "^4.2.0", "@eslint-community/regexpp": "^4.12.1", @@ -7092,7 +7087,6 @@ "integrity": "sha512-I7AIg5boAr5R0FFtJ6rCfD+LFsWHp81dolrFD8S79U9tb8Az2nGrJncnMSnys+bpQJfRUzqs9hnA81OAA3hCuQ==", "dev": true, "license": "MIT", - "peer": true, "bin": { "prettier": "bin/prettier.cjs" }, @@ -7915,7 +7909,6 @@ "integrity": "sha512-5gTmgEY/sqK6gFXLIsQNH19lWb4ebPDLA4SdLP7dsWkIXHWlG66oPuVvXSGFPppYZz8ZDZq0dYYrbHfBCVUb1Q==", "dev": true, "license": "MIT", - "peer": true, "engines": { "node": ">=12" }, diff --git a/src/core/workflows/brainstorming/instructions.md b/src/core/workflows/brainstorming/instructions.md index a236756d..7e5a1a24 100644 --- a/src/core/workflows/brainstorming/instructions.md +++ b/src/core/workflows/brainstorming/instructions.md @@ -9,19 +9,23 @@ Check if context data was provided with workflow invocation -If data attribute was passed to this workflow: -Load the context document from the data file path -Study the domain knowledge and session focus -Use the provided context to guide the session -Acknowledge the focused brainstorming goal -I see we're brainstorming about the specific domain outlined in the context. What particular aspect would you like to explore? -Else (no context data provided): -Proceed with generic context gathering -1. What are we brainstorming about? -2. Are there any constraints or parameters we should keep in mind? -3. Is the goal broad exploration or focused ideation on specific aspects? + + + Load the context document from the data file path + Study the domain knowledge and session focus + Use the provided context to guide the session + Acknowledge the focused brainstorming goal + I see we're brainstorming about the specific domain outlined in the context. What particular aspect would you like to explore? + + + + Proceed with generic context gathering + 1. What are we brainstorming about? + 2. Are there any constraints or parameters we should keep in mind? + 3. Is the goal broad exploration or focused ideation on specific aspects? Wait for user response before proceeding. This context shapes the entire session. + session_topic, stated_goals @@ -40,19 +44,19 @@ Based on the context from Step 1, present these four approach options: Which approach would you prefer? (Enter 1-4) -Based on selection, proceed to appropriate sub-step - Load techniques from {brain_techniques} CSV file Parse: category, technique_name, description, facilitation_prompts - If strong context from Step 1 (specific problem/goal) - Identify 2-3 most relevant categories based on stated_goals - Present those categories first with 3-5 techniques each - Offer "show all categories" option + + Identify 2-3 most relevant categories based on stated_goals + Present those categories first with 3-5 techniques each + Offer "show all categories" option + - Else (open exploration) - Display all 7 categories with helpful descriptions + + Display all 7 categories with helpful descriptions + Category descriptions to guide selection: - **Structured:** Systematic frameworks for thorough exploration diff --git a/src/core/workflows/party-mode/instructions.md b/src/core/workflows/party-mode/instructions.md index 890349d5..b7b68303 100644 --- a/src/core/workflows/party-mode/instructions.md +++ b/src/core/workflows/party-mode/instructions.md @@ -78,20 +78,23 @@ - If an agent asks the user a direct question: + Clearly highlight the question End that round of responses Display: "[Agent Name]: [Their question]" Display: "[Awaiting user response...]" WAIT for user input before continuing + - If agents ask each other questions: + Allow natural back-and-forth in the same response round Maintain conversational flow + - If discussion becomes circular or repetitive: + The BMad Master will summarize Redirect to new aspects or ask for user guidance + @@ -111,15 +114,18 @@ - If user message contains any {{exit_triggers}}: + Have agents provide brief farewells in character Thank user for the discussion Exit party mode + - If user seems done or conversation naturally concludes: + Would you like to continue the discussion or end party mode? - If user indicates end: + Exit party mode + + diff --git a/src/modules/bmm/workflows/1-analysis/game-brief/instructions.md b/src/modules/bmm/workflows/1-analysis/game-brief/instructions.md index 35317a63..e499cb65 100644 --- a/src/modules/bmm/workflows/1-analysis/game-brief/instructions.md +++ b/src/modules/bmm/workflows/1-analysis/game-brief/instructions.md @@ -300,9 +300,10 @@ This brief will serve as the primary input for creating the Game Design Document - Proceed to GDD workflow: `workflow gdd` - Validate assumptions with target players -If user chooses option 3 (executive summary): -Create condensed 3-page executive brief focusing on: core concept, target market, gameplay pillars, key differentiators, and success criteria -Save as: {output_folder}/game-brief-executive-{{game_name}}-{{date}}.md + + Create condensed 3-page executive brief focusing on: core concept, target market, gameplay pillars, key differentiators, and success criteria + Save as: {output_folder}/game-brief-executive-{{game_name}}-{{date}}.md + final_brief executive_brief diff --git a/src/modules/bmm/workflows/1-analysis/product-brief/instructions.md b/src/modules/bmm/workflows/1-analysis/product-brief/instructions.md index 9312ec97..ab388954 100644 --- a/src/modules/bmm/workflows/1-analysis/product-brief/instructions.md +++ b/src/modules/bmm/workflows/1-analysis/product-brief/instructions.md @@ -264,9 +264,10 @@ Which approach works best for you? This brief will serve as the primary input for creating the Product Requirements Document (PRD). -If user chooses option 3 (executive summary): -Create condensed 3-page executive brief focusing on: problem statement, proposed solution, target users, MVP scope, financial impact, and strategic alignment -Save as: {output_folder}/product-brief-executive-{{project_name}}-{{date}}.md + + Create condensed 3-page executive brief focusing on: problem statement, proposed solution, target users, MVP scope, financial impact, and strategic alignment + Save as: {output_folder}/product-brief-executive-{{project_name}}-{{date}}.md + final_brief executive_brief diff --git a/src/modules/bmm/workflows/4-implementation/correct-course/checklist.md b/src/modules/bmm/workflows/4-implementation/correct-course/checklist.md index da6f43bd..b42b2381 100644 --- a/src/modules/bmm/workflows/4-implementation/correct-course/checklist.md +++ b/src/modules/bmm/workflows/4-implementation/correct-course/checklist.md @@ -33,8 +33,8 @@ -If trigger is unclear: "Cannot proceed without understanding what caused the need for change" -If no evidence provided: "Need concrete evidence or examples of the issue before analyzing impact" +HALT: "Cannot proceed without understanding what caused the need for change" +HALT: "Need concrete evidence or examples of the issue before analyzing impact" @@ -261,9 +261,9 @@ -If any critical section cannot be completed: "Cannot proceed to proposal without complete impact analysis" -If user approval not obtained: "Must have explicit approval before implementing changes" -If handoff responsibilities unclear: "Must clearly define who will execute the proposed changes" +HALT: "Cannot proceed to proposal without complete impact analysis" +HALT: "Must have explicit approval before implementing changes" +HALT: "Must clearly define who will execute the proposed changes" diff --git a/src/modules/bmm/workflows/4-implementation/dev-story/instructions.md b/src/modules/bmm/workflows/4-implementation/dev-story/instructions.md index a1780648..fb263504 100644 --- a/src/modules/bmm/workflows/4-implementation/dev-story/instructions.md +++ b/src/modules/bmm/workflows/4-implementation/dev-story/instructions.md @@ -50,9 +50,9 @@ Parse sections: Story, Acceptance Criteria, Tasks/Subtasks, Dev Notes, Dev Agent Record, File List, Change Log, Status Identify first incomplete task (unchecked [ ]) in Tasks/Subtasks - If no incomplete tasks → Completion sequence - If story file inaccessible → HALT: "Cannot develop story without access to story file" - If task requirements ambiguous → ASK user to clarify or HALT + Completion sequence + HALT: "Cannot develop story without access to story file" + ASK user to clarify or HALT @@ -88,11 +88,11 @@ Story is already marked in-progress Plan implementation steps and edge cases; write down a brief plan in Dev Agent Record → Debug Log Implement the task COMPLETELY including all subtasks, following architecture patterns and coding standards in this repo Handle error conditions and edge cases appropriately - If unapproved dependencies are needed → ASK user for approval before adding - If 3 consecutive implementation failures occur → HALT and request guidance - If required configuration is missing → HALT: "Cannot proceed without necessary configuration files" - If {{run_until_complete}} == true → Do not stop after partial progress; continue iterating tasks until all ACs are satisfied or a HALT condition triggers - Do NOT propose to pause for review, standups, or validation until Step 6 gates are satisfied + ASK user for approval before adding + HALT and request guidance + HALT: "Cannot proceed without necessary configuration files" + Do not stop after partial progress; continue iterating tasks until all ACs are satisfied or a HALT condition triggers + Do NOT propose to pause for review, standups, or validation until Step 6 gates are satisfied @@ -108,8 +108,8 @@ Story is already marked in-progress Run the new tests to verify implementation correctness Run linting and code quality checks if configured Validate implementation meets ALL story acceptance criteria; if ACs include quantitative thresholds (e.g., test pass rate), ensure they are met before marking complete - If regression tests fail → STOP and fix before continuing - If new tests fail → STOP and fix before continuing + STOP and fix before continuing + STOP and fix before continuing @@ -118,9 +118,9 @@ Story is already marked in-progress Add completion notes to Dev Agent Record if significant changes were made (summarize intent, approach, and any follow-ups) Append a brief entry to Change Log describing the change Save the story file - Determine if more incomplete tasks remain - If more tasks remain → Next task - If no tasks remain → Completion + Determine if more incomplete tasks remain + Next task + Completion @@ -144,9 +144,9 @@ Story is marked Ready for Review in file, but sprint-status.yaml may be out of s - If any task is incomplete → Return to step 1 to complete remaining work (Do NOT finish with partial progress) - If regression failures exist → STOP and resolve before completing - If File List is incomplete → Update it before completing + Return to step 1 to complete remaining work (Do NOT finish with partial progress) + STOP and resolve before completing + Update it before completing diff --git a/src/modules/cis/workflows/storytelling/instructions.md b/src/modules/cis/workflows/storytelling/instructions.md index 066a451c..85148d18 100644 --- a/src/modules/cis/workflows/storytelling/instructions.md +++ b/src/modules/cis/workflows/storytelling/instructions.md @@ -10,20 +10,24 @@ Check if context data was provided with workflow invocation -If data attribute was passed to this workflow: -Load the context document from the data file path -Study the background information, brand details, or subject matter -Use the provided context to inform story development -Acknowledge the focused storytelling goal -I see we're crafting a story based on the context provided. What specific angle or emphasis would you like? -Else (no context data provided): -Proceed with context gathering -1. What's the purpose of this story? (e.g., marketing, pitch, brand narrative, case study) -2. Who is your target audience? -3. What key messages or takeaways do you want the audience to have? -4. Any constraints? (length, tone, medium, existing brand guidelines) + + + Load the context document from the data file path + Study the background information, brand details, or subject matter + Use the provided context to inform story development + Acknowledge the focused storytelling goal + I see we're crafting a story based on the context provided. What specific angle or emphasis would you like? + + + + Proceed with context gathering + 1. What's the purpose of this story? (e.g., marketing, pitch, brand narrative, case study) + 2. Who is your target audience? + 3. What key messages or takeaways do you want the audience to have? + 4. Any constraints? (length, tone, medium, existing brand guidelines) Wait for user response before proceeding. This context shapes the narrative approach. + story_purpose, target_audience, key_messages @@ -53,13 +57,14 @@ I can help craft your story using these proven narrative frameworks: Which framework best fits your purpose? (Enter 1-10, or ask for my recommendation) -If user asks for recommendation: -Analyze story_purpose, target_audience, and key_messages -Recommend best-fit framework with clear rationale - -Based on your {{story_purpose}} for {{target_audience}}, I recommend: -**{{framework_name}}** because {{rationale}} - + + Analyze story_purpose, target_audience, and key_messages + Recommend best-fit framework with clear rationale + + Based on your {{story_purpose}} for {{target_audience}}, I recommend: + **{{framework_name}}** because {{rationale}} + + story_type, framework_name