Brainstorming & Communication Protocol

brainstorming

Socratic questioning protocol + user communication. MANDATORY for complex requests, new features, or unclear requirements. Includes progress reporting and error handling.

CongDon1207/AGENTS.md·0installs18stars

SKILL.md

Full skill instructions

Brainstorming & Communication Protocol

MANDATORY: Use for complex/vague requests, new features, updates.

🛑 SOCRATIC GATE (ENFORCEMENT)

When to Trigger

Pattern	Action
"Build/Create/Make [thing]" without details	🛑 ASK 3 questions
Complex feature or architecture	🛑 Clarify before implementing
Update/change request	🛑 Confirm scope
Vague requirements	🛑 Ask purpose, users, constraints

🚫 MANDATORY: 3 Questions Before Implementation

STOP - Do NOT start coding
ASK - Minimum 3 questions:
- 🎯 Purpose: What problem are you solving?
- 👥 Users: Who will use this?
- 📦 Scope: Must-have vs nice-to-have?
WAIT - Get response before proceeding

🧠 Dynamic Question Generation

⛔ NEVER use static templates. Read dynamic-questioning.md for principles.

Core Principles

Principle	Meaning
Questions Reveal Consequences	Each question connects to an architectural decision
Context Before Content	Understand greenfield/feature/refactor/debug context first
Minimum Viable Questions	Each question must eliminate implementation paths
Generate Data, Not Assumptions	Don't guess—ask with trade-offs

Question Generation Process

1. Parse request → Extract domain, features, scale indicators
2. Identify decision points → Blocking vs. deferable
3. Generate questions → Priority: P0 (blocking) > P1 (high-leverage) > P2 (nice-to-have)
4. Format with trade-offs → What, Why, Options, Default

Question Format (MANDATORY)

### [PRIORITY] **[DECISION POINT]**

**Question:** [Clear question]

**Why This Matters:**
- [Architectural consequence]
- [Affects: cost/complexity/timeline/scale]

**Options:**
| Option | Pros | Cons | Best For |
|--------|------|------|----------|
| A | [+] | [-] | [Use case] |

**If Not Specified:** [Default + rationale]

For detailed domain-specific question banks and algorithms, see: dynamic-questioning.md

Progress Reporting (PRINCIPLE-BASED)

PRINCIPLE: Transparency builds trust. Status must be visible and actionable.

Status Board Format

Agent	Status	Current Task	Progress
[Agent Name]	✅🔄⏳❌⚠️	[Task description]	[% or count]

Status Icons

Icon	Meaning	Usage
✅	Completed	Task finished successfully
🔄	Running	Currently executing
⏳	Waiting	Blocked, waiting for dependency
❌	Error	Failed, needs attention
⚠️	Warning	Potential issue, not blocking

Error Handling (PRINCIPLE-BASED)

PRINCIPLE: Errors are opportunities for clear communication.

Error Response Pattern

1. Acknowledge the error
2. Explain what happened (user-friendly)
3. Offer specific solutions with trade-offs
4. Ask user to choose or provide alternative

Error Categories

Category	Response Strategy
Port Conflict	Offer alternative port or close existing
Dependency Missing	Auto-install or ask permission
Build Failure	Show specific error + suggested fix
Unclear Error	Ask for specifics: screenshot, console output

Completion Message (PRINCIPLE-BASED)

PRINCIPLE: Celebrate success, guide next steps.

Completion Structure

1. Success confirmation (celebrate briefly)
2. Summary of what was done (concrete)
3. How to verify/test (actionable)
4. Next steps suggestion (proactive)

Communication Principles

Principle	Implementation
Concise	No unnecessary details, get to point
Visual	Use emojis (✅🔄⏳❌) for quick scanning
Specific	"~2 minutes" not "wait a bit"
Alternatives	Offer multiple paths when stuck
Proactive	Suggest next step after completion

Anti-Patterns (AVOID)

Anti-Pattern	Why
Jumping to solutions before understanding	Wastes time on wrong problem
Assuming requirements without asking	Creates wrong output
Over-engineering first version	Delays value delivery
Ignoring constraints	Creates unusable solutions
"I think" phrases	Uncertainty → Ask instead

Install skill

Copy and run in your terminal

npx -y skills add https://github.com/CongDon1207/AGENTS.md --skill brainstorming

View on GitHub

.agent/skills/brainstorming/SKILL.md

senior-data-engineer
World-class data engineering skill for building scalable data pipelines, ETL/ELT systems, and data infrastructure. Expertise in Python, SQL, Spark, Airflow, dbt, Kafka, and modern data stack. Includes data modeling, pipeline orchestration, data quality, and DataOps. Use when designing data archit...
0 installs
clean-code
Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments
0 installs
vr-ar
VR/AR development principles. Comfort, interaction, performance requirements.
0 installs
tailwind-patterns
Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture.
0 installs

More skills from CongDon1207

CongDon1207/AGENTS.md

testing-patterns

Testing patterns and principles. Unit, integration, mocking strategies.

18 0

View

CongDon1207/AGENTS.md

Guide for creating effective skills, adding skill references, skill scripts or optimizing existing skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, frameworks, libraries o...

18 0

View

CongDon1207/AGENTS.md

performance-profiling

Performance profiling principles. Measurement, analysis, and optimization techniques.

18 0

View

CongDon1207/AGENTS.md

python-patterns

Python development principles and decision-making. Framework selection, async patterns, type hints, project structure. Teaches thinking, not copying.

18 0

View

CongDon1207/AGENTS.md

xlsx

Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization. When Codex needs to work with spreadsheets (.xlsx, .xlsm, .csv, .tsv, etc) for: (1) Creating new spreadsheets with formulas and formatting, (2) Reading or analyzing d...

18 0

View

CongDon1207/AGENTS.md

pdf

Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Codex needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.

18 0

View

CongDon1207/AGENTS.md

web-design-guidelines

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

18 0

View

CongDon1207/AGENTS.md

databases

Work with MongoDB (document database, BSON documents, aggregation pipelines, Atlas cloud) and PostgreSQL (relational database, SQL queries, psql CLI, pgAdmin). Use when designing database schemas, writing queries and aggregations, optimizing indexes for performance, performing database migrations...

18 0

View

CongDon1207/AGENTS.md

vulnerability-scanner

Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.

18 0

View

CongDon1207/AGENTS.md

docx

Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Codex needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with t...

18 0

View

CongDon1207/AGENTS.md

tasks-code-review

Use for QUICK PR reviews with structured checklists (architecture, patterns, security, performance). Provides step-by-step review process, git diff commands, and review report templates. Best for pull request reviews and pre-commit checks. NOT for deep refactoring analysis (use code-review instead).

18 0

View

CongDon1207/AGENTS.md