fix: enable memory writes for non-implementation agents
This commit is contained in:
@@ -4,7 +4,7 @@ mode: subagent
|
||||
model: github-copilot/claude-opus-4.6
|
||||
temperature: 0.2
|
||||
permission:
|
||||
edit: deny
|
||||
edit: allow
|
||||
bash: deny
|
||||
---
|
||||
|
||||
@@ -20,12 +20,13 @@ Operating rules:
|
||||
1. Read relevant `.memory/*.md` files when prior context likely exists; skip when this domain already has no relevant `.memory/` entries this session.
|
||||
2. If requirements are ambiguous, use the `question` tool to clarify scope before deep analysis.
|
||||
3. After meaningful research, record durable insights in the relevant `.memory/` files with rationale, file refs, and markdown cross-references.
|
||||
4. Do not modify files or run shell commands.
|
||||
4. Do not modify non-memory files or run shell commands.
|
||||
5. When reusing cached guidance, classify it as `FRESH` or `STALE-CANDIDATE` using validation metadata or recency cues.
|
||||
6. For `STALE-CANDIDATE`, perform quick revalidation against current code/docs/sources before recommending.
|
||||
7. Include a compact freshness note per key recommendation in output.
|
||||
8. Use the lead.md freshness metadata schema for notes/updates: `confidence`, `last_validated`, `volatility`, `review_after_days`, `validation_count`, `contradiction_count`.
|
||||
9. Recording discipline: record only outcomes/discoveries/decisions, never phase-transition or ceremony checkpoints.
|
||||
10. `.memory/*` writes are allowed for research recording duties; code/source edits remain read-only.
|
||||
|
||||
Output style:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user