source-command-opsx-explore

Explore codebase architecture and requirements with ASCII diagrams and OpenSpec artifacts.

9|1|Updated May 13, 2026
One-click install
npx skills add https://github.com/susomejias/rembric --skill source-command-opsx-explore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-command-opsx-explore
Source: https://github.com/susomejias/rembric/tree/main/.agents/skills/source-command-opsx-explore
Command: npx skills add https://github.com/susomejias/rembric --skill source-command-opsx-explore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a dedicated, unstructured space to think through vague ideas, investigate complex problems, and clarify project requirements without the pressure of immediate implementation, eliminating the friction of switching between brainstorming and coding workflows.

Core Features & Use Cases

  • Non-Prescriptive Thinking Partner: Follows your lead, asks open-ended questions, and explores multiple directions instead of following a rigid script.
  • Codebase-Grounded Exploration: Investigates actual project code, maps existing architecture, and surfaces hidden complexity to keep discussions rooted in reality.
  • Visual & Structured Output: Uses ASCII diagrams to clarify complex concepts, and can capture crystallized insights as OpenSpec artifacts (proposals, designs, specs) when you're ready to formalize work.
  • Use Case: For example, if you're unsure whether to add a new feature to the existing authentication system or build a separate service, you can use this Skill to brainstorm tradeoffs, map current auth architecture in the codebase, and visualize the options before making a decision.

Quick Start

Use the source-command-opsx-explore skill to think through your idea for adding real-time collaboration to the project and clarify the requirements before creating a change proposal.

Frequently Asked Questions about source-command-opsx-explore

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

FAQPage Schema
How do I brainstorm new feature ideas without immediately writing code?

To brainstorm new feature ideas without writing code, you need a pressure-free exploration space that investigates your actual codebase architecture and visualizes tradeoffs via ASCII diagrams before any implementation begins. This approach keeps discussions grounded in reality without forcing premature coding steps.

What is the best way to clarify ambiguous project requirements before development?

Clarifying ambiguous project requirements involves exploring the problem space with open-ended questions, mapping existing codebase architecture, and crystallizing insights into structured artifacts like OpenSpec proposals to formalize the work before development starts.

Can I compare technical tradeoffs for adding a new feature to an existing system versus building a separate service?

Yes, you can compare technical tradeoffs by analyzing your current codebase architecture, mapping the existing dependencies, and using visual diagrams to evaluate the complexity of extending the current system versus creating a standalone service before making a decision.

How do I investigate codebase architecture to surface hidden complexity?

Investigating codebase architecture to surface hidden complexity requires grounding the exploration in actual project code to map existing structures, identify dependencies, and visually clarify the components using ASCII diagrams to reveal underlying issues.

When should I formalize brainstorming insights into OpenSpec artifacts?

You should formalize brainstorming insights into OpenSpec artifacts like proposals, designs, or specs only when your ideas are crystallized and you are ready to transition from unstructured requirement clarification to structured implementation planning.