domains / families / research / research-manager

research-manager

separate

Records research provenance as a post-task epilogue, scanning conversation history at the end of a coding or research session to extract decisions, experiments, dead ends, claims, heuristics, and pivots, and writing them into the ara/ directory with user-vs-AI provenance tags. Use as a session epilogue — never during execution — to maintain a faithful, auditable trace of how a research project actually evolved.

When to use

• post-task epilogue
• scanning conversation history
• extracting decisions, experiments, dead ends, claims, heuristics, and pivots
• writing to ara/ directory
• maintaining auditable trace of research evolution

When not to use

• during execution
• during a task
• reading or writing ara/ while working on the user's request
• contaminating the working context

Skill page

Source