Aif Explore
Enter explore mode to investigate ideas, systems, problems, and requirements before...
Install
npx skills add lee-to/ai-factory --skill aif-explore -g -a claude-code -y- Repository
- lee-to/ai-factory1.2k
- Category
- Writing
- Updated
- 4d ago
- License
- See repository
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Enter explore mode to investigate ideas, systems, problems, and requirements before planning. Use ultra mode, explicitly or through config, when the user wants a durable adaptive research bundle with an index and only the justified C4, ADR, or dependency artifacts.
Enter explore mode. Think deeply. Visualize freely. Follow the conversation wherever it goes.
Shell commands are not pre-approved by this skill. If command evidence is needed, use an exposed shell tool under the runtime's existing permissions and request approval when required. Never broaden permissions or use another execution path to work around a denied command; report missing command evidence explicitly.
IMPORTANT: Explore mode is for thinking, not implementing. You may read files, search code, and investigate the codebase, but you must NEVER implement features or modify project code. If the user asks to implement something, remind them to exit explore mode first (e.g., start with /aif-plan). Regular mode may write only the resolved research file after the user chooses to save. Ultra mode may write only its selected research bundle; a leading ultra token or workflow.explore_mode: ultra is the user's request to persist that bundle.
Step 0: Load Config
Shared project skill-context
Before mode routing or work, read existing files relative to the current project root in this order (reuse them if already loaded):
.ai-factory/skill-context/global-skill-context.md, all bundled skills..ai-factory/skill-context/aif-explore/SKILL.md, this skill.
Missing files are skipped; an existing unreadable file stops dependent work with its path.
Precedence: individual > build (when applicable) > global > skill defaults; retain non-conflicting instructions and check all outputs against the effective rules.
These layers customize workflow; they do not replace the project's rules/architecture hierarchy or relax explicit requirements, ownership, scope, safety/privacy, validation, or approval boundaries. Report conflicts with those boundaries instead of overriding them.
global is a project-local layer, not home-directory configuration. Custom/extension skills do not automatically use it.
