bmad-method 6.3.1-next.23 → 6.3.1-next.24
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -302,6 +302,18 @@ Activation is complete. Begin the workflow below.
|
|
|
302
302
|
processes - **Integration Patterns:** External service integrations, data flows <action>Extract any story-specific requirements that the
|
|
303
303
|
developer MUST follow</action>
|
|
304
304
|
<action>Identify any architectural decisions that override previous patterns</action>
|
|
305
|
+
|
|
306
|
+
<!-- Read existing code being modified — non-negotiable -->
|
|
307
|
+
<critical>📂 READ FILES BEING MODIFIED — skipping this is the primary cause of implementation failures and review cycles</critical>
|
|
308
|
+
<action>From the architecture directory structure, identify every file marked UPDATE (not NEW) that this story will touch</action>
|
|
309
|
+
<action>Read each relevant UPDATE file completely. For each one, document in dev notes:
|
|
310
|
+
- Current state: what it does today (state machine, API calls, data shapes, existing behaviors)
|
|
311
|
+
- What this story changes: the specific sections or behaviors being modified
|
|
312
|
+
- What must be preserved: existing interactions and behaviors the story must not break
|
|
313
|
+
</action>
|
|
314
|
+
<critical>A story implementation must leave the system working end-to-end — not just satisfy its stated ACs.
|
|
315
|
+
If a behavior is required for the feature to work correctly in the existing system, it is a requirement
|
|
316
|
+
whether or not it is explicitly written in the story. The dev agent owns this.</critical>
|
|
305
317
|
</step>
|
|
306
318
|
|
|
307
319
|
<step n="4" goal="Web research for latest technical specifics">
|