Brainstorm
Resolve unclear feature behavior or approach and produce an approved spec. Use for genuine uncertainty; not small or precise changes.
Install
$ agentstack add skill-bnet47-codexicon-brainstorm ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-bnet47-codexicon-brainstorm) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Brainstorm
Announce: "I'm using brainstorm to resolve the feature choices before implementation."
1. Load relevant project context
Read the project identity and only the architecture, conventions, decisions, or prior specs relevant to the feature. If the repository is still an unconfigured template, route to $discover.
2. Resolve the problem
Ask one targeted question at a time and stop when you can state:
- the problem and affected person;
- verifiable success;
- constraints and non-goals;
- the smallest shippable slice;
- unresolved risks.
3. Compare approaches
Present two or three genuinely viable approaches with tradeoffs in behavior, complexity, reversibility, and verification. Recommend one and explain why. Ask for a choice only when the alternatives materially change the product or cost; otherwise proceed with the recommended reversible option and state the assumption.
4. Write the spec
After the direction is accepted, save agent_docs/briefs/[YYYY-MM-DD]-[feature-slug].md without overwriting an existing file:
# Spec: [Feature]
**Date:** [YYYY-MM-DD]
**Status:** Approved
## Problem
[Who is affected and what fails today.]
## Chosen solution
[User-visible behavior and the selected approach.]
## Acceptance criteria
- [ ] [Specific observable result.]
## Non-goals
- [Explicit exclusion.]
## Constraints and risks
- [Constraint, risk, or dependency.]
## First shippable slice
[Smallest complete proof of value.]
## Open questions
- [Unresolved question, or "None".]Self-check that every criterion is testable, no placeholder remains, and the first slice is complete rather than merely scaffolding.
Offer $write-plan when implementation is multi-step. Do not implement, commit, or push during brainstorming unless the user explicitly expands the request.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: bnet47
- Source: bnet47/codexicon
- License: MIT
- Homepage: https://bnet47.github.io/codexicon/repo-template-playbook.html
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.