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:
parent
c3cf0c1fc6
commit
54ab3f13d3
|
|
@ -78,3 +78,6 @@ bmad-custom-src/
|
||||||
# Docusaurus / Documentation Build
|
# Docusaurus / Documentation Build
|
||||||
.docusaurus/
|
.docusaurus/
|
||||||
build/
|
build/
|
||||||
|
|
||||||
|
# Fork-specific documentation (not committed)
|
||||||
|
BUG-TRACKING.md
|
||||||
|
|
|
||||||
|
|
@ -146,7 +146,13 @@ Change context: {description}
|
||||||
|
|
||||||
Documentation notes: {doc_impact.notes}
|
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>
|
</invoke-agent>
|
||||||
</check>
|
</check>
|
||||||
|
|
||||||
|
|
@ -163,7 +169,13 @@ Change context: {description}
|
||||||
|
|
||||||
Documentation notes: {doc_impact.notes}
|
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>
|
</invoke-agent>
|
||||||
</check>
|
</check>
|
||||||
|
|
||||||
|
|
@ -180,7 +192,13 @@ Change context: {description}
|
||||||
|
|
||||||
Documentation notes: {doc_impact.notes}
|
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>
|
</invoke-agent>
|
||||||
</check>
|
</check>
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue