feat: Update behavior rules and documentation for workspace maintenance and flow references

This commit is contained in:
2026-04-16 07:50:07 -06:00
parent a375b3c3b1
commit 1f57597ca3
21 changed files with 146 additions and 15 deletions

View File

@@ -15,6 +15,7 @@ Read:
@ai/context/index.md
@ai/context/project.md
@ai/context/workstreams/index.md
@ai/context/workstreams/flow-page-references.md
@ai/context/process/communication.md
@ai/context/process/jira-story-rules.md
@ai/context/people/manager.md
@@ -49,6 +50,8 @@ Before drafting:
- prioritize story-based updates over side questions, memory refreshes, or manager-only context
- if documentation or root cause updates directly support a story, roll them into that story's update instead of listing them separately
- exclude items that are not directly tied to a story unless they are true blockers
- when one Jira item has multiple concrete updates, group them under one top-level `JIRA-ID - Title` bullet with indented markdown sub-bullets instead of repeating the same Jira line
- use `ai/context/workstreams/flow-page-references.md` to preserve real flow/page identifiers when shorthand appears in logs or messages
Return a standup that is:
@@ -61,4 +64,5 @@ Return a standup that is:
- free of any mention of Jeff by name
- free of any mention of Mattermost, since it is internal-only communication
- uses bullet points for each item
- groups multiple updates for the same Jira item as indented sub-bullets
- uses `JIRA-ID - Title` or `JIRA-ID Title` formatting instead of comma-separated ID/title formatting