Guide codebase exploration and problem framing with ASCII diagrams.
npx skills add https://github.com/0serna/dotfiles --skill openspec-explore-0serna
Please help me install this Agent Skill. Skill: openspec-explore Source: https://github.com/0serna/dotfiles/tree/main/dotfiles/agents/skills/openspec-explore Command: npx skills add https://github.com/0serna/dotfiles --skill openspec-explore-0serna
This skill provides a structured approach to thinking through ideas and clarifying requirements without making or writing code, acting as a thinking partner that helps users explore problems deeply while preserving safety.
At activation, begin by stating the current exploration goal and ask clarifying questions to frame the problem.
High-intent search queries and answers about installing and using this skill.
To explore codebase changes safely, use a thinking partner that guides problem framing and surfaces risks without implementing modifications. It helps you visualize system relationships and clarify requirements through structured exploration before committing to actual development.
The best way to visualize system architecture during early design is using ASCII diagrams and system maps. These visual tools explain component relationships and surface design questions, allowing you to explore multiple directions without prescribing a single path.
Yes, you can generate OpenSpec artifacts without modifying source code. The exploration process enforces non-implementation guardrails, ensuring it only produces documentation artifacts while strictly preventing any actual code changes.
You surface unanswered questions and risk surfaces by applying adaptive guidance that frames problems deeply. This approach identifies potential risks and explores design spaces systematically, acting as a curious guide rather than prescribing solutions.
Yes, this codebase exploration approach supports generating visual diagrams. It utilizes ASCII diagrams and system maps to explain ideas and relationships, helping you understand structural connections while thinking through potential changes.
You should not use a code-writing approach when you need to clarify requirements and frame problems safely. If your goal is deep exploration of design spaces and surfacing options without committing changes, a non-implementation thinking partner is the correct choice.
saffron-healthGenerate phased specification documents from code and documentation analysis.
hossam7amdyFacilitates team brainstorming and clarifies requirements by reading files and generating OpenSpec artifacts without code.
alfredxwOrchestrate multi-milestone project workflows across threads and subagents.
RangeyRoverRun static analysis across multiple languages and generate prioritized issue reports.
