research_manager

Organizes research project directories, status transitions, and archival rules for a .kilo workspace.

5|1|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/WissingChen/my_code_config --skill research-manager-wissingchen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: research_manager
Source: https://github.com/WissingChen/my_code_config/tree/main/my_skills/research_manager
Command: npx skills add https://github.com/WissingChen/my_code_config --skill research-manager-wissingchen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Research projects accumulate scattered notes, proposals, and experiment records with no consistent structure, making it hard to know where a direction stands or where a new file belongs. This Skill defines a lightweight skeleton for a .kilo/ workspace so every research direction has a clear location, status, and lifecycle. ## Core Features & Use Cases - Four-directory layout: Manages proposal/, project/, archive/, and knowledge/ directories with two-digit NN-slug naming and date-prefixed archive folders. - Index and TODO layer: Maintains global.md as a pure index (≤60 lines) and TODO.md as the single source of project progress with a three-level tree (main line → phases → current approaches). - Lifecycle and archiving: Handles five outcomes (rejected, falsified, validated, superseded, abandoned), enforces REPORT.md deliverable rules, and generates dated status snapshots in .kilo/reports/. - Use Case: When a research idea passes evaluation and the user says GO, the Skill moves the direction from proposal/03-slug/ to project/03-slug/, updates the index, and later archives it as archive/2025-01-15-03-slug/ with a SUMMARY.md pointer when the direction closes. ## Quick Start Ask the assistant to initialize a .kilo research project skeleton with the standard directory layout and index files.

Frequently Asked Questions about research_manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I organize a research project directory structure?▼

Use a four-directory layout: proposal/ for directions under evaluation, project/ for active experiments, archive/ for closed directions, and knowledge/ for external notes. Name each direction with a two-digit NN-slug prefix that stays constant when the directory moves between states.

How do I track research progress across multiple directions?▼

Maintain a TODO.md file as the single source of progress with a three-level tree: a locked main research question, major phases from proposals, and current implementation approaches. Keep a global.md as a pure index of links under 60 lines, without goals or rules.

When should a research direction be archived?▼

Archive a direction when it reaches one of five outcomes: rejected before experiments, falsified by registered expectations, validated and promoted, superseded by a changed core question, or abandoned for non-scientific reasons. Archived folders use a YYYY-MM-DD-NN-slug date prefix.

Does this Skill run experiments or evaluate research ideas?▼

No. It only manages directories, naming, status transitions, and archiving. Experiment execution belongs to experiment_manager, and judging whether an idea is worth pursuing belongs to research_progress; this Skill stays strictly on the file lifecycle side.

What files are required when closing a research direction?▼

Directions that ran experiments must leave a self-contained REPORT.md with figures as the main deliverable, plus a short SUMMARY.md pointer in the archive folder. Directions rejected before experiments keep their experiment-plan.md review record instead and do not require a REPORT.md.