admin/dev_agent_team
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Phase 1-3: Add memory, skills, and improvement systems

Browse Source 
- memory/: cross-session project memory with decisions, lessons, failures,
  architecture, and sessions categories. Each has format templates and
  lifecycle documentation.
- skills/: 12 reusable specialized methodologies (tdd, systematic-debugging,
  architecture-design, code-review, security-review, repository-analysis,
  failure-analysis, refactoring, test-analysis, incident-investigation,
  browser-automation, research). Each has frontmatter and methodology sections.
- improvements/: proposal-based improvement system requiring human approval.
- scripts/memory-lifecycle.sh: deterministic memory operations (recall, store,
  list, search, sessions, cleanup).
- scripts/test-memory-system.sh: 12 structural tests for all new systems.
- orchestrator.md: added Memory Recall stage, Learning and Memory Storage
  stage, Improvement Proposals workflow, memory/skills rules, and 3 new
  actions (A23-A27) to the action catalog. Updated behavioral acceptance test
  and state separation model.
- All 12 subagents: added Memory & Skills Awareness sections with recall
  and store instructions.
- docs/AGENT_ARCHITECTURE.md: documented memory, skills, and improvements
  systems (sections 12-14). Updated action count (27), state model, and
  remaining weaknesses.
- README.md: documented new systems, updated repository layout, added
  test-memory-system.sh documentation.

All 39 tests pass (16 architecture + 12 memory + 11 bootstrap).
This commit is contained in:
Your Name
2026-09-08 04:31:40 -04:00
parent fb9d91e510
commit 2dabf8ef03
38 changed files with 2247 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files
agents/workflow-architect.md
+14
View File
@@ -73,6 +73,20 @@ Your primary evidence is the model itself: states, transitions, and the requirem
Stop when the model is complete, validated against the requirements, and the specification contains no unresolved ambiguity; escalate when requirements are too vague to model safely.
## Memory & Skills Awareness
Before modeling, check project memory for relevant context:
- `scripts/memory-lifecycle.sh recall decisions <keywords>` — for past workflow decisions
- `scripts/memory-lifecycle.sh recall lessons <keywords>` — for proven modeling approaches
- `scripts/memory-lifecycle.sh recall failures <keywords>` — for past workflow mistakes
After completing workflow model, store durable findings:
- Workflow decision made → `scripts/memory-lifecycle.sh store decisions <file>`
- Modeling lesson learned → `scripts/memory-lifecycle.sh store lessons <file>`
Load relevant skills when your brief includes a skill path.
Do NOT re-derive modeling patterns already documented in memory or skills.
## Core Behavior
Your core behavior is: