process-plan-brainstorming

Refines feature ideas into validated design documents through structured collaborative dialogue.

1|Updated Jun 23, 2026
One-click install
npx skills add https://github.com/bitranox/bitranox-skills --skill process-plan-brainstorming-bitranox
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: process-plan-brainstorming
Source: https://github.com/bitranox/bitranox-skills/tree/main/plugins/bitranox/skills/process-plan-brainstorming
Command: npx skills add https://github.com/bitranox/bitranox-skills --skill process-plan-brainstorming-bitranox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a non-trivial feature or behaviour change without a settled design leads to rework, scope creep, and misaligned implementations. This Skill turns a rough idea into a fully formed, validated design through structured one-question-at-a-time dialogue before any code is written. ## Core Features & Use Cases - Guided Requirements Discovery: Asks one question at a time, preferring multiple-choice, to clarify purpose, constraints, and success criteria. - Approach Exploration: Proposes 2-3 alternative designs with trade-offs and a reasoned recommendation, with an option to delegate synthesis to a stronger subagent model. - Incremental Design Validation: Presents the design in 200-300 word sections covering architecture, components, data flow, error handling, and testing, confirming each section before continuing. - Use Case: You want to add a caching layer to your application but haven't decided on scope or technology. The Skill interviews you about constraints, compares Redis versus in-process caching, and writes the agreed design to docs/plans/ as a committed design document. ## Quick Start Ask the assistant to brainstorm and turn your rough feature idea into a validated design document before implementation begins.

Frequently Asked Questions about process-plan-brainstorming

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

FAQPage Schema
How do I turn a rough feature idea into a design document?▼

Start a brainstorming session that asks clarifying questions one at a time about purpose, constraints, and success criteria. The process then proposes 2-3 approaches with trade-offs and writes the validated design to docs/plans/ as a dated markdown file committed to git.

When should I use design brainstorming before coding?▼

Use it for non-trivial features, components, or behaviour changes where the design or requirements are not yet settled. Skip it for trivial, mechanical, or fully-specified changes where the design is already agreed upon.

What happens after the design document is approved?▼

The validated design is written to docs/plans/YYYY-MM-DD-topic-design.md and committed to git. If you continue to implementation, the workflow requires creating an isolated git worktree and writing a detailed implementation plan.

Can brainstorming quality vary between AI models?▼

Yes, generating genuinely different design alternatives is capability-sensitive, and weaker models may produce shallow near-duplicate options. On a lesser model tier, the approach synthesis can be delegated to a pinned sonnet or opus subagent.

When should I skip the brainstorming step?▼

Skip it when the task is trivial, mechanical, or fully specified with settled requirements. Applying structured design dialogue to already-decided work adds overhead without improving the outcome.