feat: add comprehensive agent rules and workflows for memory curation, communication synchronization, and project documentation management
This commit is contained in:
57
.agents/workflows/archive-import.md
Normal file
57
.agents/workflows/archive-import.md
Normal file
@@ -0,0 +1,57 @@
|
||||
---
|
||||
description: Import a historical communication archive and refine workspace memory
|
||||
---
|
||||
|
||||
Use a historical communication export as archive evidence for the workspace.
|
||||
|
||||
Interpret this as historical recovery, not as current truth and not as model training.
|
||||
|
||||
Inputs:
|
||||
|
||||
- `$ARGUMENTS` may contain an export path, channel names, or date filters
|
||||
- if no explicit path is given, use `AIW_SLACK_EXPORT_PATH` when available
|
||||
- Fidelity profile alias: `FIDELITY_SLACK_EXPORT_PATH`
|
||||
- otherwise, if `archives/slack/export/` exists, use it as the default import source
|
||||
- if no channels are specified, auto-detect channels using `AIW_CHANNEL_PREFIX`
|
||||
- Fidelity default prefix: `fidelity`
|
||||
|
||||
Run the importer:
|
||||
|
||||
!`prefix="${AIW_CHANNEL_PREFIX:-fidelity}"; if [ -n "$ARGUMENTS" ]; then python3 scripts/slack/import_slack_export.py $ARGUMENTS; elif [ -n "$AIW_SLACK_EXPORT_PATH" ]; then python3 scripts/slack/import_slack_export.py --export-path "$AIW_SLACK_EXPORT_PATH" --channel-prefix "$prefix"; elif [ -n "$FIDELITY_SLACK_EXPORT_PATH" ]; then python3 scripts/slack/import_slack_export.py --export-path "$FIDELITY_SLACK_EXPORT_PATH" --channel-prefix "$prefix"; elif [ -d archives/slack/export ]; then python3 scripts/slack/import_slack_export.py --export-path archives/slack/export --channel-prefix "$prefix"; else echo "Provide archive import arguments, set AIW_SLACK_EXPORT_PATH, set FIDELITY_SLACK_EXPORT_PATH, or place an extracted export in archives/slack/export."; fi`
|
||||
|
||||
Read:
|
||||
|
||||
@core/README.md
|
||||
@core/memory/operational-memory.md
|
||||
@core/integrations/communication-model.md
|
||||
@project-knowledge/01-current/current-work.md
|
||||
@project-knowledge/01-current/work-items.md
|
||||
@project-knowledge/03-context/project.md
|
||||
@agent-memory/memory/context-maintenance.md
|
||||
@project-knowledge/04-people/index.md
|
||||
@project-knowledge/04-people/manager.md
|
||||
|
||||
Imported summary, if present:
|
||||
|
||||
!`if [ -s scripts/slack/generated/slack_summary.md ]; then cat scripts/slack/generated/slack_summary.md; else echo "No archive summary generated."; fi`
|
||||
|
||||
Imported archive context, if present:
|
||||
|
||||
!`if [ -s scripts/slack/generated/slack_context.jsonl ]; then cat scripts/slack/generated/slack_context.jsonl; else echo "No archive context generated."; fi`
|
||||
|
||||
Instructions:
|
||||
|
||||
- treat the archive as historical evidence
|
||||
- promote durable project-relevant context automatically when confidence is high
|
||||
- prefer durable role/person associations, recurring architecture patterns, repeated work-item references, approval/scope history, and process lessons
|
||||
- create or update `project-knowledge/04-people/*.md` when a human repeatedly affects project flow
|
||||
- avoid promoting outdated daily status unless it changes current understanding
|
||||
- update existing memory when the archive clarifies or corrects it
|
||||
- keep ambiguous or likely outdated facts as archive-only context
|
||||
- write promoted memory to `project-knowledge/`
|
||||
|
||||
Return:
|
||||
|
||||
1. What was imported
|
||||
2. Which files were updated
|
||||
3. Which historical facts were promoted or intentionally left as archive-only context
|
||||
Reference in New Issue
Block a user