Add a structured learnings tool and data model #4
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Add a focused AMCS learnings capability for storing structured development learnings as first-class records instead of burying them inside generic thoughts or markdown notes.
Why
This is still a useful product feature even though AMCS already has thoughts, skills, guardrails, and tool annotations. A learnings model would cover a different use case: durable, queryable lessons and corrections that can later be reviewed, resolved, or promoted into reusable guidance.
Important scope note
Keep v1 narrow. This issue should not try to solve every future promotion or workflow-automation use case in one shot.
Recommended v1 scope
Add a structured learnings record with:
Add a tool surface for:
Suggested v1 enums
Category
correctioninsightknowledge_gapbest_practiceArea
frontendbackendinfratestsdocsconfigotherStatus
pendingin_progressresolvedwont_fixpromotedpromoted_to_skillOut of scope for v1
Acceptance criteria
Rationale
This keeps #4 as real product work instead of a giant “build a knowledge-management universe” ticket. Future promotion/reporting workflows can be added in follow-up issues.
Add AMCS learnings tool with structured DB-backed recordsto Add a structured learnings tool and data model