itseffi/productize/execute-task

Claude Code and agent skill by itseffi/productize

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Executes one PRD task end-to-end using a provided task file, PRD directory, tracking file paths, and auto-commit mode. Use when a prompt includes a task specification that must be implemented, validated, and reflected in task tracking files. Do not use for PR review batches, generic coding tasks without a PRD task file, or standalone verification-only work.

Install

npx vskill@latest install itseffi/productize/execute-task

SKILL.md

The same SKILL.md was published earlier as itseffi/productize/execute-task.

Execute PRD Task

Execute one PRD task from exploration through tracking updates.

Required Inputs

  • Task specification markdown.
  • PRD directory path.
  • Task file path.
  • Master tasks file path.
  • Auto-commit mode.
  • Optional workflow memory directory path.
  • Optional shared workflow memory path.
  • Optional current task memory path.

Workflow

  1. Ground in repository and PRD context.
  • Read the provided task specification.
  • Read the repository guidance files named by the caller.
  • Read the PRD documents under the provided directory, especially _techspec.md and _tasks.md.
  • Read ADRs from the adrs/ subdirectory of the PRD directory to understand the architectural decision context for this task.
  • After reading all sources, check for conflicts between the task specification, techspec, and ADRs. If any requirements contradict each other, stop and report the conflict instead of guessing — do not proceed to step 2.
  • If the caller provides workflow memory paths, use the installed workflow-memory skill before editing code.
  • If the caller marks the task as isolated or task-local-only for parallel

execution, read shared workflow memory but write only current task memory.

  • Reconcile the current workspace state before new edits.
  1. Build the execution checklist.
  • Extract deliverables, acceptance criteria, and every explicit Validation, Test Plan, or Testing item into a numbered working checklist.
  • Print the full checklist before starting implementation so it is visible and trackable.
  • Capture the concrete pre-change signal that proves the task is not finished yet.
  • Use this checklist as a gate: mark each item done as evidence is produced during implementation, and do not proceed to validation until every checklist item has been addressed.
  1. Implement the task.
  • Keep scope tight to the task specification.
  • Follow repository patterns and real dependency APIs.
  • Record meaningful out-of-scope work as follow-up notes instead of silently expanding the task.
  1. Validate and self-review.
  • Run every test and validation command listed in the task specification — not just the repository-wide verification.
  • Use the installed final-verify skill. This step is mandatory regardless of auto-commit mode — always verify before claiming completion.
  • Perform a self-review after verification and resolve every blocking issue before proceeding.
  1. Update task tracking.
  • If workflow memory paths were provided, update the memory files first — record decisions, learnings, and touched surfaces before updating tracking status.
  • Use the caller-provided task file path and master tasks file path.
  • Mark subtasks complete only when the implementation and evidence are actually complete.
  • Change task status to completed only after clean verification and self-review.
  • Read references/tracking-checklist.md when applying status, checklist, or commit updates.
  • Sequence: memory update (if applicable) -> task file checkboxes -> task status -> master tasks file -> commit (if applicable).
  1. Handle commit behavior.
  • If auto-commit is enabled, create one local commit after clean verification, self-review, and tracking updates.
  • If auto-commit is disabled, leave the diff ready for manual review and commit.
  • Never push automatically.

Error Handling

  • If the pre-change signal cannot be reproduced directly, capture the strongest available baseline signal and state the limitation.
  • If validation fails, keep the task status unchanged until the failure is resolved.
  • If tracking files are missing, stop and report the missing path before marking completion.

Security

  • Security scanPassed, 95 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

7-day trend score
5

Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/itseffi/productize/execute-task/badge)](https://verified-skill.com/skills/itseffi/productize/execute-task)

Something wrong with this skill or its page? Tell us.