simple-brainstorm
77Brainstorm Focused Design Decisions
Teams lose time when creative or architecture choices are unclear. This skill guides a short process to compare options, choose a direction, and capture approval.
Plan Focused Brainstorming Sessions
Fast design discussions can lose focus or skip key trade-offs. This skill guides Claude, Codex, or Claude Code through a concise brainstorming flow before implementation.
Do not auto-install this skill.
The canonical policy requires operator review before any installation action.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "simple" from https://skillstore.io/skills/roin-orca-simple.md and its manifest at https://skillstore.io/api/skills/roin-orca-simple/manifest. Verify the artifact. Do not auto-install. Inspect the skill and report your findings, then wait for an operator or manual installation decision.Your Agent should still show its plan and request any confirmation required by the security policy.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "simple". I need to add saved filters to a dashboard.
Expected outcome:
The assistant asks focused questions, compares local storage with server-backed filters, and recommends the best path for the current product scope.
Using "simple". We may replace a shared data-fetching helper.
Expected outcome:
The assistant summarizes current constraints, presents two migration options, explains trade-offs, and waits for approval before editing files.
Using "simple". I want a cleaner settings page layout.
Expected outcome:
The assistant reviews existing patterns, proposes two layout directions, and captures the selected plan before implementation starts.
The static external command finding is a false positive because SKILL.md lines 19-32 are a Markdown dot diagram. I found a critical prompt injection attempt in the skill description and a high-risk Markdown attribute injection payload. The author should remove both malicious instructions and unsafe image markup before publication.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/roin-orca-simple/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/roin-orca-simple?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/roin-orca-simple?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/roin-orca-simple/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/roin-orca-simple.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>roin-orca. (2026). simple security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/roin-orca-simple/audits/4@techreport{roin-orca-roin-orca-simple-2026,
author = {roin-orca},
title = {simple security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/roin-orca-simple/audits/4},
note = {Author version unspecified}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "simple security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "roin-orca"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/roin-orca-simple/audits/4"
identifiers:
- type: other
value: "skillstore:roin-orca-simple:audit:4"
description: "Skillstore immutable audit report identifier"
Use the skill to clarify intent, compare options, and select a practical path before coding.
Use the flow to compare two designs and explain the trade-offs before changing shared systems.
Use the process to align behavior, constraints, and implementation scope before editing UI components.
Use the simple brainstorming skill for this change. Help me clarify the goal, compare two options, and choose a direction.
Use the simple brainstorming process to propose two implementation approaches. Include trade-offs, risks, and your recommended direction.
Use this skill to assess the existing component patterns, ask any needed questions, and recommend a focused update plan.
Use the simple brainstorming workflow for this architecture change. Consider constraints, migration cost, reversibility, and expected impact.
Author
roin-orcaLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
e397ce5a135369cd6def89cb6400d013e2f68f2f
Maintenance freshness
7/18/2026
Usage
16 downloads ยท 103 views
File structure
๐ SKILL.md
Brainstorm Focused Design Decisions
Teams lose time when creative or architecture choices are unclear. This skill guides a short process to compare options, choose a direction, and capture approval.
Guide Fast Brainstorming Sessions
Creative and architectural decisions can stall when options are unclear. This skill gives Claude, Codex, and Claude Code a focused process for exploring options and choosing a direction.
Compare Options With Decision Frameworks
by shubhamsaboo
Complex choices are hard when trade-offs are unclear. This skill guides Claude, Codex, and Claude Code through structured option scoring and practical recommendations.
Plan Creative Work Before Building
by ZhanlinCui
Teams often start implementation before goals, constraints, and trade-offs are clear. This skill guides Claude, Codex, and Claude Code through structured brainstorming before design work begins.
Diagnose Product Decisions in Chinese
by atdy
Product teams often mistake symptoms for root causes and spread resources across weak priorities. This skill identifies the main blocker and recommends measurable next actions.
Organize Long AI Tasks with Planning Files
by ZhanlinCui
Long AI sessions can lose goals, decisions, and progress. This skill guides Claude, Codex, and Claude Code to store plans, findings, and logs in project files.
Guide CTO Engineering Decisions
by davila7
Engineering leaders need clear frameworks for architecture, metrics, hiring, and technical debt. This skill turns CTO planning questions into structured assessments, templates, and practical next steps.
Track Feature Requirements in YAML
by Chemiseblanc
Teams lose project intent when requirements live only in chat or task lists. This skill keeps scope, tests, decisions, and progress in a persistent features.yml file.