aif-explore

Identify problems, hypotheses, and design questions while reading project context files.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/afterwork/arra-aif --skill aif-explore-afterwork
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-explore
Source: https://github.com/afterwork/arra-aif/tree/main/.cursor/skills/aif-explore
Command: npx skills add https://github.com/afterwork/arra-aif --skill aif-explore-afterwork

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a patient thinking partner to help teams explore ideas, investigate problems, and clarify requirements without implementing changes.

Core Features & Use Cases

  • Exploration-focused reasoning: helps map problems, surface assumptions, and surface multiple directions during early ideation.
  • Codebase-grounded analysis: reads context from files and project rules to stay aligned with the real system while thinking aloud.
  • Documentation of decisions: captures insights, risks, and questions in a persistent, shareable format for later planning.

Quick Start

Enter explore mode to think deeply, visualize freely, and follow the conversation wherever it leads.

Frequently Asked Questions about aif-explore

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

FAQPage Schema
How do I explore architecture and map out codebase risks before making changes?

Codebase exploration maps architecture and surfaces risks by acting as a visual thinking partner that reads project context, articulates hypotheses, and documents design questions without implementing any code changes.

What is the best way to document architectural decisions and risk assessment findings?

Documenting architectural decisions and risk findings involves capturing insights and assumptions in a persistent, shareable format during exploration, ensuring project rules and guardrails are satisfied throughout the process.

Can I use an exploration partner to analyze a codebase without modifying the source files?

Codebase analysis can be performed without modifying source files, as the exploration process strictly reads mandatory project files and context to map problems while leaving the actual system untouched.

Does codebase exploration require specific project configuration files to function?

Codebase exploration requires mandatory configuration files such as .ai-factory/RESEARCH.md and project-specific constraints defined within the .ai-factory context to align reasoning with established guardrails.

When should I use an architecture exploration tool instead of directly implementing code changes?

Architecture exploration should be used during early ideation to surface multiple directions, clarify requirements, and assess risks, providing a documented foundation before any actual implementation begins.

Why does exploration mode read mandatory context files before analyzing codebase architecture?

Exploration mode reads mandatory context files to ground the visual thinking process in the real system, ensuring that articulated problems and hypotheses adhere to project guardrails and specific constraints.