Run any Skill in Manus with one click

Get Started

brainstorm-feature

Stars510

Forks149

UpdatedJune 18, 2026 at 13:01

Clarify a rough product or engineering idea into a BRD-lite brief (Why) with measurable business value.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

HoangNguyen0403

HoangNguyen0403/agent-skills-standard

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

SKILL.md

readonly

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.

Optional args: slug=, ticket=<id/url>, mode=interactive|autonomous|channel, channel=, auto_continue=true|false.

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 BA-owned BRD-lite brief before PM PRD planning or technical design.

Steps

Gather intent:
- Load baseline BRD section and common-business-requirements.
- Draft a provisional brief before asking.
- Capture objective, sponsor, validation owner, stakeholders, users, pain/opportunity, value hypothesis, SMART metric, constraints, glossary, non-goals, and delivery context.
Explore options:
- List 3 viable approaches.
- Capture benefit, cost, risk, and unknowns for each.
- Include funding/priority rationale.
- Mark one recommended approach.
Pressure-test:
- Keep BRD solution-free; route functional behavior to PRD/SRS.
- Check security, privacy, accessibility, performance, data, rollout risks, and measurable approval criteria.
- Treat non-critical unknowns as assumptions.
- Split stakeholder asks into candidate REQ-* placeholders and flag platform, market, permission, and edge-case gaps for PM.
Decide:
- Ask only true blocking product decisions, max 3 at a time.
- Include a recommended default and 2-3 options for each question.
- Record accepted approach and rejected alternatives.
- Continue on non-critical assumptions; return BLOCKED only for missing owner, value metric, or scope fence.
- Save to docs/brd/brd-[slug].md when writes are allowed and route to plan-feature.

Runtime Contract

Use for rough feature, ops, or process-change ideas before PRD.
Required inputs: rough intent plus any known owner, metric, or scope fence.
Return BLOCKED only for missing owner, measurable value, or clear scope boundary.

Handoff Payload

slug, executive summary, business objective, SMART metric, recommended approach, alternatives, constraints, non-goals, open questions, PM handoff checklist.

Blocking Questions

Ask max 3 at a time with a recommended default and 2-3 options.

Output Template

# 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
## Offshore Delivery Context
## Recommended Approach
## Alternatives Considered

## Stakeholders

## Constraints
## Non-Goals
## Glossary
## PM Handoff Checklist

## Open Questions
## Next Workflow
plan-feature
## Cost Report
Call `get_session_cost(workflow="brainstorm-feature")` before final handoff.

More from this repository

same repository

common-protocol-enforcement

HoangNguyen0403/agent-skills-standard

Enforce Red-Team verification and adversarial protocol audit. Use when verifying tasks, performing self-scans, or checking for protocol violations. Load as composite for all sessions.

2026-06-18510

common-security-audit

HoangNguyen0403/agent-skills-standard

Probe for hardcoded secrets, injection surfaces, unguarded routes, business logic flaws, and platform-specific weaknesses across backend (Node, Go, Java, Python, Rust), frontend (React, Angular, Vue), and mobile (iOS, Android, Flutter) codebases. Use when performing security audits, vulnerability scans, secrets detection, or penetration testing.

2026-06-18510

battle-test

HoangNguyen0403/agent-skills-standard

Deep audit of a skills directory against the Skill Creator standard. Produces a scored report and phased remediation plan.

2026-06-18510

code-review

HoangNguyen0403/agent-skills-standard

Run an AI-assisted PR code review using multi-layer lenses with confidence scoring.

2026-06-18510

codebase-review

HoangNguyen0403/agent-skills-standard

Review an entire codebase against framework best practices and generate a prioritized improvement plan.

2026-06-18510

deploy-release

HoangNguyen0403/agent-skills-standard

Prepare and verify a staged or production deployment with rollback and smoke checks.

2026-06-18510

Brainstorm Feature Skill

[!IMPORTANT] Clarify a rough product or engineering idea into a BRD-lite brief (Why) with measurable business value.

Optional args: slug=, ticket=<id/url>, mode=interactive|autonomous|channel, channel=, auto_continue=true|false.

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 BA-owned BRD-lite brief before PM PRD planning or technical design.

Steps

Gather intent:

Load baseline BRD section and common-business-requirements.
Draft a provisional brief before asking.
Capture objective, sponsor, validation owner, stakeholders, users, pain/opportunity, value hypothesis, SMART metric, constraints, glossary, non-goals, and delivery context.

Explore options:

List 3 viable approaches.
Capture benefit, cost, risk, and unknowns for each.
Include funding/priority rationale.
Mark one recommended approach.

Pressure-test:

Keep BRD solution-free; route functional behavior to PRD/SRS.
Check security, privacy, accessibility, performance, data, rollout risks, and measurable approval criteria.
Treat non-critical unknowns as assumptions.
Split stakeholder asks into candidate REQ-* placeholders and flag platform, market, permission, and edge-case gaps for PM.

Decide:

Ask only true blocking product decisions, max 3 at a time.
Include a recommended default and 2-3 options for each question.
Record accepted approach and rejected alternatives.
Continue on non-critical assumptions; return BLOCKED only for missing owner, value metric, or scope fence.
Save to docs/brd/brd-[slug].md when writes are allowed and route to plan-feature.

Runtime Contract

Use for rough feature, ops, or process-change ideas before PRD.

Required inputs: rough intent plus any known owner, metric, or scope fence.

Return BLOCKED only for missing owner, measurable value, or clear scope boundary.

Handoff Payload

slug, executive summary, business objective, SMART metric, recommended approach, alternatives, constraints, non-goals, open questions, PM handoff checklist.

Blocking Questions

Ask max 3 at a time with a recommended default and 2-3 options.

Output Template

# 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 ## Offshore Delivery Context ## Recommended Approach ## Alternatives Considered ## Stakeholders ## Constraints ## Non-Goals ## Glossary ## PM Handoff Checklist ## Open Questions ## Next Workflow plan-feature ## Cost Report Call `get_session_cost(workflow="brainstorm-feature")` before final handoff.