sap-brainstorming

Document SAP feature decisions with ADR templates before coding.

6|1|Updated Mar 18, 2026

Search Tags:#brainstorming #process #workflows #sap #decision-tree #architecture-decision-record

Ready to run

npx skills add https://github.com/vigneshbarani24/sap-superpowers --skill sap-brainstorming

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sap-brainstorming
Source: https://github.com/vigneshbarani24/sap-superpowers/tree/main/skills/sap-brainstorming
Command: npx skills add https://github.com/vigneshbarani24/sap-superpowers --skill sap-brainstorming

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured brainstorming for SAP work to ensure clear planning and documented decisions before implementation.

Core Features & Use Cases

Enforces a formal checklist and decision records (ADR) before coding.
Guides exploration of SAP standard options, clean core impact, and integration considerations.
Generates architecture decision artifacts and documentation for project governance.

Quick Start

Begin a brainstorming session by outlining the business requirement, selecting a classification, exploring standard SAP options, and recording your Architecture Decision Record before any development.

Frequently Asked Questions about sap-brainstorming

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

FAQPage Schema

How do I document SAP feature planning decisions before coding?▼

To document SAP feature planning before coding, enforce structured brainstorming with formal checklists and Architecture Decision Records. This ensures clear project governance by exploring standard options and clean-core impact before any development begins.

What is the best way to structure SAP brainstorming for new module enhancements?▼

The best way to structure SAP brainstorming for enhancements is to apply a decision-tree workflow with hard gates. This process mandates exploring standard SAP options and evaluating clean-core impact before finalizing the design.

When do I need an Architecture Decision Record for SAP workflows?▼

You need an Architecture Decision Record for SAP workflows when you require formal checkpoint approval before implementation. It captures option analysis and clean-core impact assessments to guide and govern project design decisions.

How do I evaluate clean-core impact during SAP solution exploration?▼

To evaluate clean-core impact during SAP solution exploration, use a structured brainstorming process that enforces hard gates. This formal checklist requires you to explore standard SAP options and document integration considerations before coding.

Can I use this structured brainstorming process across different SAP modules?▼

Yes, you can use this structured brainstorming process across different SAP modules. It supports concept ideation for new features, enhancements, or project approaches, ensuring consistent decision documentation and clean-core evaluation.

Why enforce hard gates in SAP architecture decision workflows?▼

Enforce hard gates in SAP architecture decision workflows to prevent unstructured planning and unclear feature scopes. This checkpoint mechanism guarantees option analysis and clean-core impact are fully documented before development starts.