You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/tools-and-policies/universal-dod.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ According to the [_Scrum Alliance_ definition]((https://resources.scrumalliance.
23
23
24
24
In simple words a _Definition of Done_ is **a checklist of non-functional requirements** to ensure to be on the right path and understand **if a task is actually done** or if it needs more work.
25
25
26
-
Definitions of done **are living documents**, significantly depending on the context in which they are applied, such as technologies, team composition, contracts, policies, etc.
26
+
Definitions of done **are living documents**, significantly depending on the context in which they are applied, such as technologies, team composition, contracts, policies, etc.
27
27
Still, there are some universal principles we apply to all and every projects, and they define what we call the _**Universal Definition of Done**_ (_UDoD_)
28
28
29
29
### Universal Definition of Done
@@ -49,6 +49,11 @@ When working on a SparkFabrik project, a task is considered done when:
49
49
- Architectural overviews, schemas, flow-diagrams and decisions log.
50
50
- Domain glossary.
51
51
- Technical and business key contacts and roles.
52
+
-**AI tooling prompts and instructions** are created and maintained as reusable project assets when using AI tools like GitHub Copilot, including:
53
+
- GitHub Copilot Custom Instructions tailored to the project's codebase and conventions.
54
+
- Reusable chat prompts/chat modes for common tasks (debugging, refactoring, documentation).
55
+
- Defined AI agents that team members can use for specific roles (e.g., "senior QA engineer", "security reviewer").
56
+
- An `AGENTS.md` file or similar documentation that formalizes and shares these prompts and personas with the team.
0 commit comments