recipe-front-plan

Generate a frontend work plan from design docs by placing UI specifications in docs/design/. The automation orchestrates document selection, creates test skeletons, and builds a reviewable work plan requiring explicit user approval to finalize.

Yes, you can automate test skeleton generation from UI specs. The Skill reads design specifications from docs/design/ and automatically produces tied test skeletons to accelerate validation alongside the generated work plan.

The best way to orchestrate frontend planning from design documents is using an automated workflow that selects design files, generates test skeletons, creates a work plan, and enforces iterative review approvals to ensure alignment between design intent and tasks.

Yes, you need explicit user approval to complete frontend work plan creation. The workflow includes built-in review steps where you must explicitly approve the generated plan before the orchestration finishes and finalizes the output.

Yes, this frontend planning automation works without external dependencies. It operates independently to select design documents, generate test skeletons, and create work plans without requiring additional packages or external component integrations.