43 lines
1.2 KiB
Markdown
43 lines
1.2 KiB
Markdown
# Behavior Check Template
|
|
|
|
Use this template when a change to `AGENTS.md`, `agent-docs`, or the `agent-docs` skill suite requires representative prompt checks.
|
|
|
|
## Per Prompt Record
|
|
|
|
```md
|
|
### Prompt <n>
|
|
|
|
Prompt:
|
|
- <representative user phrasing>
|
|
|
|
Expected Route:
|
|
- <root entrypoint>
|
|
- <specialized skill or child doc that should follow>
|
|
- <required follow-up checks if any>
|
|
|
|
Observed Route:
|
|
- <what the agent actually read, chose, or skipped>
|
|
|
|
Result:
|
|
- <pass / fail>
|
|
|
|
Failure Reason:
|
|
- <omit if pass; otherwise explain the mismatch such as skipped root entrypoint, missed follow-up check, or guessed through ambiguity>
|
|
```
|
|
|
|
## Summary
|
|
|
|
```md
|
|
- behavior check outcome: <pass / fail / incomplete>
|
|
- prompts tested: <count>
|
|
- failing condition hit: <yes / no>
|
|
- notes: <anything the static checks still cannot prove>
|
|
```
|
|
|
|
## Pass Criteria
|
|
|
|
- The agent reads the root entrypoint before choosing a specialized workflow when required.
|
|
- The agent follows the intended route instead of picking an equally plausible but wrong skill or doc.
|
|
- The agent performs required follow-up checks after refactor-oriented changes.
|
|
- The agent surfaces ambiguity instead of guessing through duplicate authority or overlapping scope.
|