Add follow-up issue guidance
This commit is contained in:
37
docs/agent-handoff.md
Normal file
37
docs/agent-handoff.md
Normal file
@@ -0,0 +1,37 @@
|
||||
# Agent Handoff
|
||||
|
||||
Use this file for current repository follow-ups when tracker issues cannot be created.
|
||||
|
||||
## Current State
|
||||
|
||||
The kit now includes guidance for creating focused tracker issues for actionable follow-up work.
|
||||
|
||||
## Changes Made
|
||||
|
||||
- Added issue creation guidance to the agent rules, quickstart, README, new/existing repository workflows, and manifest.
|
||||
- Added handoff guidance for cases where issue creation is unavailable or too sensitive.
|
||||
- Updated the kit version to `1.0.1`.
|
||||
|
||||
## Verification
|
||||
|
||||
| Check | Result |
|
||||
| --- | --- |
|
||||
| Issue creation test | Blocked: Gitea API returned `invalid username, password or token` |
|
||||
|
||||
## Open Questions
|
||||
|
||||
- Whether the local `GITEA_TOKEN` should be refreshed for future issue/release automation.
|
||||
|
||||
## Next Steps
|
||||
|
||||
- Create a focused tracker issue for adding a reusable follow-up issue template once issue API access is available.
|
||||
|
||||
## Follow-up Issues
|
||||
|
||||
| Issue | Status |
|
||||
| --- | --- |
|
||||
| Add reusable issue template for agent follow-ups | Pending issue tracker access |
|
||||
|
||||
## Risks
|
||||
|
||||
- Issue automation cannot be fully validated until a valid token is available.
|
||||
Reference in New Issue
Block a user