Execute approved implementation plans into validated code with tests, lint, and builds.
npx skills add https://github.com/gvinokur/qatar-prode --skill implementer-gvinokur
Please help me install this Agent Skill. Skill: implementer Source: https://github.com/gvinokur/qatar-prode/tree/main/.claude/skills/implementer Command: npx skills add https://github.com/gvinokur/qatar-prode --skill implementer-gvinokur
This Skill automates and enforces a disciplined implementation workflow after a plan is approved, preventing scope creep and broken commits by requiring task definition, dependency tracking, per-task code-structure updates, and mandatory validation before any commit or deployment.
Use the implementer skill to execute an approved plan by creating tasks, defining dependencies, running tests and linters, updating CODE-STRUCTURE.md, and pushing the validated commit to trigger a Vercel Preview.
High-intent search queries and answers about installing and using this skill.
To turn an approved plan into deployable code, break it into atomic tasks using TaskCreate, declare dependencies with TaskUpdate, execute in waves, run mandatory tests and linting, update CODE-STRUCTURE.md, then commit to trigger a Vercel Preview deployment.
Manage task dependencies and execution waves by using TaskCreate to define atomic implementation tasks and TaskUpdate to declare their dependencies, organizing them into parallel execution waves for clarity and safe subagent delegation.
Enforce code structure updates and validation by requiring a CODE-STRUCTURE.md update in the same commit as source changes, alongside passing mandatory local tests, lint checks, and build validation before any code is committed.
Yes, the implementer workflow supports Vercel Preview deployments. Pushing validated commits automatically triggers a Vercel Preview environment for user testing and QA after local validation passes.
Yes, you can delegate simple and isolated implementation tasks to subagents. The workflow supports both hybrid subagent delegation for individual tasks and per-wave subagent workflows for larger feature stories.
Yes, you need explicit permission to run migrations during the implementation workflow. The process enforces migration permission checks to prevent unauthorized database changes before committing code.
ch-yang1273Convert plan.md and spec.md into phase-based tasks.md with dependency graphs.
mrhinkleSet up VibeCoding project infrastructure and onboarding for website preview or deployment.
chy5301Coordinates subagents to automate phased, multi-step workflows with task review cycles.
ma08Automate Vercel preview deployments with fallback for unauthenticated CLI environments.
