chore: add AGENTS.md, tasks/todo.md, and tasks/lessons.md for workflow management
This commit is contained in:
15
tasks/lessons.md
Normal file
15
tasks/lessons.md
Normal file
@@ -0,0 +1,15 @@
|
||||
# Lessons
|
||||
|
||||
## 2026-05-12
|
||||
|
||||
- Trigger: the user corrected the execution workflow for non-trivial tasks and required persistent task tracking.
|
||||
- Rule: for any non-trivial task, create or update `tasks/todo.md` before substantive implementation, keep progress current, and do not mark done without review evidence.
|
||||
- Preventive action: check for `tasks/todo.md`, `tasks/lessons.md`, and repository guidance files before editing code; if the user corrects process expectations, record the rule immediately.
|
||||
|
||||
- Trigger: the user required corrections to be persisted for future sessions.
|
||||
- Rule: any user correction must be recorded in `tasks/lessons.md` as `trigger -> rule -> preventive action`.
|
||||
- Preventive action: after any correction, update lessons before closing the task and mention the recorded rule in the final verification summary.
|
||||
|
||||
- Trigger: the user clarified that this repository is meant to run in mainland China environments.
|
||||
- Rule: future code, build, deployment, and integration changes must consider mainland China network accessibility and should prefer China-friendly defaults where practical.
|
||||
- Preventive action: when adding dependencies, mirrors, external endpoints, or download flows, explicitly check whether the default path works reliably in mainland China and add configuration or fallback when needed.
|
||||
25
tasks/todo.md
Normal file
25
tasks/todo.md
Normal file
@@ -0,0 +1,25 @@
|
||||
# Task Plan
|
||||
|
||||
## Checklist
|
||||
|
||||
- [x] Clarify scope, repository boundaries, and validation requirements for a repository-level AGENTS.md.
|
||||
- [x] Verify that the plan covers the user-specified workflow rules, project structure, and risk points.
|
||||
- [x] Create a complete AGENTS.md that embeds the requested workflow orchestration rules and repo-specific guardrails.
|
||||
- [x] Verify the generated AGENTS.md against the current repository structure and required workflow sections.
|
||||
- [x] Update the Review section with the final result and verification evidence.
|
||||
|
||||
## Scope And Risks
|
||||
|
||||
- Scope: add a repository-root AGENTS.md that governs future modifications across the Go backend, Vue frontend, deployment assets, and embedded Python managed services.
|
||||
- Risk: omit a repository area or validation command and leave future work under-constrained.
|
||||
- Risk: copy the requested workflow rules without adapting them to this repo's actual layout and toolchain.
|
||||
- Risk: finish without writing persistent task evidence for plan, review, and lessons.
|
||||
|
||||
## Review
|
||||
|
||||
- Status: completed.
|
||||
- Result: added a repository-root `AGENTS.md` plus `tasks/todo.md` and `tasks/lessons.md` to enforce the requested workflow for future non-trivial tasks.
|
||||
- Verification:
|
||||
- confirmed `AGENTS.md` exists at the repository root;
|
||||
- read back `AGENTS.md` and verified it covers workflow orchestration, task management, repo structure, validation matrix, and definition of done;
|
||||
- matched required repository-specific references including `internal/webdevice/`, `managed/people_flow_project/`, `managed/store_dwell_alert/`, `tasks/todo.md`, and `tasks/lessons.md`.
|
||||
Reference in New Issue
Block a user