aif-explore

Explore ideas, investigate problems, and clarify requirements before implementing software changes.

Updated May 16, 2026
One-click install
npx skills add https://github.com/vulikjulik/DeepLom --skill aif-explore-vulikjulik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-explore
Source: https://github.com/vulikjulik/DeepLom/tree/main/.opencode/skills/aif-explore
Command: npx skills add https://github.com/vulikjulik/DeepLom --skill aif-explore-vulikjulik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of costly rework from jumping into implementation without fully understanding the problem, exploring all options, or clarifying requirements. It acts as a dedicated thinking partner to help you work through ideas, investigate issues, and refine your plans before writing any code.

Core Features & Use Cases

  • Open-Ended Exploration: Work through vague ideas, specific problems, or existing plans with curious, non-prescriptive questioning instead of rigid scripts.
  • Codebase Grounding: Investigate your actual project code to map relevant architecture, find existing patterns, and surface hidden complexity instead of theorizing in a vacuum.
  • Visualization & Comparison: Use ASCII diagrams to sketch systems, state machines, and data flows, and compare different technical or design approaches with clear tradeoff analysis.
  • Use Case: For example, if you are considering adding real-time collaboration to your project, use this Skill to explore the collaboration spectrum, check if existing code supports it, and compare CRDT vs. operational transform approaches before committing to a plan.

Quick Start

Use the aif-explore skill to think through the idea of adding real-time collaboration to the project before you start planning the implementation.

Frequently Asked Questions about aif-explore

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

FAQPage Schema
How do I investigate a codebase to clarify vague feature requirements before implementation?

Exploring technology options involves comparing different approaches with clear tradeoff analysis. You can use ASCII concept visualization to sketch systems and data flows, helping you evaluate alternatives like CRDT versus operational transform before committing to a plan.

How do I explore software design ideas and compare technical approaches for my project?

Exploring technology options involves comparing different approaches with clear tradeoff analysis. You can use ASCII concept visualization to sketch systems and data flows, helping you evaluate alternatives like CRDT versus operational transform before committing to a plan.

What is the best way to refine an existing software plan and identify implementation risks?

Codebase investigation applies whenever you face vague feature proposals, complex problem investigation, or existing plan refinement. It works by mapping your project's relevant architecture and finding existing patterns to ground your software design decisions in reality.

When do I need codebase investigation for software design and problem solving?

Codebase investigation applies whenever you face vague feature proposals, complex problem investigation, or existing plan refinement. It works by mapping your project's relevant architecture and finding existing patterns to ground your software design decisions in reality.

Can I visualize system architecture and data flows without writing code first?

Exploration insights can be optionally persisted to project research artifacts. This allows you to save the results of your codebase investigation, risk identification, and technology comparison for future reference during the implementation phase.