BMAD-METHOD/scripts
Caleb 8a41477ae0 feat(epic-execute): bound design-phase context and persist plans
Design phase improvements #1 and #2:

#1 Bounded context:
- Pass architecture.md by path instead of embedding full contents
  (the main unbounded size risk in this prompt)
- Cap decision-log context at last 20KB (matches dev phase)
- Add log_prompt_size guard, consistent with other phases
- Replace hardcoded JS/TS exploration hints with language-agnostic guidance

#2 File persistence:
- Add DESIGN_DIR config and persist each plan to <DESIGN_DIR>/<story>-design.md
- build_design_context_for_dev falls back to the persisted file when the
  in-memory plan is empty, so resumed runs keep their design context

Story file remains inlined (small, bounded, needed in full by the planner).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-03 05:57:58 -05:00
..
epic-execute-lib feat(epic-execute): bound design-phase context and persist plans 2026-06-03 05:57:58 -05:00
epic-chain.sh feat(scripts): port memory-safe execution and reliability improvements from revive-dev 2026-04-12 11:52:39 -05:00
epic-execute.sh feat(epic-execute): bound design-phase context and persist plans 2026-06-03 05:57:58 -05:00
uat-validate.sh feat(scripts): port memory-safe execution and reliability improvements from revive-dev 2026-04-12 11:52:39 -05:00