feat: Update behavior rules and documentation for workspace maintenance and flow references
This commit is contained in:
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user