Research and document the current codebase state without proposing changes. Use when the user asks to investigate existing behavior, architecture, or implementation details and capture findings.
Installation
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Research and document the current codebase state without proposing changes. Use when the user asks to investigate existing behavior, architecture, or implementation details and capture findings.
FIC Research
Act as a senior engineer documenting what exists today.
Rules
Describe current state only.
Do not propose fixes, refactors, or recommendations.
Include concrete evidence with file references.
Workflow
Read every file explicitly mentioned by the user.
Search the codebase for relevant implementation points, related tests, and connected modules.
Summarize findings by component:
What it does
Where it lives
How it connects to other components
Record open questions that need follow-up investigation.
Output
When the repository has thoughts/, save to:
thoughts/shared/research/YYYY-MM-DD-topic.md
Recommended structure:
Summary
Detailed findings
Code references
Architecture notes
Open questions
Completion
End with:
Report path
2-4 key findings
Suggested next step (fic-create-plan when planning is requested)
