Individual skill
brainstorming
Use before implementing a feature, a change in behavior, or a bug fix — however small. Not for questions, checks, or edits that change no behavior (typos, documentation or configuration only, mechanical refactors).
packages/pi-thinkrail-workflow/skills/brainstorming/SKILL.md
Source commit 519286befe0f15cc2dd270e251ecd8cdb9d0a01c
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 8,049
- Repository last updated
- Nov 8, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent Repository topic
- agent-skills Repository topic
- agentic-ai Repository topic
- agentic-workflow Repository topic
- ai-coding Repository topic
- ai-tools Repository topic
- spec-driven Repository topic
- spec-driven-coding Repository topic
- spec-driven-development Repository topic
- vibe-coding Repository topic
- docs Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,689 bytesSKILL.mdcore · 4,689 bytesamending-specs.mddoc · 2,086 bytesfixing-a-bug.mddoc · 2,290 bytes
Read excerpt
# Brainstorming
## Interview before you build
- Every feature, behavior change, or bug fix goes through this workflow. Depth scales with the
change and never drops to zero: a small change gets one short round and a few lines of task-spec.
- The aim is a design the user understands and has accepted, recorded in a spec-graph `task-spec`,
built, and then reflected in the durable specs — not a speculative implementation.
- Do not implement until the design is accepted. An explicit design or acceptance criteria in the
request count as approval of what they cover; build on them and never re-ask them.
## Doc map
- `fixing-a-bug.md` — the bug branch (step 4).