openlore-brainstorm

openlore: Brainstorm

When to use this skill

Trigger this skill when the user wants to explore or design a new feature before writing any code, with phrasings like:

• "I want to add feature X"
• "how should I approach this?"
• "let's brainstorm this story"
• explicit command /openlore-brainstorm

---

Step 1 — Detect mode

Capture $PROJECT_ROOT, $FEATURE_DESCRIPTION, and $FEATURE_SLUG (kebab-case, ≤ 5 words, e.g. payment-retry-flow).

Then probe the structural index by calling the openlore MCP tool orient with:

{
  "directory": "$PROJECT_ROOT",
  "task": "$FEATURE_DESCRIPTION",
  "limit": 7
}

Set $MODE based on the result:

Result	$MODE	Meaning
Returns functions with score > 0	brownfield	Existing indexed codebase
Returns "error": "no cache" or 0 functions	greenfield	No structural index yet

Inform the user:

• Brownfield: "I found existing code related to this feature. Using structural analysis to guide design."
• Greenfield: "No structural index found. Using Domain Sketch — structural analysis will be available after openlore analyze is run on the first implementation."

Load project antipatterns (both modes):

If .claude/antipatterns.md exists, read it and store as $ANTIPATTERNS. These will be used as a failure mode source in Step 5. If absent, $ANTIPATTERNS = none.

---

Steps 2–4 — Structural analysis (brownfield only)

Skip to Step 5 if $MODE = greenfield.

Step 2 — Architecture overview

Call the openlore MCP tool get_architecture_overview with {"directory": "$PROJECT_ROOT"}.

Note hub functions and cross-domain dependencies in $DOMAINS_AFFECTED.

Step 3 — Generate change proposal

Call the openlore MCP tool generate_change_proposal with:

{
  "directory": "$PROJECT_ROOT",
  "description": "$FEATURE_DESCRIPTION",
  "slug": "$FEATURE_SLUG"
}

This chains orient + search_specs + analyze_impact and writes openspec/changes/$FEATURE_SLUG/proposal.md.