skills.rest
FnSK4R17s
FnSK4R17sCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

brainstorming

Create linked brainstorming docs for GitHub issues with standard folder structures.

1|Updated Nov 28, 2025
Search Tags:#documentation#brainstorming#decision#spec#ideas#github-issues
One-click install
npx skills add https://github.com/FnSK4R17s/chakravarti-cli --skill brainstorming-fnsk4r17s
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/FnSK4R17s/chakravarti-cli/tree/main/.agent/skills/brainstorming
Command: npx skills add https://github.com/FnSK4R17s/chakravarti-cli --skill brainstorming-fnsk4r17s

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming docs are ephemeral and linked to GitHub issues; they let teams explore ideas, plan features, and document decisions before formal specs are created, after which they may be discarded or promoted.

Core Features & Use Cases

  • Create and organize issue-linked brainstorming docs that evolve into specs.
  • Use a standard folder structure (brainstorming/issue-XXX-<title>) to keep context clear and traceable.
  • Promote lasting insights to guiding docs or convert them into formal specs as part of the workflow.

Quick Start

Create a new brainstorming folder from a GitHub issue, fill in notes.md from the template, and link decisions back to the issue.

Frequently Asked Questions about brainstorming

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create brainstorming docs linked to GitHub issues for feature planning?▼

Promote brainstorming docs into formal specs by extracting lasting insights and decisions from the ephemeral notes and converting them into structured specifications with clear handoffs and traceable decision history.

What is the best way to document decisions before creating formal specs from GitHub issues?▼

Archive brainstorming docs when finished by discarding ephemeral notes after lasting insights are promoted to guiding docs or formal specs, keeping the repository clean while preserving traceable decision history.

How does organizing issue-linked brainstorming docs work with a standard folder structure?▼

Organizing issue-linked brainstorming docs works by enforcing a consistent folder structure named brainstorming/issue-XXX-<title> for each GitHub issue, ensuring context stays clear and traceable throughout the documentation workflow.

Can I use brainstorming docs for GitHub issues without formal specs?▼

You can use brainstorming docs for GitHub issues without formal specs by keeping them as ephemeral planning artifacts that may be discarded when finished or archived after documenting decisions.

Related Skills

Explore More Product & Management Skills→
mori-shin-xmori-shin-x
12

speckit-taskstoissues

Convert task list items into dependency-ordered GitHub issues.

Community
Advanced
andregusman-raizandregusman-raiz
19

ag-pipeline-issue

Converts GitHub Issues into SPECs, plans, builds, verifications, and tests.

Community
Advanced
PiklarPiklar

speckit-taskstoissues

Convert project tasks into dependency-ordered GitHub issues.

Community
Advanced
mindmorassmindmorass
2

obsidian-publisher

Write Markdown notes and Mermaid diagrams into Obsidian vault folders.

Community
Basic