docs: migrate project memory governance
This commit is contained in:
1 parent
7b5d855b09
commit
e7aa58a203
37 files changed
+942
-34
No files matched your search
@@ -0,0 +1,13 @@
|
||||
# Reflection Index
|
||||
|
||||
Use this index for second-order workflow lessons.
|
||||
|
||||
| Date | Reflection | Trigger | Action | Detail |
|
||||
|---|---|---|---|---|
|
||||
| 2026-08-28 | Shared rolling planning files created repeated size pressure and forced semantic compression. | Root `task_plan.md` repeatedly approached or exceeded its fixed limit. | Replaced the legacy system with task-scoped records plus serialized canonical integration in `.project-docs/`. | [Migration task](../30-worklog/tasks/20260828-migrate-project-docs-6f1a9c2d.md) |
|
||||
|
||||
## When To Reflect
|
||||
|
||||
Create a reflection only when work reveals a reusable lesson: skipped gates, repeated mistakes, durable debugging patterns, ineffective plans, human corrections, or candidates for new scripts or skills.
|
||||
|
||||
Routine task completion belongs in `30-worklog/task-history.md`.
|
||||
@@ -0,0 +1,54 @@
|
||||
# Reflection: {short title}
|
||||
|
||||
## Trigger
|
||||
|
||||
What happened?
|
||||
|
||||
## Expected Behavior
|
||||
|
||||
What should the agent or workflow have done?
|
||||
|
||||
## Actual Behavior
|
||||
|
||||
What happened instead?
|
||||
|
||||
## Root Cause
|
||||
|
||||
Classify the cause:
|
||||
|
||||
- Missing trigger
|
||||
- Weak gate
|
||||
- Stale docs
|
||||
- Unclear ownership
|
||||
- Missing script
|
||||
- Human decision not promoted
|
||||
- Agent ignored context
|
||||
- Other:
|
||||
|
||||
## Evidence
|
||||
|
||||
- Commit:
|
||||
- Files:
|
||||
- Session/thread:
|
||||
- Command output:
|
||||
- Docs involved:
|
||||
|
||||
## Lesson
|
||||
|
||||
What should future agents learn?
|
||||
|
||||
## Action
|
||||
|
||||
Choose one:
|
||||
|
||||
- Update docs
|
||||
- Update gate
|
||||
- Create script
|
||||
- Create/update skill
|
||||
- Add check/eval
|
||||
- Ask human to decide
|
||||
- No action
|
||||
|
||||
## Promotion
|
||||
|
||||
Should this become a rule, ADR, architecture note, task-history entry, skill change, or script?
|
||||
@@ -0,0 +1,10 @@
|
||||
# Skill Candidates
|
||||
|
||||
Track repeated workflow lessons that may deserve a reusable skill, script, or stronger gate.
|
||||
|
||||
| Date | Candidate | Evidence | Proposed Action | Status |
|
||||
|---|---|---|---|---|
|
||||
|
||||
## Promotion Rule
|
||||
|
||||
If the same reflection pattern appears repeatedly or prevents a serious mistake, propose a skill update, new skill, script, or deterministic check.
|
||||
Reference in new issue
Block a user