ai-task-template.md
active
Edit Selected
# AI Task Template
Use this file when you want an AI model to execute work, not just discuss it.
## Non-Negotiable Task Description Format
When creating or updating a task description for Vikunja, use this exact format and do not stray from it:
1. Summary
- 2-4 lines max
2. What To Do
- short bullet list
3. Systems Affected
- short bullet list
4. Constraints
- short bullet list
5. Validation
- short bullet list
6. Acceptance Criteria
- short bullet list
7. References
- file paths, task ids, URLs
This format is mandatory for task descriptions. Do not replace it with long narrative sections, paragraph-heavy explanations, or oversized design-document formatting.
## How To Use
Copy the template below, fill in the fields that matter, and give the filled version to the model.
If a field is unknown, say so plainly.
If a field is irrelevant, remove it.
If a fact can be discovered directly from the repo or systems, the model should do that instead of asking unnecessary questions.
## Prompt Wrapper
Use a prompt in this shape:
```text
As per the AI Task Template, execute the following task. Ask only the minimum necessary questions if critical information is missing. Otherwise proceed end-to-end, implement the work, validate it, and document any important outcomes.
```
## Template
```text
# Task Title
<short clear task title>
## Summary
<2-4 lines max>
## What To Do
- <short bullet>
- <short bullet>
- <short bullet>
## Systems Affected
- <host, service, repo, workflow>
- <host, service, repo, workflow>
## Constraints
- <security limit>
- <change-management guardrail>
- <behavior that must be preserved>
## Validation
- <command or check>
- <command or check>
- <expected success condition>
## Acceptance Criteria
- <observable condition 1>
- <observable condition 2>
- <observable condition 3>
## References
- <file path>
- <task id>
- <URL>
## Completion Output
When finished, report:
- what changed
- validation performed
- unresolved risks or follow-up items
- exact files touched
```
## Model Behavior Rules
When given a filled template, the model should:
1. Determine whether any critical facts are missing.
2. Ask only the minimum blocking questions.
3. Prefer direct inspection over speculative questions.
4. Execute the task end-to-end when feasible.
5. Validate the outcome.
6. Confirm with the user that the result is acceptable before closing the task.
7. If accepted, document the change according to the repository documentation guidance.
8. If not accepted, continue working with the user until the result is correct.
9. Avoid recording or exposing secrets.
10. Use the mandatory Vikunja task description format exactly as defined above.
## Good Use Cases
- infrastructure changes
- documentation work
- automation work
- troubleshooting
- service migrations
- firewall changes
- storage changes
- access-control changes
## Notes
- This template is meant to be practical, not exhaustive.
- It should be lightweight enough for day-to-day homelab work.
- If a task is small, several sections can be brief.
---
**2026-03-18 22:29:24 UTC | Template Format Update**
Content modified