work-brainstorming

Name: work-brainstorming
Availability: InStock
Author: byunghak-dable

Guide requirement clarification and generate specification documents for architect review.

Updated Sep 12, 2023

Search Tags:#brainstorming #software design #spec writing #requirements gathering #architectural review #pre-coding

Ready to run

npx skills add https://github.com/byunghak-dable/.dotfiles --skill work-brainstorming

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: work-brainstorming
Source: https://github.com/byunghak-dable/.dotfiles/tree/main/claude/.claude/skills/work-brainstorming
Command: npx skills add https://github.com/byunghak-dable/.dotfiles --skill work-brainstorming

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the ambiguity and decision-making paralysis that often occurs before starting a new coding task, ensuring clear requirements and a well-defined approach.

Core Features & Use Cases

Requirement Elicitation: Engages in a structured 1:1 conversation to uncover and refine feature requirements.
Approach Definition: Presents 2-3 distinct implementation strategies with their trade-offs.
Spec Document Generation: Creates a formal specification document for architect review.
Architectural Review: Facilitates a review process to ensure feasibility and completeness.
Use Case: When tasked with implementing a new user authentication flow, use this Skill to explore different security models, define the exact user journey, and get architectural sign-off before writing any code.

Quick Start

Use the work-brainstorming skill to explore requirements for implementing a new user profile editing feature.

Frequently Asked Questions about work-brainstorming

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

FAQPage Schema

How do I clarify software design requirements before starting to code?▼

Defining implementation approaches before coding involves exploring 2-3 distinct software design strategies with their specific trade-offs, ensuring you select the most feasible architectural path before development begins.

What is the best way to gather requirements for a new feature like a user authentication flow?▼

The best way to gather requirements for a user authentication flow is through a structured 1:1 conversation that explores different security models, defines the exact user journey, and secures architectural sign-off via a spec document.

How do I generate a specification document for architectural review?▼

You generate a specification document for architectural review by completing a pre-coding requirement clarification process that captures context, defines the chosen approach, and outputs a formal spec ensuring feasibility and completeness.

Does structured pre-coding brainstorming help with decision-making paralysis in software development?▼

Structured pre-coding brainstorming resolves decision-making paralysis by guiding you through context gathering and requirement exploration, presenting clear implementation strategies to ensure a well-defined approach before writing code.

When do I need spec writing and architectural review for a software engineering task?▼

You need spec writing and architectural review when facing ambiguity in a new coding task, ensuring that requirement gathering is complete and architectural feasibility is validated before any development starts.