brainstorming
Explore the solution space before committing to an approach. Use when the user has a rough idea, when multiple valid approaches exist, or in early-stage feature design before coding.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-11
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- brainstorming
- description
- Explore the solution space before committing to an approach. Use when the user has a rough idea, when multiple valid approaches exist, or in early-stage feature design before coding.
02 资源文件 8
- 参考文档agents/distillate-compressor.md4.8 KB
- 参考文档agents/round-trip-reconstructor.md2.7 KB
- 参考文档reference/question-frameworks.md531 B
- 参考文档resources/compression-rules.md2.6 KB
- 参考文档resources/distillate-format-reference.md11.6 KB
- 参考文档resources/splitting-strategy.md3.3 KB
- 脚本scripts/analyze_sources.py9.7 KB
- 脚本scripts/tests/test_analyze_sources.py7.5 KB
03 SKILL.md 正文
Brainstorming
Transform a vague idea into a concrete design through structured dialogue. Work the phases in order; finish when you have produced the design doc at the end.
Phase 1: Understand the seed
Ask clarifying questions until you can answer:
- Goal: What problem are we solving?
- Context: What exists today?
- Constraints: What limits apply?
- Success: How will we know it works?
Question catalog by domain (features / architecture / UX): reference/question-frameworks.md.
Phase 2: Generate options
Present 2–4 distinct approaches (more than 4 is analysis paralysis):
## Option A: [Name]
- Approach: [Brief description]
- Pros: [Benefits]
- Cons: [Drawbacks]
- Effort: [Relative complexity]
Phase 3: Explore trade-offs
For each option, weigh: technical implications, maintenance burden, future flexibility, team familiarity. Make every assumption explicit.
Phase 4: Converge
Recommend one option with rationale, list the open questions per path, and propose the next concrete step. Emit the design doc:
# Design: [Feature Name]
## Summary
[1-2 sentence description]
## Chosen Approach
[Selected option with rationale]
## Key Decisions
- Decision 1: [Choice] because [reason]
## Open Questions
- [ ] Question 1
## Next Steps
1. [First concrete action]
Next
- Feed the design doc into the
create-planskill. - Persist decisions under
thoughts/shared/.
04 同仓库更多 Skills
writing-standards
Apply AS v2 technical-writing standards (clarity, brevity, active voice, Python/Django conventions). Use when writing a README, a docstring (PEP 257), a commit message, a PR description, an error message, or any technical doc.
verification-gate
Verify before claiming success. Use when about to say something works/is done, after implementing a feature, after a bugfix, or before pushing — run the proof command and confirm output first.
test-driven-development
Write the failing test before the implementation in AS v2 (pytest + Django/DRF). Use when implementing a feature or fixing a bug, before any production code is written.
subagent-development
Orquestra subagents no AS v2 — decompõe a tarefa em domínios independentes, paraleliza e revisa em 2 estágios. Use ao delegar exploração, implementação ou validação cross-arquivo para acelerar o trabalho e poupar o contexto principal.
security-scan
Automated security scanning for AS v2. Use before commits or when reviewing changes for vulnerabilities. Runs dependency audit (pip-audit, npm audit), secret detection (grep patterns), and code pattern scanning (SQL injection, XSS, eval, pickle, hardcoded secrets). Integrates with project hooks system.
resume-handoff
Resume work from a saved handoff document, validating its state against the current codebase before continuing. Use when resuming work from a saved handoff after a context clear or in a new session (path, session name, or GitHub issue).