Analyze frontend task risks

frontend-task-analysisskillsetup L20
AlexanderKopyl/boardly
What it does

Analyze and break down frontend development tasks into estimable subtasks

Best for

When decomposing frontend work into concrete, parallelizable subtasks with clear acceptance criteria.

Inputs
  • · feature description
  • · design mockup/spec
  • · acceptance criteria
Outputs
  • · component breakdown
  • · estimated task list
  • · testing plan
Preconditions

Feature scope defined; design available; team familiar with component patterns

Failure modes
  • · estimation doesn't account for edge cases
  • · components too coupled to parallelize
  • · visual QA requirements under-scoped
Trust signals
  • · component architecture patterns
  • · QA checklist examples
  • · dependency mapping