Execute WP

Select and execute queued or specified Work Packages from an idea-scoped backlog.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Darkpunkki/v-forge --skill execute-wp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Execute WP
Source: https://github.com/Darkpunkki/v-forge/tree/main/.claude/skills/work-wp
Command: npx skills add https://github.com/Darkpunkki/v-forge --skill execute-wp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end execution of Work Packages (WPs) from an idea-scoped backlog, selecting the next queued WP or running a specific WP to keep development momentum without manual coordination.

Core Features & Use Cases

  • Resolve IDEA_ID from input references, locate the corresponding backlog and target WP, then start execution automatically.
  • Auto-update statuses across the idea's backlog and manifest, with an auditable run log for traceability.
  • Support both queued progression and direct WP execution (WP-####) with structured verification and task-tracking.

Quick Start

Provide an IDEA_ID (and optionally a WP-####) to start executing the next WP from the backlog.

Frequently Asked Questions about Execute WP

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate work package execution from an idea backlog?

Automating work package execution requires providing an IDEA_ID to automatically select and execute the next queued WP from the backlog, maintaining steady project momentum without manual coordination.

Can I execute a specific work package directly using a WP ID?

Yes, you can execute a specific work package directly by providing both the IDEA_ID and the specific WP-#### identifier, enabling targeted runs alongside automated queued progression.

How does automated backlog tracking update task statuses?

Automated backlog tracking updates task statuses by resolving the IDEA_ID, reading work_packages.md and tasks.md, and syncing completion states across the backlog and manifest with auditable run logs.

Do I need an existing work_packages.md file to track backlog progress?

Yes, the workflow reads the latest work_packages.md and tasks.md files to resolve work packages and record verification results, requiring an established idea backlog environment to function correctly.

What is the best way to maintain steady project momentum across queued work packages?

The best way to maintain momentum is using automated progression to select and execute queued work packages sequentially, resolving IDEA_IDs and updating manifest statuses without manual intervention.