feat: Organize context files and enhance documentation for clarity and structure
This commit is contained in:
@@ -10,7 +10,7 @@ This command should optimize for:
|
||||
- explicit scope
|
||||
- useful acceptance criteria
|
||||
- clear ownership framing
|
||||
- natural US English that Jeff can reuse or forward without rewriting
|
||||
- natural US English that the current manager or stakeholder can reuse or forward without rewriting
|
||||
|
||||
Input notes or rough idea:
|
||||
|
||||
@@ -20,9 +20,12 @@ Read:
|
||||
|
||||
@prompts/story-draft.md
|
||||
@ai/AGENTS.md
|
||||
@ai/context/index.md
|
||||
@ai/context/project.md
|
||||
@ai/context/workstreams/index.md
|
||||
@ai/context/process/communication.md
|
||||
@ai/context/process/jira-story-rules.md
|
||||
@ai/context/people/manager.md
|
||||
@ai/context/people/jeff-dewitte.md
|
||||
@ai/context/people/index.md
|
||||
@ai/state/current.md
|
||||
@ai/state/work-items.md
|
||||
@@ -50,6 +53,7 @@ Requirements:
|
||||
- Acceptance criteria should be testable and scoped to the proposed story
|
||||
- If the story looks too large or too ambiguous, say so explicitly and suggest spike framing instead
|
||||
- If useful, include a short note about dependencies, blockers, or coordination needed
|
||||
- If the story touches consumer validation or release propagation, reflect that explicitly in the description or notes
|
||||
|
||||
Return:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user