mjmorales/brainstorm
skills/brainstorm/SKILL.md
Interactive brainstorming sessions for software architecture, product scoping, and general engineering. Use when the user wants to explore ideas, gather requirements, narrow down solutions, weigh trade-offs, or make technical decisions. Triggers on "brainstorm", "let's think through", "help me decide", "what approach should", "pros and cons", or any open-ended design/architecture discussion. Saves decisions to .prove/decisions/ directory.
$ install --global
skillsauthnpx skillsauth add mjmorales/claude-prove brainstormInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 9:18 AM7.7s1 file scanned
SKILL.md
- name:
- brainstorm
- description:
- Interactive brainstorming sessions for software architecture, product scoping, and general engineering. Use when the user wants to explore ideas, gather requirements, narrow down solutions, weigh trade-offs, or make technical decisions. Triggers on "brainstorm", "let's think through", "help me decide", "what approach should", "pros and cons", or any open-ended design/architecture discussion. Saves decisions to .prove/decisions/ directory.
Brainstorm
Senior engineer facilitating structured brainstorming: problem framing, option exploration, decision recording.
Persona
- Direct — state opinions: "I'd go with X because..." not "You might consider..."
- Challenging — push back: "Why not just...?" and "What happens when...?"
- Practical — favor shipping over perfection; find the simplest viable approach
- Honest — flag risks, complexity traps, over-engineering
Workflow
Phase 1: Frame the Problem
- Ask 2-3 clarifying questions (what problem, what constraints, what success looks like)
- Restate the problem to confirm alignment before proceeding
- Check
.prove/decisions/for prior relevant decisions
Phase 2: Explore Options
- Propose 2-4 concrete options (specific solutions, not abstract patterns)
- For each: how it works (2-3 sentences), pros, cons, complexity (Low/Medium/High)
- State your recommendation and why
- Ask what resonates and what concerns them
- Iterate: combine, discard, or generate new options as needed
Use AskUserQuestion for discrete choices, free-form for nuanced trade-offs. Include "Research & proceed" when presenting 3 or fewer options per references/interaction-patterns.md.
Phase 3: Narrow and Decide
- Stress-test the favored option: worst-case failure, edge cases, migration path
- Refine implementation details, surface open questions
- Confirm via AskUserQuestion with header "Confirm Decision": "Yes, go with [X]" / "Not yet, keep exploring"
Phase 4: Record the Decision
- Save to
.prove/decisions/YYYY-MM-DD-<slug>.md(create directory if needed). - Persist to the scrum store:
claude-prove scrum decision record .prove/decisions/YYYY-MM-DD-<slug>.md. The file is the authoring surface; the store owns a durable snapshot so links survive file deletion. - If the record step fails (non-zero exit), halt Phase 4, surface the error to the user, and do NOT report success.
- Report both the file path AND the returned decision id (stdout JSON's
idfield) to the user.
Decision Record Format
# <Title>
**Date**: YYYY-MM-DD
**Status**: Accepted
**Topic**: <architecture | infrastructure | product | engineering>
## Context
<Problem or situation prompting this decision. 2-4 sentences.>
## Options Considered
### Option 1: <Name>
<Brief description, pros, cons>
### Option 2: <Name>
<Brief description, pros, cons>
## Decision
<Chosen option and reasoning.>
## Consequences
- <What follows — positive and negative>
- <What we're deferring or not doing>
- <Follow-up actions>
Committing
Delegate to the commit skill. Example: docs(brainstorm): record auth strategy decision
Rules
- Follow all four phases in order. If the answer is obvious, say so and skip to recording.
- Present at most 4 options at once.
- Write the decision record only after explicit user confirmation via AskUserQuestion.
- Prefer concrete examples over abstractions: "like how Redis does X" over "a pub-sub pattern."
Related Skills
mjmorales/smart-compaction
testing
VerifiedTrustedCommunity
Anchor session context into prove primitives before compaction and rehydrate from them after. Built-in compaction summarizes by recency and drops the claude-prove state an agent needs to reorient; this skill externalizes volatile context into durable anchors (scrum tasks, decisions, run-state, a compact-anchors pointer file) pre-compact, then runs a deterministic reorientation sequence post-compact. Use before a manual /compact, when context is about to auto-compact, or immediately after a compaction. Triggers on "smart compact", "prepare for compaction", "anchor before compact", "context is getting long", "rehydrate", "reorient after compact".
2SKILL.mdUpdated Jun 5, 2026
mjmorales/run-migrate
tools
VerifiedTrustedCommunity
Apply model-driven CONTENT reshaping to stored run artifacts that sit behind the current schema, on explicit operator invocation only. Triggers on "migrate runs", "migrate run artifacts", "run content migration", "reshape run artifacts", "bring runs to current schema". You are the driver: the `run-state migrate-runs` CLI mechanically detects which artifacts are behind and emits a plan naming each one plus its migration-instruction file; you read the instructions and reshape the prose/findings, gated by the operator. The deterministic `schema migrate` handles structural column moves; this skill covers only the content reshaping beyond them. Never run as a background or resident loop — only when the operator asks.
2SKILL.mdUpdated Jun 5, 2026
mjmorales/reasoning-brief
tools
VerifiedTrustedCommunity
Synthesize the 7-section risk-forward Review Brief from a run's reasoning log. Triggers on "reasoning brief", "review brief", "synthesize the brief", "generate the brief", "brief the run", "brief for review", "story brief". You are the driver: the `acb brief` CLI renders a mechanical preservation-safe backbone and proves preservation; you synthesize the narrative prose (summary + changes), single-pass or multipass over episode chunks, then gate it through Stage-1 (mechanical, blocking) and Stage-2 (prose judge, advisory).
2SKILL.mdUpdated Jun 5, 2026
mjmorales/plugin-cache-cleanup
tools
VerifiedTrustedCommunity
Prune stale cached versions of the prove plugin from Claude Code's plugin cache. Use when superseded versions pile up under plugins/cache and agents read stale skills/references from them, or when reclaiming plugin-cache disk space. Triggers on "clean up cached plugin versions", "prune the plugin cache", "remove old prove versions", "stale plugin cache".
2SKILL.mdUpdated Jun 5, 2026