brainstorm-feature
$
npx mdskill add HoangNguyen0403/agent-skills-standard/brainstorm-feature> [!IMPORTANT] > Clarify a rough product or engineering idea into a BRD-lite brief (Why) with measurable business value.
SKILL.md
.github/skills/brainstorm-featureView on GitHub ↗
---
name: brainstorm-feature
description: "Clarify a rough product or engineering idea into a BRD-lite brief (Why) with measurable business value."
metadata:
triggers:
keywords:
- brainstorm feature
- workflow
---
# Brainstorm Feature Skill
> [!IMPORTANT]
> Clarify a rough product or engineering idea into a BRD-lite brief (Why) with measurable business value.
## Instructions
When the user asks to perform this workflow, execute the following steps:
# Brainstorm Feature Workflow (BRD-lite / Why)
Goal: Convert vague intent into a compact BRD-lite brief before PRD or technical planning.
## Steps
1. Gather intent:
- Load baseline: `docs/requirements-standards-baseline.md` (BRD section).
- Load `common-business-requirements`.
- Executive summary: purpose, desired outcome, sponsor, validation owner.
- Business objective
- Stakeholders and impacted teams
- Current state (AS-IS) and desired state (TO-BE)
- Target user
- Pain or opportunity
- Desired outcome and value hypothesis
- SMART metric: baseline, target, and date
- Cost-benefit or value hypothesis
- Constraints, glossary terms, and non-goals
2. Explore options:
- List 3 viable approaches.
- Capture benefit, cost, risk, and unknowns for each.
- Include funding/priority rationale.
- Mark one recommended approach.
3. Pressure-test:
- Keep BRD solution-free; route functional behavior to PRD/SRS.
- Check security, privacy, accessibility, performance, data, and rollout risks.
- Define measurable success metrics and approval criteria.
- Identify assumptions that need user confirmation.
- Identify existing repo patterns to reuse.
- Add Mermaid AS-IS/TO-BE process diagram when workflow complexity affects approval.
4. Decide:
- Ask only for unresolved product decisions.
- Record accepted approach and rejected alternatives.
- Save BRD-lite brief to `docs/specs/product-brief-[slug].md` when writing files is allowed.
- Route next step to `plan-feature` when intent is actionable.
## Output
## Output Template
```md
# BRD-lite Brief: [Name]
## Executive Summary
## Business Objective
## SMART Success Metric
## Target Users
## Problem
## AS-IS To TO-BE
## Stakeholders And Validation Owner
## Success Metrics
## Cost-Benefit / Value Hypothesis
## Recommended Approach
## Alternatives Considered
## Stakeholders
## Constraints
## Non-Goals
## Glossary
## Open Questions
## Next Workflow
plan-feature
## Cost Report
```
More from HoangNguyen0403/agent-skills-standard
- android-agp-upgradeUpgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.
- android-architectureApply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns.
- android-background-workImplement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers.
- android-composeBuild high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects.
- android-compose-migrationMigrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.
- android-concurrencyWrite correct coroutine scopes, Flow collection, and dispatcher injection in Android. Use when writing suspend functions, choosing between StateFlow and SharedFlow, or injecting Dispatchers for testability.
- android-deploymentConfigure release signing, R8 obfuscation, and App Bundle publishing for Android. Use when setting up signing configs, enabling minification, adding ProGuard keep rules, or preparing for Play Store submission.
- android-design-systemEnforce Material Design 3 theming and design token usage in Jetpack Compose. Use when implementing M3 components, color schemes, typography, or design tokens.
- android-diConfigure Hilt dependency injection with proper scoping, modules, and constructor injection in Android. Use when setting up Hilt DI, defining modules, or configuring component scoping.
- android-edge-to-edgeMigrate a Jetpack Compose app to edge-to-edge display and fix system bar inset issues. Use when UI components are obscured by navigation/status bars, fixing IME insets, or enabling edge-to-edge for SDK 35+.