requirements-analyzer
Requirements Analyzer
Check clarity, scope, feasibility, and risk before implementation.
Depth
- Quick: bug fix or small change.
- Standard: feature or medium change.
- Deep: large feature or architecture change.
Scope Rules
- Target
50-200 LOCper PR. - Split work over
400 LOC. - Common splits: foundation, API/data, UI, integration.
Discovery
- Who is the user?
More from flpbalada/fb-skills
progressive-disclosure
Reduce complexity by revealing information progressively. Use when designing
11discuss-task
Clarify ambiguous tasks before action. Use when goal, scope, success criteria, constraints, or risks are unclear.
7react-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.
5