Lucas Oliveira Costa

You can manage the full PRD-driven development cycle: create Product Requirements Documents via interactive brainstorming, generate Technical Specifications from PRDs, decompose specs into executable task files, execute tasks with auto-commit, run code review rounds, and enforce verification evidence before completion claims.

Tech leads, software engineers, and engineering teams practicing spec-driven development benefit most. The skills suit anyone who wants structured requirements documentation, architecture decisions recorded in TechSpecs, tracked task execution, and disciplined review and verification before shipping code.

Start with cy-create-prd to build requirements, then cy-create-techspec for the technical plan, cy-create-tasks to break work into task files, cy-execute-task to implement each task, cy-review-round to audit the changes, and cy-final-verify before committing or claiming completion.

Task execution requires a provided task file, PRD directory, and tracking file paths. Task decomposition requires an existing PRD or TechSpec, and TechSpec creation requires an existing PRD. Review rounds operate on implemented PRD tasks, and final verification applies only at concrete completion steps.

The skills are published publicly on the author's GitHub profile under the lucasocosta account with 30 public repositories. No paid tier or licensing fee is indicated in the manifest; consult the individual repository for the exact license terms before redistribution or commercial use.