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, profile=business|hybrid|technical.
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,
common-business-requirements, and common-operator-profile.
- Infer
operator_profile (business | hybrid | technical) from request phrasing; never ask the operator to self-rate. Carry it in the Handoff Payload.
- 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.
- Draft defaults before blocking: sponsor/validation owner = the requesting operator; SMART metric drafted from the stated pain (mark
assumed); scope fence drafted from the request with explicit non-goals.
- For
operator_profile=business, present all three drafted defaults as one confirm-with-default question round (fits the max-3 rule) instead of blocking outright.
- Continue on non-critical assumptions; return BLOCKED only when the operator rejects the drafted defaults, or in autonomous/channel mode with no confirmation channel available.
- 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; missing items get drafted defaults, not an automatic block.
- Return BLOCKED only when the operator rejects drafted defaults for owner, measurable value, or scope boundary, or autonomous mode has no confirmation channel.
Handoff Payload
slug, operator_profile, executive summary, business objective, SMART metric, recommended approach, alternatives, constraints, non-goals, open questions, assumptions (flagged assumed), PM handoff checklist.- Outcome report with
feature_status=requirements_ready | blocked, requirement trace seed, completed/missing evidence, decision needed, and recommended next workflow.
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
## Outcome Report
feature_status: requirements_ready | blocked
requirement_trace: BRD-OBJ-* -> candidate REQ-*
completed_evidence: []; missing_evidence: []; decision_needed: []; assumptions: []; recommended_next_workflow: plan-feature
## Open Questions
## Next Workflow
plan-feature
## Cost Report
Call `get_session_cost(workflow="brainstorm-feature")` before final handoff.
1---2name: brainstorm-feature3description: Clarify a rough product or engineering idea into a BRD-lite brief (Why) with measurable business value.4---5# Brainstorm Feature Skill
6
7> [!IMPORTANT]
8> Clarify a rough product or engineering idea into a BRD-lite brief (Why) with measurable business value.
9
10Optional args: slug=<feature>, ticket=<id/url>, mode=interactive|autonomous|channel, channel=<id>, auto_continue=true|false, profile=business|hybrid|technical.
11
12## Instructions
13
14When the user asks to perform this workflow, execute the following steps:
15
16
17# Brainstorm Feature Workflow (BRD-lite / Why)
18
19Goal: Convert vague intent into a compact BA-owned BRD-lite brief before PM PRD planning or technical design.
20
21## Steps
22
231. Gather intent:
24 - Load baseline BRD section, `common-business-requirements`, and `common-operator-profile`.
25 - Infer `operator_profile` (business | hybrid | technical) from request phrasing; never ask the operator to self-rate. Carry it in the Handoff Payload.
26 - Draft a provisional brief before asking.
27 - Capture objective, sponsor, validation owner, stakeholders, users, pain/opportunity, value hypothesis, SMART metric, constraints, glossary, non-goals, and delivery context.
282. Explore options:
29 - List 3 viable approaches.
30 - Capture benefit, cost, risk, and unknowns for each.
31 - Include funding/priority rationale.
32 - Mark one recommended approach.
333. Pressure-test:
34 - Keep BRD solution-free; route functional behavior to PRD/SRS.
35 - Check security, privacy, accessibility, performance, data, rollout risks, and measurable approval criteria.
36 - Treat non-critical unknowns as assumptions.
37 - Split stakeholder asks into candidate `REQ-*` placeholders and flag platform, market, permission, and edge-case gaps for PM.
384. Decide:
39 - Ask only true blocking product decisions, max 3 at a time.
40 - Include a recommended default and 2-3 options for each question.
41 - Record accepted approach and rejected alternatives.
42 - Draft defaults before blocking: sponsor/validation owner = the requesting operator; SMART metric drafted from the stated pain (mark `assumed`); scope fence drafted from the request with explicit non-goals.
43 - For `operator_profile=business`, present all three drafted defaults as one confirm-with-default question round (fits the max-3 rule) instead of blocking outright.
44 - Continue on non-critical assumptions; return BLOCKED only when the operator rejects the drafted defaults, or in autonomous/channel mode with no confirmation channel available.
45 - Save to `docs/brd/brd-[slug].md` when writes are allowed and route to `plan-feature`.
46
47## Runtime Contract
48
49- Use for rough feature, ops, or process-change ideas before PRD.
50- Required inputs: rough intent plus any known owner, metric, or scope fence; missing items get drafted defaults, not an automatic block.
51- Return BLOCKED only when the operator rejects drafted defaults for owner, measurable value, or scope boundary, or autonomous mode has no confirmation channel.
52
53## Handoff Payload
54
55- `slug`, `operator_profile`, executive summary, business objective, SMART metric, recommended approach, alternatives, constraints, non-goals, open questions, assumptions (flagged `assumed`), PM handoff checklist.
56- Outcome report with `feature_status=requirements_ready | blocked`, requirement trace seed, completed/missing evidence, decision needed, and recommended next workflow.
57
58## Blocking Questions
59
60- Ask max 3 at a time with a recommended default and 2-3 options.
61
62## Output Template
63
64```md
65# BRD-lite Brief: [Name]
66## Executive Summary
67## Business Objective
68## SMART Success Metric
69## Target Users
70## Problem
71## AS-IS To TO-BE
72## Stakeholders And Validation Owner
73## Success Metrics
74## Cost-Benefit / Value Hypothesis
75## Offshore Delivery Context
76## Recommended Approach
77## Alternatives Considered
78## Stakeholders
79## Constraints
80## Non-Goals
81## Glossary
82## PM Handoff Checklist
83## Outcome Report
84feature_status: requirements_ready | blocked
85requirement_trace: BRD-OBJ-* -> candidate REQ-*
86completed_evidence: []; missing_evidence: []; decision_needed: []; assumptions: []; recommended_next_workflow: plan-feature
87## Open Questions
88## Next Workflow
89plan-feature
90## Cost Report
91Call `get_session_cost(workflow="brainstorm-feature")` before final handoff.
92```
93
HoangNguyen0403