chore: Add fork docs gitignore and improve implement workflow

- Add BUG-TRACKING.md to gitignore for fork-specific documentation
- Improve implement workflow doc update tasks with return instructions
  - PRD, architecture, and UX update tasks now remind to return to /implement
  - Ensures implementation proceeds after doc updates complete

🤖 Generated with [Claude Code](https://claude.ai/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Darren Podolak 2025-12-30 09:44:03 -05:00
parent c3cf0c1fc6
commit 54ab3f13d3
2 changed files with 24 additions and 3 deletions

3
.gitignore vendored
View File

@ -78,3 +78,6 @@ bmad-custom-src/
# Docusaurus / Documentation Build
.docusaurus/
build/
# Fork-specific documentation (not committed)
BUG-TRACKING.md

View File

@ -146,7 +146,13 @@ Change context: {description}
Documentation notes: {doc_impact.notes}
Please update the relevant PRD sections to reflect this change. After updates, summarize what was changed.</task>
Please update the relevant PRD sections to reflect this change.
After updates:
1. Summarize what was changed
2. Return to the implement workflow by running: /implement {item_id}
IMPORTANT: You MUST return to /implement {item_id} after completing the PRD updates so the actual code implementation can proceed.</task>
</invoke-agent>
</check>
@ -163,7 +169,13 @@ Change context: {description}
Documentation notes: {doc_impact.notes}
Please update the relevant architecture sections (data model, APIs, security, etc.) to reflect this change. After updates, summarize what was changed.</task>
Please update the relevant architecture sections (data model, APIs, security, etc.) to reflect this change.
After updates:
1. Summarize what was changed
2. Return to the implement workflow by running: /implement {item_id}
IMPORTANT: You MUST return to /implement {item_id} after completing the architecture updates so the actual code implementation can proceed.</task>
</invoke-agent>
</check>
@ -180,7 +192,13 @@ Change context: {description}
Documentation notes: {doc_impact.notes}
Please update the relevant UX spec sections (screens, flows, components, etc.) to reflect this change. After updates, summarize what was changed.</task>
Please update the relevant UX spec sections (screens, flows, components, etc.) to reflect this change.
After updates:
1. Summarize what was changed
2. Return to the implement workflow by running: /implement {item_id}
IMPORTANT: You MUST return to /implement {item_id} after completing the UX updates so the actual code implementation can proceed.</task>
</invoke-agent>
</check>