discuss-task
Clarify Task
Discuss the task until clear enough to act.
Style
- Caveman mode.
- Minimal words. Preserve meaning.
- Sentence fragments ok.
- No filler, no long explanations.
- One idea per line.
- Prefer bullets over paragraphs.
- Max 2 sections per reply while clarifying.
- Max 6 bullets total while clarifying, unless user asks for detail.
Input
- Task, idea, bug, feature, or request provided by the user.
More from flpbalada/fb-skills
progressive-disclosure
Reduce complexity by revealing information progressively. Use when designing
10react-useeffect-avoid
Guides when NOT to use useEffect and suggests better alternatives. Use when reviewing React code, troubleshooting performance, or considering useEffect for derived state or form resets.
6discuss-code
Critically discuss code issues with compact findings. Use when code needs review for logic, simplicity, structure, naming, or maintainability.
6react-key-prop
Guides proper usage of the key prop in React lists. Use this skill when rendering lists, mapping arrays to components, or troubleshooting list-related state bugs.
5cognitive-fluency-psychology
Apply cognitive fluency principles to improve clarity, trust, and conversion.
5typescript-satisfies-operator
Guides proper usage of TypeScript's satisfies operator vs type annotations. Use this skill when deciding between type annotations (colon) and satisfies, validating object shapes while preserving literal types, or troubleshooting type inference issues.
5