Compare commits

...

8 Commits

Author SHA1 Message Date
Can Tecim 5b75e53859
Merge f70a9e0569 into 3d824d4c0f 2026-04-24 12:09:23 -04:00
Can Tecim f70a9e0569
Merge branch 'main' into patch-1 2026-04-19 19:54:13 +03:00
Can Tecim 9794507384
fix: update allowed modifications 2026-04-19 22:07:27 +07:00
Can Tecim 18c6fb6b7c
Merge branch 'main' into patch-1 2026-04-19 17:54:02 +03:00
Can Tecim 84bf1b7bba
refactor: allow 'Marking Review Follow-ups'
Updated instructions to include 'Marking Review Follow-ups' in the modification areas.
2026-04-19 21:53:23 +07:00
Can Tecim e67672ae38
refactor: update dev-story workflow instructions 2026-04-19 21:49:23 +07:00
Can Tecim 02a8c203c6
refactor: fix findings section in step-04-present.md
Updated the instructions for writing findings in the story file to specify a new subsection for follow-ups.
2026-04-19 21:48:20 +07:00
Can Tecim c90bdce306
refactor: allow dev-story skill to modify Review Findings todo items 2026-04-03 04:48:01 +07:00
2 changed files with 4 additions and 4 deletions

View File

@ -18,7 +18,7 @@ If zero findings remain after triage (all dismissed or none raised): state that
### 2. Write findings to the story file
If `{spec_file}` exists and contains a Tasks/Subtasks section, append a `### Review Findings` subsection. Write all findings in this order:
If `{spec_file}` exists and contains a Tasks/Subtasks section, append a `### Review Follow-ups (AI)` subsection if not exists already. Append all findings in this order:
1. **`decision-needed`** findings (unchecked):
`- [ ] [Review][Decision] <Title> — <Detail>`

View File

@ -5,10 +5,10 @@
**Your Role:** Developer implementing the story.
- Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}
- Generate all documents in {document_output_language}
- Only modify the story file in these areas: Tasks/Subtasks checkboxes, Dev Agent Record (Debug Log, Completion Notes), File List, Change Log, and Status
- Only modify the story file in these areas: Tasks/Subtasks checkboxes (including Review Follow-ups (AI)), Dev Agent Record (Debug Log, Completion Notes), File List, Change Log, and Status
- Execute ALL steps in exact order; do NOT skip steps
- Absolutely DO NOT stop because of "milestones", "significant progress", or "session boundaries". Continue in a single execution until the story is COMPLETE (all ACs satisfied and all tasks/subtasks checked) UNLESS a HALT condition is triggered or the USER gives other instruction.
- Do NOT schedule a "next session" or request review pauses unless a HALT condition applies. Only Step 6 decides completion.
- Do NOT schedule a "next session" or request review pauses unless a HALT condition applies. Only Step 8 decides completion.
- User skill level ({user_skill_level}) affects conversation style ONLY, not code updates.
---
@ -47,7 +47,7 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
<critical>Absolutely DO NOT stop because of "milestones", "significant progress", or "session boundaries". Continue in a single execution
until the story is COMPLETE (all ACs satisfied and all tasks/subtasks checked) UNLESS a HALT condition is triggered or the USER gives
other instruction.</critical>
<critical>Do NOT schedule a "next session" or request review pauses unless a HALT condition applies. Only Step 6 decides completion.</critical>
<critical>Do NOT schedule a "next session" or request review pauses unless a HALT condition applies. Only Step 8 decides completion.</critical>
<critical>User skill level ({user_skill_level}) affects conversation style ONLY, not code updates.</critical>
<step n="1" goal="Find next ready story and load it" tag="sprint-status">