Files
dev_agent_team/skills/SKILLS.md
T
Your Name 2dabf8ef03 Phase 1-3: Add memory, skills, and improvement systems
- 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).
2026-09-08 04:31:40 -04:00

96 lines
3.1 KiB
Markdown

# Skills System
## Purpose
Skills provide reusable, specialized capabilities that agents can load when needed.
Instead of duplicating instruction sets across every agent, skills centralize
domain-specific knowledge and procedures.
## Structure
```
skills/
├── SKILLS.md # This file — index and loading rules
├── tdd/ # Test-Driven Development
│ └── SKILL.md
├── systematic-debugging/ # Systematic debugging methodology
│ └── SKILL.md
├── architecture-design/ # Architecture decision process
│ └── SKILL.md
├── code-review/ # Code review checklist and process
│ └── SKILL.md
├── security-review/ # Security review methodology
│ └── SKILL.md
├── repository-analysis/ # Repository exploration methodology
│ └── SKILL.md
├── failure-analysis/ # Failure investigation methodology
│ └── SKILL.md
├── refactoring/ # Refactoring principles and patterns
│ └── SKILL.md
├── test-analysis/ # Test coverage and quality analysis
│ └── SKILL.md
├── incident-investigation/ # Incident response methodology
│ └── SKILL.md
├── browser-automation/ # Browser automation patterns
│ └── SKILL.md
└── research/ # Research methodology
└── SKILL.md
```
## Loading Rules
1. The Orchestrator identifies which skill(s) a task requires
2. The Orchestrator includes the skill path in the agent's dispatch brief
3. The agent reads the skill file before beginning work
4. The agent applies the skill's procedures to the task
## Skill Format
Each skill file contains:
```markdown
---
name: <skill-name>
description: <what this skill provides>
version: "1.0"
owner: <which agent maintains this skill>
prerequisites: <what must be true before using this skill>
---
# <Skill Name>
## When to use this skill
## Core methodology
## Step-by-step procedure
## Common pitfalls
## Evidence requirements
## Exit criteria
```
## Agent-Skill Mapping
| Agent | Primary Skills | Optional Skills |
|-------|---------------|-----------------|
| Explorer | repository-analysis, research | browser-automation |
| Detective | systematic-debugging, failure-analysis | incident-investigation |
| Architect | architecture-design | code-review, security-review |
| Builder | tdd, refactoring | code-review |
| Tester | tdd, test-analysis | failure-analysis |
| Reviewer | code-review, security-review | test-analysis, architecture-design |
| Maintainer | refactoring | code-review |
| Toolsmith | systematic-debugging | — |
| Designer | — | research, browser-automation |
| Philosopher | — | research |
| Writer | — | research |
| Workflow Architect | — | — |
## Customization
Skills can be extended per-project by adding project-specific sections.
When a skill is customized, add a note at the top:
```markdown
> Customized for <project> on YYYY-MM-DD. Original skill preserved in
> the agent team repository.
```